I was merely hoping that the problem was something we could directly effect, like a missing RDNS entry. AOL users complaining that our customers are spamming them is probably not unfounded or unwarrented, unfortunately.
We provide a web based Outlook replacement for recruiting companies. Our clients commonly email candidates telling them about new jobs, etc. I'm sure their email borders on spam, and I'm sure they are not great about taking people off their lists when they actually land a job.
If I were one of their candidates, I would probably block them as spammers, too. I just wish that AOL would not block the message, in favor of delivering it to a special spam folder. At least this would allow the user to choose whether they wanted to see it.
Anyone else have to deal with a customer base in the spamming grey area?
-Chase
Network and Systems Engineer
Bullhorn, Inc.
p. 617.464.2440 ex 119
m. 617.512.0326
www.bullhornstaffing.com
-----Original Message-----
From:R. Scott Perry [EMAIL PROTECTED]
To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>;
Sent: Apr 20, 2004 07:12:32 AM
Subject: RE: [IMail Forum] AOL - Reverse DNS Rejections
From:R. Scott Perry [EMAIL PROTECTED]
To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>;
Sent: Apr 20, 2004 07:12:32 AM
Subject: RE: [IMail Forum] AOL - Reverse DNS Rejections
>So are you saying that the RDNS results at dnsstuff for bullhorn.com don't
>matter? They do indeed generate a failure, but I'm unclear as to whether
>this is a test an actual mail server would use.
That is correct, in this case. Specifically, the E-mail is being sent from
an IP other than the one(s) in the MX record. If the IP address(es) that
are actually sending the mail have reverse DNS, AOL will happily accept the
mail. Unless there is another problem, as is the case here (AOL apparently
received spam complaints from users).
>All our mail comes from outbound3.bullhorn.com, but this is not a
>registered mail server for bullhorn.com. This is because we have seperate
>incomming and outgoing mail servers. Would AOL look at our connecting
>mailserver (outbound3.bullhorn.com) and do an MX lookup for bullhorn.com?
No.
>If so, outbound3.bullhorn.com would not be one of the servers that came
>back. Is this what they mean by a RDNS failure?
No.
>Is it ok to have seperate incomming and outgoing email servers in general?
Yes.
However, it does worry me that you are completely overlooking this:
>>Diagnostic-Code: smtp;554-: (RLY:BD)
>>http://postmaster.aol.com/guidelines/bulk_email.html The mail server you
>>are using to send mail to AOL has been identified as a source of spam. If
>>you believe this message is in error, please have your mail administrator
>>contact AOL at 888-212-5537.
>
>AOL is telling you that your IP has been identified as a source of
>spam. That's the problem.
AOL you identified you as a spammer, yet all you seem to be concerned about
is your reverse DNS entry. Please re-read and then re-read again the above
details.
-Scott
---
Declude JunkMail: The advanced anti-spam solution for IMail mailservers
since 2000.
Declude Virus: Ultra reliable virus detection and the leader in mailserver
vulnerability detection.
Find out what you've been missing: Ask for a free 30-day evaluation.
---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html
List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
