
Hi there,
We use Mailman 2.1 with Qmail and Plesk (v10.2). Everything works nicely with Mailman however it's not sending out the bounce emails to the owner to say there are pending requests. Upon checking the /var/log/mailman/smtp-failure logs, it's showing that website-owner@website.name doesn't exist when mailman tries to send the bounce request to the list owner. It does however send back the user who sent the email a pending request saying that their email is awaiting authorization. There's all the .qmail files in /var/qmail/mailnames/website/.qmail-listname-* and have this type of format:
|/var/qmail/bin/preline /usr/lib/plesk-9.0/mm_wrapper /usr/lib/mailman/mail/mailman owner websitename
If I try and send an email directly to website-owner@website.name, it'll bounce back straight away with: 550 sorry, no mailbox here by that name. (#5.7.17)
It's like qmail isn't passing control to mailman when doing recipient verification? Has anyone else had these issues with Plesk and Qmail?
Cheers, Mike

Mike Manning writes:
We use Mailman 2.1 with Qmail and Plesk (v10.2). Everything works nicely with Mailman however it's not sending out the bounce emails
"Bounce" is a term of art; it means "mail returned because it was undeliverable". Mailman doesn't send out bounces to anybody, although it may forward bounces it has received from MTAs to list owners.
The messages you are referring to are notifications of pending moderation.
It's important to keep these separate because bounce processing is an extremely important (and complex!) part of Mailman functionality, but it is completely separate from the moderation queue.
Evidently, Mailman has been configured to send to a non-existent address. (See the 2d and 3d items on the General Options page, assuming Plesk hasn't mangled it.) There is not enough information to speculate on how this happened, but it's not a Mailman problem.
To solve it, somebody needs to get real addresses of the mailing list owners, and either configure Mailman to send to them directly, or to set up aliases to website-owner@website.name for them in qmail so the that the pre-configured addresses work. It's possible that Plesk offers a front-end that is supposed to handle this in a convenient way, but if that's failing, it's a Plesk problem.
It's like qmail isn't passing control to mailman when doing recipient verification?
Mailman doesn't, and can't, verify addresses; it can only ask qmail to try to send to the addresses that admins and subscribers have registered with it.

Mike Manning wrote:
The specific qmail alias you quote above looks wrong. I would expect something more like
|/var/qmail/bin/preline /usr/lib/mailman/mail/mailman owner websitename
or
|/var/qmail/bin/preline /usr/lib/plesk-9.0/mm_wrapper owner websitename
Look at the /var/qmail/mailnames/website/.qmail-listname file. The /var/qmail/mailnames/website/.qmail-listname-owner file should have exactly the same ownership and permissions and should have exactly the same contents except where /var/qmail/mailnames/website/.qmail-listname has 'post', /var/qmail/mailnames/website/.qmail-listname-owner should have 'owner' (and similarly for the other /var/qmail/mailnames/website/.qmail-listname-* files).
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

Mike Manning writes:
We use Mailman 2.1 with Qmail and Plesk (v10.2). Everything works nicely with Mailman however it's not sending out the bounce emails
"Bounce" is a term of art; it means "mail returned because it was undeliverable". Mailman doesn't send out bounces to anybody, although it may forward bounces it has received from MTAs to list owners.
The messages you are referring to are notifications of pending moderation.
It's important to keep these separate because bounce processing is an extremely important (and complex!) part of Mailman functionality, but it is completely separate from the moderation queue.
Evidently, Mailman has been configured to send to a non-existent address. (See the 2d and 3d items on the General Options page, assuming Plesk hasn't mangled it.) There is not enough information to speculate on how this happened, but it's not a Mailman problem.
To solve it, somebody needs to get real addresses of the mailing list owners, and either configure Mailman to send to them directly, or to set up aliases to website-owner@website.name for them in qmail so the that the pre-configured addresses work. It's possible that Plesk offers a front-end that is supposed to handle this in a convenient way, but if that's failing, it's a Plesk problem.
It's like qmail isn't passing control to mailman when doing recipient verification?
Mailman doesn't, and can't, verify addresses; it can only ask qmail to try to send to the addresses that admins and subscribers have registered with it.

Mike Manning wrote:
The specific qmail alias you quote above looks wrong. I would expect something more like
|/var/qmail/bin/preline /usr/lib/mailman/mail/mailman owner websitename
or
|/var/qmail/bin/preline /usr/lib/plesk-9.0/mm_wrapper owner websitename
Look at the /var/qmail/mailnames/website/.qmail-listname file. The /var/qmail/mailnames/website/.qmail-listname-owner file should have exactly the same ownership and permissions and should have exactly the same contents except where /var/qmail/mailnames/website/.qmail-listname has 'post', /var/qmail/mailnames/website/.qmail-listname-owner should have 'owner' (and similarly for the other /var/qmail/mailnames/website/.qmail-listname-* files).
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Mark Sapiro
-
Mike Manning
-
Stephen J. Turnbull