Michael R. Brumm wrote:
Teddy, FYI, your message to the list had the following in its headers:
Received-SPF: fail (mail.teddy.ch: domain of teddy(_at_)teddy(_dot_)ch does not
designate 62.167.122.90 as permitted sender) receiver=mail.teddy.ch;
client_ip=62.167.122.90; envelope-from=teddy(_at_)teddy(_dot_)ch;
Yes, I know that. It is because I send my mail from a DSL-line to my
mailserver with SMTP AUTH. So of course it is a fail. My mailserver
(which is listet as permitted sender) then sends the mail to the recipient.
What should I do to prevent this? Hide the headers if it is a fail like
this?
Why do you want to add a paramater SUBMITTER to the MAIL FROM command
instead of adding a new command SUBMITTER to the ESMTP protocol? So we
can check if a server understands SUBMITTER at the EHLO command.
This is only because some MTAs that are not patched have problems with
SUBMITTER in the MAIL FROM command.
I personally think that a LOT more analysis on whether it should be a MAIL FROM
parameter OR a separate command should be done. Simply announcing it as a
parameter without examining impact on existing systems is a bad idea. It may
have fewer adverse affects on SMTP sanitizers, and be easier to implement on
MTAs, as a command.
Yes, you are right it is also the implementation that is easier, not
only the error of old MTAs.
Has someone any arguments for or against the parameter in MAIL FROM or a
new command?
Teddy