On Mon, 23 Feb 2004, Jonathan Nichols wrote:
>
> Here's the big problem. Big company, lots of Exchange servers, some that
> aren't set up to send an FQDN as a HELO.
>
> The result:
> Feb 23 10:04:16 mailgate postfix/smtpd[16182]: 71DBD13FF3: reject: RCPT
> from mail.rt.firstam-reis.com[206.103.66.185]: 404 <reisdal01smxs01>:
> Helo command rejected: need fully-qualified hostname;
> from=<[EMAIL PROTECTED]> to=<[EMAIL PROTECTED]> proto=ESMTP
> helo=<reisdal01smxs01>
>
> That's a valid sender, to a valid domain, but the Exchange server just
> sends its hostname as the HELO. I have tried without success to contact
> the powers-that-be to change that.
[snip..]
You do realize that the rejection is due to your postfix
configuration, SpamAssasssin has nothing to do with it.
SpamAssasssin by itself is not capable of rejecting anything.
Reconfigure your postfix to not block based upon the HELO and then
work on your SpamAssasssin config to do the tagging.
--
Dave Funk University of Iowa
<dbfunk (at) engineering.uiowa.edu> College of Engineering
319/335-5751 FAX: 319/384-0549 1256 Seamans Center
Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527
#include <std_disclaimer.h>
Better is not better, 'standard' is better. B{
