Sameer N Ingole wrote:
Claudio Jeker wrote:
On Mon, Sep 19, 2005 at 06:23:05PM +0530, Sameer N Ingole wrote:
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
I am trying to find a solution on reconfiguring spamassasin. In the
meanwhile
does anyone here have any solution on this as to how I can modify that
header
field?
(till I find answer to my question, its time to research again..!)
Regards,
Hi!
I did some research ;-)
I don't know what tests your spamassassin setup does.
What you probably want is, that after successful authentication SA
should match ALL_TRUSTED, even if you don't know the client IPs (no
chance for having them in trusted_networks).
What you can do right now is setting env AUTHPREPEND="authenticated as:"
(matches case 1 below, according to
/../Mail/SpamAssassin/Message/Metadata/Received.pm)
###
# try to catch authenticated message identifier
# the first one works for Sendmail, MDaemon, some webmail servers, and
others
# the second one works for Critical Path Messaging Server
# with ESMTPA, ESMTPSA, LMTPA, LMTPSA should cover RFC 3848 compliant MTAs
# with ASMTP (Authenticated SMTP) is used by Earthlink, Exim 4.34, and
others
# with HTTP should only be authenticated webmail sessions
...
###
What qmail-ldap could do, would be following RFC 3848.
instead of: "by mail.xxx.at (qmail-ldap-1.03) with AES256-SHA encrypted
SMTP"
add:
=> with ... ESMTPA for authenticated users
=> with ... ESMTPSA for authenticated users over starttls
Regards,
Manfred
