From: "Jerome Mainka" <[EMAIL PROTECTED]>
Le Mercredi 19 Octobre 2005 21:13, Matt Kettler a écrit :
Jerome Mainka wrote:
> OK, I understand that. But the why is it offending to send a mail from a
> dynamic address?
It's not, it's only offensive to send it from a dynamic IP directly to a
trusted server.
OK. (Sorry if I am a little slow to understand the rationale behind all
that.)
These days the "notfirsthop" tests are applied to the first untrusted IP
delivering mail to a trusted server.
OK. In my case, it means that because mwinf0107.wanadoo.fr is considered
internal/trusted, the address 193.251.71.180 is illegitimate to delivering
mail directly to it.
But if I remove mwinf0107.wanadoo.fr from the trusted networks set, I have
the
same behavior. Actually, if I empty the internal/trusted networks set, I get
the same behavior. What is wrong with this path?
193.251.71.180 (dialup) -> mwinf0107.wanadoo.fr (its smtp server) ->
127.0.0.1
-> mwinb0504 (which has no ip and no fqdn)
The sender and the recipient belong together to the same provider, and the
final server of the received path is not the host on which SA is run.
Thank you for your help and sorry for my poor english (and my poor
understanding of the process...)
<< Do not send directly. Send through your ISP's mail service. That is
<< about the only way to avoid the dialup problem you are having. You ARE
<< on a dialup address. So you get tagged that way when you try to send
<< email directly.
{^_^}
