| commit | c1737baf0d8191a817765b36ee0490bb9fb311df | |
| author | Steffen Nurpmeso <steffen@sdaoden.eu> | |
| Wed, 6 Jun 2018 17:29:22 +0000 (6 19:29 +0200) | ||
| committer | Steffen Nurpmeso <steffen@sdaoden.eu> | |
| Wed, 6 Jun 2018 17:31:33 +0000 (6 19:31 +0200) | ||
| tree | 0e831f21a1002f011f505995c3fa6f4ded62e4be | treesnapshot (tar.gz zip) |
| parent | 8a5a123cb82a95386cfe89e335546cb26140c999 | commitdiff |
Do not process From: alternates if Sender: is set (Michael Dressel)..
Another point that i did not get right at first, Michael pointed
out all he wants is really going for what he stated, and put some
receivers in Cc:. It turns out Heirloom and we always took into
account From: in the alternates list automatically, even if Sender:
is explicitly set.
This may even not be false as such, the real problem i have introduced,
and that is that sending performs alternates processing just as does
replying, but only the latter is defined by the standard.
I did not see a real difference in respect to alternates, however.
But according changes cannot be cherry-picked to master, anyhow
Another point that i did not get right at first, Michael pointed
out all he wants is really going for what he stated, and put some
receivers in Cc:. It turns out Heirloom and we always took into
account From: in the alternates list automatically, even if Sender:
is explicitly set.
This may even not be false as such, the real problem i have introduced,
and that is that sending performs alternates processing just as does
replying, but only the latter is defined by the standard.
I did not see a real difference in respect to alternates, however.
But according changes cannot be cherry-picked to master, anyhow
| nam-a-grp.c | diffblobblamehistory |