openSUSE admin

mlmmj would only report "bouncing messages" if a message had actually bounced :-) While your mailserver was in trouble, any list messages would have been queueing on anna, maybe anna decided to bounce something? Your log snippet shows a message being deferred, not bounced.

An alternative might be to change delay_warning_time = 1h on anna to a higher value so that mlmmj doesn't get too many delay notifications.

anna is used for other relaying isn't it? "0h" would disable it. I don't think mlmmj cares about those notifications anyway.

Since midnight, anna sent out 73 delay notificaitons - I see some for your address, some for others. mlmmj just ignores them.

cboltz wrote:

Since midnight, anna sent out 73 delay notificaitons - I see some for your address, some for others. mlmmj just ignores them.

I'm afraid reality disagrees ;-)

Hmm, they are processed by mlmmj-receive, but there are no log entries (mlmml.operation.log). Still, you're right, reality disagrees.
I guess I was too optimistic that mlmmj would understand :-(

My guess is that:

• mlmmj sends the mail to anna, envelope sender opensuse-de+bounces-105611-suse=cboltz.de@opensuse.org
• anna gets a 4xx tempfail (or connection refused, which is also a tempfail)
• after an hour, anna sends a "delay warning" message to opensuse-de+bounces-105611-suse=cboltz.de@opensuse.org which gets routed to mlmmj
• mlmmj receives the "delay warning" mail at the bounce address and thinks it was bounced (actually I'd be surprised if mlmmj would parse the mail content)
• mlmmj sends out the "Bouncing messages" notification

That is exactly what happens, yes.

Regarding change delay_warning_time - 0h (= disabling) doesn't sound like a good idea, but increasing it might be a good idea. The alternative is to let baloo send out the mails directly, but that's another can of worms ;-)

I wonder if there might be a way of disabling the delay warning selectively. Or throwing it way.

pjessen wrote:

I wonder if there might be a way of disabling the delay warning selectively. Or throwing it way.

I'm trying out a header check on baloo - only logging a warning sofar:

/THIS IS A WARNING ONLY. YOU DO NOT NEED TO RESEND YOUR MESSAGE/ warn klop99

With this we could just discard those delay warnings. Of course, any posting actually containing that text would also be discarded.

I subscribed to opensuse-test@o.o as opensuse-test-blocked AT cboltz.de and adjusted my postfix config so that this address always says "450 intentionally delayed - poo#51092".

I also sent a mail to opensuse-test@o.o 5 minutes ago, so that you should see something[tm] in the log soon ;-)

(I'll disable the "450" tomorrow evening so that the mail can be delivered.)

BTW:

I'm trying out a header check on baloo - only logging a warning sofar:

/THIS IS A WARNING ONLY. YOU DO NOT NEED TO RESEND YOUR MESSAGE/ warn klop99

Should this really be a header check? The text looks more like text from the mail body...

I removed the "450" blocking again, and as expected, I got "Bouncing messages from opensuse-test@opensuse.org" notifications - one with timestamp 2:00 CEST, one with timestamp 14:00 CEST.

First log entry for each envelope sender on my server (times are CEST, I removed my mail address for spam protection)

Jul 6 22:17:41 server postfix/smtpd[22497]: NOQUEUE: reject: RCPT from proxy-nue1.opensuse.org[195.135.221.145]: 450 4.7.1 <...>: Recipient address rejected: intentionally delayed - poo#51092; from=<opensuse-test+bounces-189-opensuse-test-blocked=cboltz.de@opensuse.org> [...]

Jul 7 02:00:04 server postfix/smtpd[24484]: NOQUEUE: reject: RCPT from proxy-nue1.opensuse.org[195.135.221.145]: 450 4.7.1 <...>: Recipient address rejected: intentionally delayed - poo#51092; from=<opensuse-test+bounces-probe-opensuse-test-blocked=cboltz.de@opensuse.org> [...]

Jul 7 14:00:04 server postfix/smtpd[17659]: NOQUEUE: reject: RCPT from proxy-nue1.opensuse.org[195.135.221.145]: 450 4.7.1 <...>: Recipient address rejected: intentionally delayed - poo#51092; from=<opensuse-test+bounces-probe-opensuse-test-blocked=cboltz.de@opensuse.org> [...]

The first one is the actual ML mail, the other two are the "Bouncing messages" notifications.

If you want to do more tests, I can switch on the "450" rejects for that address again.

Should this really be a header check? The text looks more like text from the mail body...

No, it probably ought to be a body check, but we don't currently use any. I thought trying with the killfile was worth testing.
I'm moving the check to a body_check, still with a warning.

cboltz wrote:

If you want to do more tests, I can switch on the "450" rejects for that address again.

Yes please switch it on again.

pjessen wrote:

cboltz wrote:

If you want to do more tests, I can switch on the "450" rejects for that address again.

Yes please switch it on again.

Done, you'll get "450" rejects again.

FYI: delayed mails still cause "bouncing messages" warning mails, in my case for some opensuse-security-announce mails.

First delivery attempt: (mail-20190925.xz on anna)

2019-09-24T13:47:24.963808+00:00 anna postfix/smtp[5415]: DFA45226BA: to=<christianboltz@web.de>, relay=mx-ha02.web.de[212.227.17.8]:25, delay=0.05, delays=0.01/0/0.04/0, dsn=4.0.0, status=deferred (host mx-ha02.web.de[212.227.17.8] refused to talk to me: 421-web.de (mxweb113) Nemesis ESMTP Service not available 421-Service unavailable 421-Reject due to policy restrictions. 421 For explanation visit http://postmaster.web.de/error-messages??ip=195.135.221.145&c=irlims)

3 hours (and some delivery attempts) later, the mail was accepted by web.de:

2019-09-24T16:15:57.223381+00:00 anna postfix/smtp[19221]: DFA45226BA: to=<christianboltz@web.de>, relay=mx-ha03.web.de[212.227.15.17]:25, conn_use=7, delay=8912, delays=8911/1.3/0.01/0.05, dsn=2.0.0, status=sent (250 Requested mail action okay, completed: id=1MTh17-1icLdQ0ke5-00U5qP)