Re: [Mailman-Users] Why are mails not being sent to all users (mails seem to disappear)?
Am 31.05.19 um 02:46 schrieb Steven D'Aprano: > On Thu, May 30, 2019 at 07:22:38PM +0200, Till Dörges wrote: > >> I figured it out. And it was neither a Mailman nor a Postfix problem. >> >> systemd-journald simply enforced some rate limiting. After removing it >> (setting >> RateLimitBurst=0 in /etc/systemd/journald.conf), delivery for all mails can >> be seen >> in the logfiles. > > Are you saying that the emails actually were sent, but systemd dropped > the log messages so you wrongly thought they weren't sent? That was the case. Only the log messages in syslog were missing. To be clear: AFAICT everything was working as configured. Regards -- Till -- Dipl.-Inform. Till Dörges doer...@pre-sense.de PRESENSE Technologies GmbHSachsenstr. 5, D-20097 HH Geschäftsführer/Managing Directors AG Hamburg, HRB 107844 Till Dörges, Jürgen Sander USt-IdNr.: DE263765024 -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Easy question for this crowd
Well, it was worth a try. :-/ About 12 hours after I put that RE in place, I got another one from a different domain in '.icu'. It was held for moderation, not automatically discarded. I have: 8 email addresses in accept_these_nonmembers 0 email addresses in hold_these_nonmembers 0 email addresses in reject_these_nonmembers ^@.*\.icu$ in discard_these_nonmembers 'Hold' for generic_nonmember_action 'Yes' for forward_auto_discards but it seemed to make no difference; the UCE was still held for moderation. I'm going to try putting "from: .*@.*\.icu" in header_filter_rules and see if that makes any difference. Any other ideas? -Chip- On 5/30/2019 7:03 PM, Robert Heller wrote: At Thu, 30 May 2019 11:57:44 -0400 Chip Davis wrote: I've supported a dozen Mailman listservers for over a dozen years. This doesn't represent much real effort most of the time. I've had to block specific users often and specific domains rarely, but this is the first time I've had to block an entire TLD. Recently I've been gifted with an inordinate amount of UCE from many different domains under the '.icu' TLD. Since Python RE's are _almost_ the same as the UNIX RE's I used many years ago, if I put ^@.*\.icu$ in discard_these_nonmembers, will it block all domains in that TLD? Yes. And not block anyone else? Yes. I've done this, and then I took things a step further: What *I* have done (because I can), is configure rejection of both domains AND cidrs at the Postfix level, putting REJECT's in both /etc/postfix/access and /etc/postfix/cidr.clients. (I use *REJECT* for a reason: I figure if these idiots are going to make trouble for me, I'll make trouble for them -- eg now they will will get reject messages. Also when the addresses are from legit mail servers, the admins there will get a wake up call and presumably do something -- I have discovered that there is really little point in sending anything to the [so-called] 'abuse' addresses.) I've also configured mimedefang and spamassassin to *reject* spam at the Postfix as well. Very little gets though now. Thanks, -Chip Davis- Mailman 2.1.27 > shared host linux 2.6.32-696.18.7.el6.x86_64 cPanel 80.0.10 -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/heller%40deepsoft.com -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Why are mails not being sent to all users (mails seem to disappear)?
On 5/30/19 7:46 PM, Steven D'Aprano wrote: > Or that systemd prevented the emails from being sent in the first place, > and didn't log the fact that it had done so? I don't think systemd metastasized its own smtpd just yet, so it probably can't do that. Fear not, though, it has its own DNS resolver already, I'm sure it won't take long. -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Why are mails not being sent to all users (mails seem to disappear)?
On Thu, May 30, 2019 at 07:22:38PM +0200, Till Dörges wrote: > I figured it out. And it was neither a Mailman nor a Postfix problem. > > systemd-journald simply enforced some rate limiting. After removing it > (setting > RateLimitBurst=0 in /etc/systemd/journald.conf), delivery for all mails can > be seen > in the logfiles. Are you saying that the emails actually were sent, but systemd dropped the log messages so you wrongly thought they weren't sent? Or that systemd prevented the emails from being sent in the first place, and didn't log the fact that it had done so? I'm not sure which of those is more horrific, so I'm hoping I've misunderstood something because I will soon be migrating my mailman to a system using systemd. -- Steven -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Easy question for this crowd
At Thu, 30 May 2019 11:57:44 -0400 Chip Davis wrote: > > I've supported a dozen Mailman listservers for over a dozen years. > This doesn't represent much real effort most of the time. I've had to > block specific users often and specific domains rarely, but this is > the first time I've had to block an entire TLD. > > Recently I've been gifted with an inordinate amount of UCE from many > different domains under the '.icu' TLD. > > Since Python RE's are _almost_ the same as the UNIX RE's I used many > years ago, if I put > > ^@.*\.icu$ > > in discard_these_nonmembers, will it block all domains in that TLD? Yes. > > And not block anyone else? Yes. I've done this, and then I took things a step further: What *I* have done (because I can), is configure rejection of both domains AND cidrs at the Postfix level, putting REJECT's in both /etc/postfix/access and /etc/postfix/cidr.clients. (I use *REJECT* for a reason: I figure if these idiots are going to make trouble for me, I'll make trouble for them -- eg now they will will get reject messages. Also when the addresses are from legit mail servers, the admins there will get a wake up call and presumably do something -- I have discovered that there is really little point in sending anything to the [so-called] 'abuse' addresses.) I've also configured mimedefang and spamassassin to *reject* spam at the Postfix as well. Very little gets though now. > > Thanks, > > -Chip Davis- > > Mailman 2.1.27 > shared host > linux 2.6.32-696.18.7.el6.x86_64 > cPanel 80.0.10 > -- > Mailman-Users mailing list Mailman-Users@python.org > https://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > Unsubscribe: > https://mail.python.org/mailman/options/mailman-users/heller%40deepsoft.com > > -- Robert Heller -- 978-544-6933 Deepwoods Software-- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services hel...@deepsoft.com -- Webhosting Services -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Easy question for this crowd
I've supported a dozen Mailman listservers for over a dozen years. This doesn't represent much real effort most of the time. I've had to block specific users often and specific domains rarely, but this is the first time I've had to block an entire TLD. Recently I've been gifted with an inordinate amount of UCE from many different domains under the '.icu' TLD. Since Python RE's are _almost_ the same as the UNIX RE's I used many years ago, if I put ^@.*\.icu$ in discard_these_nonmembers, will it block all domains in that TLD? And not block anyone else? Thanks, -Chip Davis- Mailman 2.1.27 shared host linux 2.6.32-696.18.7.el6.x86_64 cPanel 80.0.10 -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Why are mails not being sent to all users (mails seem to disappear)?
Am 09.05.19 um 23:33 schrieb Mark Sapiro: > On 5/9/19 2:06 PM, Till Dörges wrote: >> Curiously for the message that was not delivered to the specific user I did >> /not/ >> find a message by Postfix like the following in /var/log/mail: [...] >> To me that looks as if Postfix did in deed not complete sending all messages. [...] >> I will monitor the situation with these reduced rate settings applied. > > OK. I figured it out. And it was neither a Mailman nor a Postfix problem. systemd-journald simply enforced some rate limiting. After removing it (setting RateLimitBurst=0 in /etc/systemd/journald.conf), delivery for all mails can be seen in the logfiles. Thanks again for your help, and sorry for the noise! Regards -- Till -- Dipl.-Inform. Till Dörges doer...@pre-sense.de PRESENSE Technologies GmbHSachsenstr. 5, D-20097 HH Geschäftsführer/Managing Directors AG Hamburg, HRB 107844 Till Dörges, Jürgen Sander USt-IdNr.: DE263765024 -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] question about email automation
Hello, this is unrelated to using mm itself but was wondering if anyone here had any insight they could share; i run a mailing list on mm 2.x. periodically i send out an event opening email to the list. this is typically followed by a conclusion email at the end of a specific period. in the interim period i would like to send out reminders of the event to the list but would like to automate this task. i want the reminders to be triggered by my opening email and end with my conclusion email. has anyone done this and how? i've looked at ifttt and zapier but wasn't sure. thanks. -- Fabian S. OpenPGP: 0xA1250C2112D2D0E53E5BD964BBB5B16CFB701CD7 -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
