openSUSE admin

pjessen wrote in #note-1:

I'm going to check on those 579 other bounces, it seems like quite a lot, but I think the issue here is -

Those 579 are all bounces going back to 2021-04-27. The mail log on progressoo never grows big enough to be rotated. Counting only October 2023, there has been 144 bounces.

pjessen wrote in #note-2:

Counting only October 2023, there has been 144 bounces.

The usual bounce reasons -

• unknown address
• spam rejected (@pjessen @crameleon @wrosenauer plus many others)

Does redmine have some built-in mechanism for dealing with this sort of thing, e.g. in the style of mailman?

pjessen wrote in #note-2:

pjessen wrote in #note-1:

I'm going to check on those 579 other bounces, it seems like quite a lot, but I think the issue here is -

Those 579 are all bounces going back to 2021-04-27. The mail log on progressoo never grows big enough to be rotated. Counting only October 2023, there has been 144 bounces.

That sure is a long ping-pong match 😁

redmine sends out notifications etc with envelope address redmine@opensuse.org - that probably ought to be improved

We can change the From (envelope?) address, but it's referenced in several places (mostly Postfix rewrite maps on multiple machines), which might lead to regressions.

Does redmine have some built-in mechanism for dealing with this sort of thing

I doubt it. The mail handler is a relatively rudimentary Ruby script which takes an email and forwards it to Redmine using the HTTP API:

https://github.com/redmine/redmine/blob/master/extra/mail_handler/rdm-mailhandler.rb

Those 579 are all bounces going back to 2021-04-27

I do want to point out that until recently progressoo.i.o.o was only running https://progress-test.opensuse.org (now defunct). I repurposed the machine to run the new production setup. Hence such old mail entries are likely not from the currently running Redmine instance.

that probably ought to be improved on such that bounces can be recognised as such.

Would it help to add some code to the Ruby script which just drops bounced emails? If so, is there a good programmatic way to detect such an email based on what data is injected by Postfix?

Edit: I now added -v to the command line which should dump the data to the journal next time.

crameleon wrote in #note-7:

that probably ought to be improved on such that bounces can be recognised as such.

Would it help to add some code to the Ruby script which just drops bounced emails?

If redmine can't process NDRs anyway (I was not aware), we might as well throw them away.
That sounds like something for postfix to do. IOW, "drop anything for redmine that doesn't have a proper sending address". I can do that.

If so, is there a good programmatic way to detect such an email based on what data is injected by Postfix?

Envelope address = <> (empty).

That sounds like something for postfix to do. IOW, "drop anything for redmine that doesn't have a proper sending address". I can do that.

If that's possible in Postfix, that'd be even better - no hacky patching of the script. :-) Let me know what it is you configure, so I can add it to Salt.

pjessen wrote in #note-10:

Let me know what it is you configure, so I can add it to Salt.

Willdo. I am just testing a solution, it is a simple sender check.

Old: smtpd_sender_restrictions = lmdb:/etc/postfix/access,reject_unknown_sender_domain
New: smtpd_sender_restrictions = lmdb:/etc/postfix/discard_ndrs,reject_unknown_sender_domain

Contents of /etc/postfix/discard_ndrs:

# poo#138290 discard ndrs etc.
<>      discard

This is a log excerpt:

2023-10-21T10:35:23.271296+00:00 progressoo postfix/smtpd[24532]: connect from mx1.infra.opensuse.org[192.168.47.95]
2023-10-21T10:35:23.281293+00:00 progressoo postfix/smtpd[24532]: NOQUEUE: discard: RCPT from mx1.infra.opensuse.org[192.168.47.95]: <>: Sender address triggers DISCARD action; from=<> to=<redmine+admin@progressoo.infra.opensuse.org> proto=ESMTP helo=<mx1.infra.opensuse.org>
2023-10-21T10:35:23.290794+00:00 progressoo postfix/smtpd[24532]: 46EDF3A92: client=mx1.infra.opensuse.org[192.168.47.95]
2023-10-21T10:35:23.291890+00:00 progressoo postfix/smtpd[24532]: disconnect from mx1.infra.opensuse.org[192.168.47.95] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5

