Not getting our email?

I just replied to a user wanting more information about SpamButcher. I promptly got the following bounce message back:

   ----- The following addresses had permanent fatal errors -----

    (reason: 553 Sorry, UCE is not allowed on this network. RT#301262)

   ----- Transcript of session follows -----
... while talking to mx01.kw.com.:
>>> >>> RCPT To:<---@--.com>
<<< 553 Sorry, UCE is not allowed on this network. RT#301262
550 5.1.1 <-----@--.com>... User unknown

This isn't the first time I've had this kind of problem. At least once a month or so I come across users who simply don't seem to get our email.

We keep our noses pretty clean at SpamButcher. If you check major blacklists for our email server - you won't find it. We have a strong policy against sending unsolicited email.

We also know how to keep our emails free of "trigger" phrases that might set off an anti-spam utility. There really shouldn't be any reason for our email to go missing.

Still, we encounter customers who claim they never got their serial number, or that we don't answer their support requests. When the problem becomes apparent - we'll send the message via a non-SpamButcher account. This always seems to solve the issue.

So why would anyone block email from SpamButcher? One word: spam.

Many server filters and some email applications give users the option to "label" suspected spam as "spam". The content filter may actually insert the word "SPAM:" into the subject tag.

Users can then configure their email program to deal with such messages as they please. A hypothetical Outlook antispam setup might move all such labeled messages to the junk folder. This also lets server administrators setup a single configuration server-side - and leave it up to individual users to handle labeled messages as they please.

But what happens when a message is sent with the subject, "Your SpamButcher Purchase Information?" Depending on how the user's email program is setup - it may never be seen.

Back