Bug 256326 - Bounce received on current@
Summary: Bounce received on current@
Status: Open
Alias: None
Product: Services
Classification: Unclassified
Component: Mailing Lists (show other bugs)
Version: unspecified
Hardware: Any Any
: --- Affects Only Me
Assignee: postmaster
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-06-01 08:11 UTC by Daniel Ebdrup Jensen
Modified: 2021-06-24 06:40 UTC (History)
1 user (show)

See Also:


Attachments
Raw mail file (10.34 KB, application/mbox)
2021-06-01 08:11 UTC, Daniel Ebdrup Jensen
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Ebdrup Jensen freebsd_committer 2021-06-01 08:11:56 UTC
Created attachment 225442 [details]
Raw mail file

I'm not exactly sure what happened here, but the script (in freefall.freebsd.org:/home/debdrup/freebsd-quarterly/tools/sendcalls) that sends out quarterly calls apparently got a message bounced from freebsd-current, despite not sending to the address in question.

I've attached the raw email, in case you wanna have a look at it.
Comment 1 Philip Paeps freebsd_committer 2021-06-01 08:22:12 UTC
Thanks for reporting this.

current@ is subscribed to quarterly-calls@.  This setup worked under Mailman but apparently it makes mlmmj cranky.

We'll look into this and see if it can be fixed.  Good catch!
Comment 2 Daniel Ebdrup Jensen freebsd_committer 2021-06-15 07:48:41 UTC
I just got another email for the second reminder, so this is still happening.
Comment 3 Daniel Ebdrup Jensen freebsd_committer 2021-06-15 07:51:35 UTC
I just noticed that this also happens for hackers@, and it happened last time too. Do I need to submit anything more?
Comment 4 Philip Paeps freebsd_committer 2021-06-15 08:27:20 UTC
We haven't had a chance to fix this yet.  Both current@ and hackers@ have the same problem and the fix will be identical.
Comment 5 Baptiste Daroussin freebsd_committer 2021-06-21 08:15:36 UTC
I really don't like it, but I did activate the "tocc" flag in mlmmj which allows to send an email to a lists which is not listed in the To field nor the CC field.

Imho this is still wrong, and we should not do that at all... Anyway that should fix the current situation
Comment 6 Baptiste Daroussin freebsd_committer 2021-06-21 08:21:42 UTC
To be honnest, I would like explanation on why this has been done in the first place, and see how we can work on preventing us to have this flag activated on the mailing lists. I really dislike the gates this flag to open, and want to remove it ASAP. I have been adding it, to unlock the current situation, but this need to be considered as temporary.
Comment 7 Baptiste Daroussin freebsd_committer 2021-06-22 09:59:17 UTC
I have made a pull request to the tool which sends the email and remove the workaround I have put in place on the mailing lists.

if you want the mail to go through current@ and hackers@ it needs to use the patched version of the sender.
Comment 8 Daniel Ebdrup Jensen freebsd_committer 2021-06-22 11:39:45 UTC
I've pulled it and tested with sendcalls -t on freefall, and both hackers and current are included in the recipients, so it looks to me as if it works?
Comment 9 Daniel Ebdrup Jensen freebsd_committer 2021-06-24 06:40:54 UTC
I just received a few more emails, this time one from freebsd-office and freebsd-emulation, as well as two more from freebsd-hackers - nor does it look like the change to the sendcalls script worked, since nothing appears to have been sent to the mailing lists when I check the online archives.