Thank you for the implementation and the details, Per.

syscid.com - This message does not meet our delivery requirements

That's my server!

I'm not sure it's related to this ticket, but the tracker is very quiet in the last days and two users report having sent emails to admin@o.o which I cannot locate in the queue. Did anything go wrong? The only email related change I performed was removing "infra." from "myhostname" on mx1.

crameleon wrote in #note-14:

I'm not sure it's related to this ticket, but the tracker is very quiet in the last days and two users report having sent emails to admin@o.o which I cannot locate in the queue. Did anything go wrong? The only email related change I performed was removing "infra." from "myhostname" on mx1.

Looks like anna is having trouble talking to progressoo.

2023-10-31T18:48:41.037648+00:00 anna postfix/error[29947]: 05E372151A: to=<redmine+admin@progressoo.infra.opensuse.org>, relay=none, delay=0.01, delays=0.01/0/0/0, dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to progressoo.infra.opensuse.org[192.168.47.34]:25: Connection timed out)

Yep, just retried, it is timing out.

The timeout is odd, the attempts from anna do show up:

Oct 31 15:48:30 progressoo postfix/smtpd[1256]: connect from mx1.infra.opensuse.org[192.168.47.95]
Oct 31 15:48:30 progressoo postfix/smtpd[1256]: NOQUEUE: discard: RCPT from mx1.infra.opensuse.org[192.168.47.95]: <>: Sender address triggers DISCARD action; from=<> to=<redmine+admin@progressoo.infra.opensuse.org> proto=ESMTP helo=<mx1.opensuse.org>
Oct 31 15:48:30 progressoo postfix/smtpd[1256]: F121D453A: client=mx1.infra.opensuse.org[192.168.47.95]
Oct 31 15:48:30 progressoo postfix/smtpd[1256]: disconnect from mx1.infra.opensuse.org[192.168.47.95] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5
Oct 31 18:54:21 progressoo postfix/smtpd[22518]: connect from anna.infra.opensuse.org[192.168.47.102]
Oct 31 18:54:26 progressoo postfix/smtpd[22518]: disconnect from anna.infra.opensuse.org[192.168.47.102] quit=1 commands=1

crameleon wrote in #note-16:

The timeout is odd, the attempts from anna do show up:

Oct 31 15:48:30 progressoo postfix/smtpd[1256]: connect from mx1.infra.opensuse.org[192.168.47.95]
Oct 31 15:48:30 progressoo postfix/smtpd[1256]: NOQUEUE: discard: RCPT from mx1.infra.opensuse.org[192.168.47.95]: <>: Sender address triggers DISCARD action; from=<> to=<redmine+admin@progressoo.infra.opensuse.org> proto=ESMTP helo=<mx1.opensuse.org>
Oct 31 15:48:30 progressoo postfix/smtpd[1256]: F121D453A: client=mx1.infra.opensuse.org[192.168.47.95]
Oct 31 15:48:30 progressoo postfix/smtpd[1256]: disconnect from mx1.infra.opensuse.org[192.168.47.95] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5
Oct 31 18:54:21 progressoo postfix/smtpd[22518]: connect from anna.infra.opensuse.org[192.168.47.102]
Oct 31 18:54:26 progressoo postfix/smtpd[22518]: disconnect from anna.infra.opensuse.org[192.168.47.102] quit=1 commands=1

Yeah, I just ran a tcpdump - I think this is my fault. I changed the smtp_bind_address on anna - I'm going to comment out for now, then look at it tomorrow.

pjessen wrote in #note-17:

Yeah, I just ran a tcpdump - I think this is my fault. I changed the smtp_bind_address on anna - I'm going to comment out for now, then look at it tomorrow.

Mea culpa. I was too fast - the bind address really does need setting, but only for external deliveries.