• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

qmail and multilog

M

magnetik

Guest
Hello,

just wondering, is there any reason why Plesk 7.5 does not setup qmail to use multilog from the daemontools package by default?

As suggested by qmail author D. J. Bernstein here:

http://cr.yp.to/qmail/faq/admin.html#multilog

All my reading has told me that splogger is slower and chews CPU - which I wanted to avoid with the amount of email qmail is sending out (I have a few newsletter clients doing 5000+ emails a day successfully). Also multilog handles log rotation automagically.

I have successfully installed daemontools from an RPM (and disabled svscan) and tweaked my qmail install to use it - works fine. I have also done some other qmail tweaks to improve the queue - like dropping the queuelifetime of a message to 1 day (instead of 7) and turned off all bouncebacks of unknown mail - to avoid "double bounces".

Keen to discuss this topic with others and the reasons why Plesk does not use multilog out of the box.
 
How do you turn off bouncebacks of unknown mail?

Here are some tips for fine tuning this and other parameters:

Run Brent Meshier's Greylisting Qmail Plesk patched with maxrcpt patch, then you can:

Add maxrcpt in control folder to limit number of recipients

More fine tuning:

Add queuelifetime as 259200 (3 days, the default is 7)
Add bouncefrom username, e.g. postmaster
Add doublebounceto to user, e.g. joebloggs
Add doublebouncehost, e.g. domain.com

Double bounces will now go to that address. It's probably a good idea to see why you have double bounces, especially if you have a lot.

I've also seen people use a '#' as the doublebounceto in order to avoid double bounces taking up queue space.

Your original question about Qmail and Multilog and Plesk remains, and I see multiple people are asking the same question with no answer.
 
Here are some tips for fine tuning this and other parameters:

Run Brent Meshier's Greylisting Qmail Plesk patched with maxrcpt patch, then you can:

Add maxrcpt in control folder to limit number of recipients

More fine tuning:

Add queuelifetime as 259200 (3 days, the default is 7)
Add bouncefrom username, e.g. postmaster
Add doublebounceto to user, e.g. joebloggs
Add doublebouncehost, e.g. domain.com

Double bounces will now go to that address. It's probably a good idea to see why you have double bounces, especially if you have a lot.

I've also seen people use a '#' as the doublebounceto in order to avoid double bounces taking up queue space.

Your original question about Qmail and Multilog and Plesk remains, and I see multiple people are asking the same question with no answer.

maxrcpt is built into Plesk Linux from version 8.4 see here http://kb.odin.com/en/1411
 
Back
Top