openSUSE admin

Hello Per,

Am Sonntag, 18. Juli 2021, 10:21:42 CEST schrieben Sie:

[openSUSE Tracker]
Issue #95602 has been updated by pjessen.

Category set to Mailing lists
Status changed from New to In Progress
Private changed from Yes to No

DocB wrote:

Dear Admins,

in the below mail I asked to heroes to investigate why the Board Meeting
reminder is not sent.

As I did not get any reply, and the mail is still not sent, can you pls
investigate?

Hi Axel

the bounce message actually explains it quite well -

Is being held until the list moderator can review it for approval.
The message is being held because:
Message has implicit destination

However, it looks like it was already released.

yes, this was already changed two weeks ago. This this ticket I wanted to
address only the following point:

Wrt to the weekly meeting reminder, it looks like it just needs to have the
appropriate destination in the To: line. There is currently nothing held
for board@lists.o.o

Definition is made in:
https://github.com/openSUSE/mail-reminder/blob/master/data/board-meeting.mail

To: openSUSE Project and Community related discussions
project@lists.opensuse.org

is not valid?

Cheers
Axel

Hello Per,

Am Sonntag, 18. Juli 2021, 17:44:54 CEST schrieb redmine@opensuse.org:

[openSUSE Tracker]
Issue #95602 has been updated by pjessen.

Status changed from In Progress to Feedback

DocB wrote:

.....

To: openSUSE Project and Community related discussions
project@lists.opensuse.org

is not valid?

It looks good, although enclosing openSUSE Project and Community related
discussions in double quotes would be a good idea.

agree, athough the 'From' was working in that way
openSUSE Meeting Reminder no-reply@opensuse.org
all the time....

I also don't see any
held mails on project@lists.o.o - there is one from today and one from 5
July, so I guess the one in between is missing.

I don't see anything on mailman3 nor on mx[12] from you to project@lists.o.o
on 10 or 11 July. If you can let me know roughly when it was sent and
maybe even a message-id, that might help tracking it down.

As per configuration, the mail should have been sent this saturday (17.07.) by
the meeting reminder tool - obviously it was not, as neither on the board, nor
on the project list anything was received

Am Montag, 19. Juli 2021, 10:45:16 CEST schrieben Sie:

[openSUSE Tracker]
Issue #95602 has been updated by DocB.

I also don't see any
held mails on project@lists.o.o - there is one from today and one from 5
July, so I guess the one in between is missing.

I don't see anything on mailman3 nor on mx[12] from you to
project@lists.o.o on 10 or 11 July. If you can let me know roughly when
it was sent and maybe even a message-id, that might help tracking it
down.

As per configuration, the mail should have been sent this saturday (17.07.)
by the meeting reminder tool - obviously it was not, as neither on the
board, nor on the project list anything was received

I had a look at the code, and it seems the tag 'bcc' is not understood:

for key in headers.keys():
if not key in ['From', 'To', 'Subject', 'Reply-To']:
raise ConfigException('Mail template file \'%s\' contains a
non-authorized header: \'%s\'.' % (self.template, key))

-> Do you see the error message somewhere (in a cron-log maybe)?

Is there any chance this might be related:
There is a cronjob on 'pinot': Cron /home/mail_reminder/git/mail-reminder --no-debug which complains:

Mail template file 'board-meeting.mail' contains a non-authorized header: 'Bcc'.

Looks like it's been complaining since 30 June. I guess someone changed the template - the only permitted headers are: From, To, Subject and Reply-To. Looking at "/home/mail_reminder/git/data/board-meeting.mail" it was changed on 22 July, so someone already found and fixed this issue.

Hello Per,

Am Samstag, 24. Juli 2021, 10:40:14 CEST schrieben Sie:

Is there any chance this might be related:
There is a cronjob on 'pinot': Cron
/home/mail_reminder/git/mail-reminder --no-debug which complains: ~~~
Mail template file 'board-meeting.mail' contains a non-authorized header:
'Bcc'. ~~~
Looks like it's been complaining since 30 June.

Thank you, that confirms my assumption that the bcc was not permitted.
This is fixed in between, we dont need that mail anymore

Thank you!
Axel

DocB wrote:

I did not receive it
Schöne Grüße
Axel

Hi Axel

Looking at pinot, the reminder was sent 2021-07-31 11:42 UTC, to board@lists.o.o and project@lists.o.o, both relayed via anna (192.168.47.4), queue id BC9121FF6C. anna sent them to mx1, queue id D37034FF0. mx1 sent them to mailman3, queue id 550EE7DA. Here it was sent to the board list (7 recipients), again via anna. Unfortunately, your copy was rejected by your provider:

554-Transaction failed 
554-Reject due to policy restrictions. 
554 For explanation visit https://www.gmx.net/mail/senderguidelines?ip=195.135.221.145&c=hi

It also looks like it was correctly sent to project@lists.o.o, I see it myself. Your copy was again rejected by gmx.

I don't see the reminder in the project list archive though, and I guess the board list is not being archived.

pjessen wrote:

554-Transaction failed 
554-Reject due to policy restrictions. 
554 For explanation visit https://www.gmx.net/mail/senderguidelines?ip=195.135.221.145&c=hi

I wonder if that might be because the reminder mail does not have a To: header.

Thanks for your analysis, Per!
There were indeed some mails already missing in my inbox from oS lists...seems that GMX is not reliable anymore
From the project@ email archive I cant really see what is missing.
The change for the mail reminder was just that we now have 2 recipients: project + board.
And a recipient is set:
toaddrs = [ addr for (name, addr) in email.utils.getaddresses([ headers['To'] ]) ]

I will open an issue for the reminder mail....

DocB wrote:

Thanks for your analysis, Per!
There were indeed some mails already missing in my inbox from oS lists...seems that GMX is not reliable anymore

They do seem to be a little strict with the spam filtering, yes. On the other hand, I saw many other mails being normally delivered to your address.

From the project@ email archive I cant really see what is missing.

I don't know why the mail was not archived, but it is probably also related to the missing 'To' header. (just guessing)