[Mailman-Users] bulk subscribe 7K users

Dimitri Maziuk dmaziuk at bmrb.wisc.edu
Mon Oct 2 15:22:20 EDT 2017


On 10/02/2017 01:10 PM, Mark Sapiro wrote:

> You need to look in Mailman's 'smtp' log to see how much time is being
> taken to deliver to postfix. 

Close to .1 s, with an occasional .12 on the date in question.

> One big killer in delivery from Mailman to
> Postfix is recipient address validation at smtpd time. I.e., you don't
> want reject_unknown_recipient_domain in smtpd_recipient_restrictions.

:) Well I do actually, this being our mail gateway, but I get the point.
The more reason to outsource this to out university's IT instead of
running it locally.

> Also, you don't need spamd scanning of Mailman's outbound mail as list
> posts will have been scanned on input.
> 
> Whatever the reason, you won't be able to run a viable list if it takes
> days to deliver 3500 messages. Even an hour would be excessive.

Of course it's not scanning outbound mail, but it is scanning the
incoming on delivery, using up cycles and i/o.

/var/log/mailman/smtp is interesting, actually:

> Sep 25 15:53:57 2017 (7782) <mailman.0.1506372716.29657.XXX at XXX> smtp to XXX for 1 recips, completed in 0.081 seconds
...
> Sep 25 15:59:06 2017 (7782) <mailman.2.1506373144.7778.XXX at XXX> smtp to XXX for 1 recips, completed in 0.061 seconds
> Sep 25 16:48:39 2017 (7782) <mailman.2.1506376117.7779.XXX at XXX> smtp to XXX for 1 recips, completed in 0.065 seconds
> Sep 25 19:03:16 2017 (7782) <mailman.3.1506384195.7778.XXX at XXX> smtp to XXX for 1 recips, completed in 0.079 seconds
> Sep 25 19:33:19 2017 (7782) <mailman.4.1506385998.7778.XXX at XXX> smtp to XXX for 1 recips, completed in 0.069 seconds
> Sep 26 01:14:46 2017 (7782) <mailman.0.1506406484.11544.XXX at XXX> smtp to XXX for 1 recips, completed in 0.062 seconds
> Sep 26 12:12:45 2017 (7782) <mailman.3.1506445964.7779.XXX at XXX> smtp to XXX for 1 recips, completed in 0.060 seconds

There's 3200 of these lines total, so at .1s/address it should've ran in
320 seconds. Instead it ran for 6 minutes, then hours later a message or
two for a while, and nothing after Sep 26 12:12:45.

/var/log/mailman/subscribe goes

> Sep 25 15:51:56 2017 (29657) XXX: new aaa at ADDR, admin mass sub

to

> Sep 25 15:53:56 2017 (29657) XXX: new jjj at ADDR, admin mass sub

and ends there. To my uneducated eye it looks like smtp transactions
haven't even started until the subscription's gone about halfway through
and presumably aborted.

Anyway, this is getting academic. What I wanted to know was is it dead
or is it still doing something behind the scenes, and I got the answer.

Thanks everyone.
-- 
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-users/attachments/20171002/dd9a9a62/attachment.sig>


More information about the Mailman-Users mailing list