Review by chucko58 
member for 2 years, 8 visits, last login: 1.2 years ago
lodged 2 years ago
 Sunnyvale,Santa Clara,CA
 $58 per month- (3 month contract)
 about 30 days AT&T "Run by a geek, for geeks. Great tech support, no BS, no BW caps. VERY reliable - 99.9+% uptime." "We were stuck on ADSL1 tech. Web server quotas eaten up by anti-spam logs." "It was great when we started, but there are better choices today."
| Pre Sales information:
Install Co-ordination:
Connection reliability:
Tech Support:
Services:
Value for money:
|
We switched to Raw Bandwidth ADSL in 2000 after a nightmarish experience with @Home (remember them? I wish I could forget!). Mike Durkin apparently runs the whole show himself. It was a relief after hours on hold with @Home "idiot deflectors" to talk directly to the guy running the network. In our first months with the service, we even got a response from Mike on Thanksgiving day!
We are ~12000' from the CO, so we never had more than 1.5M down/128K up. But that was nearly rock-solid. Most connection outages were due to a known issue with our modem, the Westell Wirespeed. Power-cycling the modem usually fixed them. I can think of 3 occurrences in 10 years where the network problem was on Raw Bandwidth's end - and these were fixed promptly.
I have large photo galleries on my web site, and I started bumping up against the storage quotas. Mike switched me to their new server with twice the quota - 500 MB. This was fine for a while but then I started hitting the quota again. Came to find out that I had 100+ MB of spam filter logs in a hidden directory! I was never told about the new filtering tech, so that came as a shock.
I was willing to pay the premium over consumer-grade ADSL for quite a while. But between the spam logs that need constant cleanup, the low storage quotas, and the advent of Sonic.net's inexpensive Fusion service, I decided it is time to move on.
Comments:
 mdurkin
join:1999-08-11
San Bruno, CA | spam filtering at Raw Bandwidth is with full disclosure The spam filtering you're referring to is spamassassin. On our system, it defaults to off and is only turned on when a customer goes to the control panel and turns it on. It was a very conscious decision of ours not to apply RBLs, blacklists, and other filtering to customer's incoming email without their full knowledge and consent. We do some greylisting system wide, only when keyed off some RBLs that suggest machines that shouldn't be sending email direct to us; greylisting has an extremely low risk of false positives, generally only delays some email.
The filtered mail folder for spamassassin isn't in a hidden file, it's described on the control panel page and is in the same directory under users' home directories that other IMAP folders live in. The control panel also provides the option to have email tagged and delivered to the inbox (which is not subject to disk quota) so you can download and filter based on the tag on the desktop client, rather than put it into the folder on the server. So you may not have remembered about the filtered mail folder, but it would have been disclosed to you when you enabled the filters. | |
|
| |
|
