1 / 32

Enhancing MailMan with Postfix: Addressing Missing Features for Better Resource Management

I am currently using MailMan with Postfix and have identified some features that may be beneficial, or perhaps it's just my oversight. Key suggestions include disabling sorting of recipients during message injection to reduce memory usage and implementing a hard limit on concurrent SMTP connections. These improvements can help users manage mailing lists more efficiently without overloading the system. Additionally, I propose a more flexible configuration option for system admins to manage these settings per list, ensuring better control and resource allocation.

afia
Télécharger la présentation

Enhancing MailMan with Postfix: Addressing Missing Features for Better Resource Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. > I'm currently using MailMan with Postfix and I noticed some

  2. > 'missing' features (or maybe my fault :P).

  3. >

  4. > Those are: Disable sorting of recipients when injecting

  5. > the messages. This will help using less

  6. > memory when using MTAs like Postfix or QMail.

  7. I don't think this has been addressed as an option yet.

  8. > Disable or hardlimit (globally) the number

  9. > of concurrent SMTP connections that MailMan

  10. > will open to inject the messages. This will

  11. > be helpfull to let a user maintain it's our

  12. > list without hogging the system down. (You

  13. > know... Stupid users who set this to like

  14. > 100!).

  15. >

  16. > Are these implemented? Sorry if it's already. :P

  17. This also isn't a feature, but for a quick hack you can just

  18. take it out of the CGI interface. People could still get around

  19. it by issuing a POST with that variable set, but they'd have to

  20. know what they're doing AND want to be malicious. The disadvantage

  21. is that this affects every list on your system. Anyhow, comment

  22. out the section about num_spawns in $prefix/Mailman/MailList.py,

  23. around line 431 or so.

  24. #('num_spawns', mm_cfg.Number, 3, 0,

  25. #'Number of outgoing connections to open at once '

  26. #'(expert users only).',

  27. #"This determines the maximum number of batches into which"

  28. #" a mass posting will be divided."),

  29. I've also done this with host_name, max_message_size, and web_page_url,

  30. but plan on making it a per list config option that can only be set

  31. by the system admin.

  32. Chris

More Related