Once upon a time, Cyril - ImprovMX <[email protected]> said:
> Just to clarify, I'm not trying to pin some issue on a company (Google) but
> I'm trying to understand why aiosmtpd seems to follow an RFC that
> appears to be clear on the behavior, that GMail doesn't do but doesn't
> appear to be the only one (as my user is generating a document that also
> doesn't seems to follow it).
>
> I'm more thinking about a different interpretation on the RFC that leads to
> various behavior between aiosmtpd and (some) others.
You have only looked at half of the two related pieces about lines which
start with a dot (you quoted the the "remove a leading dot" piece). The
other half of the puzzle is that when transmitting a message via SMTP,
the sender is required to ADD a leading dot to any line with a leading
dot (that is then, per the RFC section you quoted, removed by the
receiver).
If your sending software is not adding the second dot to lines that
already start with a dot, that is your problem.
Basically, if you have a line in your original message that looks like
(indented JUST to make it clear):
.example.com
then when it is actually being transmitted via SMTP, the sender changes
it to:
..example.com
and then the receiver strips the leading dot to make it:
.example.com
as originally written.
--
Chris Adams <[email protected]>
_______________________________________________
mailop mailing list
[email protected]
https://list.mailop.org/listinfo/mailop
