spam problems
Jan. 20th, 2004 11:43 pmI've since fixed the mailing list to close that particular loophole, at some inconvenience to some list members. I also sent a message to the list saying, basically, be more careful in targetting your complaints. But it turns out it's only partially the fault of the list member who complained.
AOL makes it very easy for people to complain about spam, even if they didn't mean to. Apparently, the current UI is such that many people accidentally hit the "complain" button when they meant to hit the "delete" button. My sys admin told me of cases where AOL users "complained", presumably erroneously, about messages that they had sent. Talk about bad interface design! Quick, send them some experts in human-computer interaction! Heck, send them any intern from any HCI program.
AOL is huge, and they're certainly not going to investigate every spam complaint. Smaller providers can't afford to do so either. So they'll blacklist sites, usually temporarily, based on complaints, not on investigations. I think it's wrong to target hosts of mailing lists (absent reason to believe that they're being especially reckless), but I suppose this is how things work now. And it's going to get even worse now that the federal government has legalized spam and abolished state laws that limited it.
I'm not sure, but I might have liked it better when the uncertainty in email delivery came from the UUCP chain rather than from blacklists (and black holes). At least then everyone who was using email knew it wasn't necessarily reliable; now people just assume you're ignoring them. Sigh.
But all of this did finally prod me into learning enough about procmail tonight to set up some filtering on my own inbox. The spam has been getting a lot worse in recent months, up from 10-20 messages a day to more like 100. So I finally have candidate spam going to its own folder that I'll check in on from time to time. In the few hours it's been in place it's caught 23 pieces of spam, missed three pieces of spam, and caught no non-spam. So far, so good.
(no subject)
Date: 2004-01-21 02:59 am (UTC)(no subject)
From:(no subject)
From:(no subject)
From:(no subject)
From:(no subject)
Date: 2004-01-21 06:42 am (UTC)In Mary Kay, consultants have an opt-in mailing list. If we add someone to our mailing list, MK sends out one message asking for permission to send them more messages. If they do not respond, or if they say no, MK will not allow us to send messages out to them.
AOL, however, has determined that MK consultants are spamming their customers when we send out email from the marykay domain, and they bounce them.
It would seem that there is nothing MORE right that MK could be doing.
(no subject)
From:(no subject)
Date: 2004-01-21 02:19 pm (UTC)[* I'm not. I like my new shell provider much better.]
(no subject)
From:(no subject)
From:AOL's ludicrous spam policy
Date: 2004-01-23 09:49 am (UTC)This happened to JTan (my shell/email/webhost provider) a few months ago. One Sunday morning I suddenly found I couldn't send email to my girlfriend, who is unfortunately still on AOL. Chris investigated, and discovered that JTan was blacklisted based on "complaints from users". After investigation, the best he was able to detemine wsa that some AOL idiot had signed up for a mailing list hosted on JTan, and then instead of unsubscribing started blocking...
I'm all for improving the user experience, to a point, but when you dumb it down so much that you HURT other people, you've done something wrong.
Re: AOL's ludicrous spam policy
From: