On Mon, Sep 19, 2005 at 06:23:05PM +0530, Sameer N Ingole wrote: > Hi, > > What smtp should add to Received: header field when it relays a > mail after smtp-auth. > > As I observed, it adds the mail client's IP or host name to > Received: header field. When I tried to find what exactly it should > add, I end up finding this: > > ---- RFC 1869 [SMTP Service Extensions] --- > > 7. Received: Header Field Annotation > > SMTP servers are required to add an appropriate Received: field to > the headers of all messages they receive. A "with ESMTP" clause > should be added to this field when any SMTP service extensions are > used. "ESMTP" is hereby added to the list of standard protocol names > registered with IANA. > > ---- end RFC 1869 text ---- > > Here I found is pretty obscure as what *add an appropriate Received: field* > means. What should smtp add? The IP or host name of email server on which > smtp relay is or IP or host name of smtp client? Is this decision left to > smtp server? > > All this is because I have qmail-ldap running with smtp-auth. When a user > send an email to user on same domain, email comes with Received: header > field added with sender's ISP's IP or host name. Most of the times this > IP is in several BLs. The spamassassin running on the servers then > attributes this mail as spam whereas it is not. Now how do I deal with > it? Is it some misconfiguration in qmail-ldap or it is normal behavior? >
This is a misconfiguration of spamassasin. We will not modify reveived lines just because spamassasin is dumb, especially it will hurt many others that try to find out what "route" a mail is taking but fail to track it because some IPs are modified or missing -- :wq Claudio
