Previously we were only checking total size but then silently dropping the
emails ( not on purpose but as result of the long local-part ). So we start
to enforce the limits pre-queueing.
Giving the nature of these messages, I think we will rewrite the
offending address coming from *.bounces.google
Long senders are almost always a version of VERP, encoding information
about where the mail comes from so bounces can be attributed directly.
When we were writing a different one, we went through several iterations
including having it case sensitive, to try and keep it shorter. There were
a lot m
On 10 Jul 2018, at 8:43 (-0400), David Hofstee wrote:
Hi José,
More do it, but not that many. Some will just clip the local part.
In the hierarchy of very wrong mail behaviors, "clipping" a local part
is deeper in the muck than using overlong local parts or rejecting them.
On 10 July 2018
Hi José,
More do it, but not that many. Some will just clip the local part.
David
On 10 July 2018 at 14:16, Jose Borges Ferreira wrote:
> I'm getting some notifications from @docos.bounces.google.com that have a
> local-part with the following pattern 1234567890123+
> 123456789012345678901234
