[EMAIL PROTECTED] wrote:
Received: from host-212-158-194-14.bulldogdsl.com (HELO
phoenix.example.com) (212.158.194.14)
by secure.example.name with (DHE-RSA-AES256-SHA encrypted) SMTP; 1 Jul
2005 10:00:52 +0100
What SMTP service generates this header?
phoenix.example.com is a machine NATted by my DSL router. example.com,
secure.example.com, server.example.info and example.info are all domains
and hostnames identifying my main server.
My mail was handed from my dynamic DSL IP, to my own mail-server(
secure.example.com ), which is configured as the SMTP server on my mail
clients. What can I do to prevent SpamAssassin from triggering mails
sent between users of domains hosted on my server, yet still retain the
DUL list checks for all other mails?
If you can use SMTP auth (which I really hope you are, or are at least
using an IP based auth list) and if whatever server you are using will
place a supported auth token in the received header your problem will
magically go away (actually SpamAssassin will automatically extend the
trust boundary to authenticated clients).
Note that the (DHE-RSA-AES256-SHA encrypted) token isn't used since it's
not an authentication token. You want to see something like
"authenticated user" or "authenticated x bits" immediately before the
"by" section of the header or "ESMTPA", "ESMTPSA", "LSMTPA", "LSMTPSA"
or "HTTP" as the "with" method.
Daryl
