> Viktor Dukhovni via Postfix-users <[email protected]>:
>
> On Thu, Dec 11, 2025 at 01:55:16AM +0100, Gerald Galster via Postfix-users
> wrote:
>>
>>> Viktor Dukhovni via Postfix-users <[email protected]>:
>>>
>>> On Thu, Dec 11, 2025 at 12:55:53AM +0100, Gerald Galster via Postfix-users
>>> wrote:
>>
>> And the error case would look like this:
>>
>>> postfix/bounce[]: 4dRQzN6pXBzVHYR: sender non-delivery notification:
>>> message content rejected
>>
>> How shall a parser best distinguish a queue id from a possibly variable
>> error message?
>
> The message could be subtly different, perhaps one of:
>
> postfix/bounce[]: <queue-id>: sender non-delivery notification message
> content rejected
> postfix/bounce[]: <queue-id>: sender non-delivery message content rejected
> postfix/bounce[]: <queue-id>: rejected: sender non-delivery notification
> message
> ...
That would be great, thanks. I'll see your final choice in the changelog then.
> Of course the real solution is to NOT configure your MTA to reject
> bounces. And perhaps send header-only boucnes, to reduce the chance
> that the body will trigger filters.
>
> If your system reports this sort of message, the problem isn't its
> syntax, it is the fact this is happening at all.
True and I've checked that I'm not affected, but I'd like to know what to expect
to keep my parsers from crashing, leaking memory or adding garbage to the
database.
Best regards,
Gerald
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
