You will need to either move to Mailman v2.1 (in alpha) or use ezmlm. Webumake requires each message to be sent individually and the header to be set to the exact individual. That functionality is an option in version 2.1 of Mailman, and a built-in "feature" of ezmlm.
That's fine but it really removes a great deal of functionality from Mailman. Part of Mailman's existing optimizations is that it will send one email to a mailserver that will go to many individuals on that mailserver. As an example, if you have 400 people from aol on your list, Mailman will only send out 8 messages to aol's mailservers and let aol break those messages out to each individual. This is much more efficient than sending 400 individual emails.
I'm curious though about the functionality of Webumake. Is it actually acting as your MTA? does it supercede Sendmail or can it work in conjunction with Sendmail? If the two can work together, then you should be able to eat your cake, and have it too. Sendmail has no problems in sending out to a general list.
Jon Carnes ----- Original Message ----- From: "webmaster" <webmaster@carpemail.com> To: <mailman-users@python.org> Sent: Monday, February 25, 2002 11:27 AM Subject: [Mailman-Users] webmail issues
Hello, i am starting a webmail service, we are using webumake mail to serve this service.
My service is aimed at a niche market in which yahoo groups are popular, but webumake mail does not work with yahoo groups, but webumake support claim it will work will Mailman.
I have setup a test list and tried this, although i have been able to register and receive the confirmation email, it fails to register new user and account cannot receive email from list.
The list does work as i have signed up with normal pop account, webumake give the following reasons why it will not work:
The problem is that email received into the catchall account must have the intended recipient somewhere in the email header for WebUMake Mail (and any such web-based email product, for that matter) to determine who the email is intended for. Unfortunately, some mailing list software persists in defying RFC's and doesn't provide the recipient information in the standard headers. We have developed a method to check the last Received: header element and check it for the "for" text that on most SMTP servers contains the recipient (though this isn't where it should appear, it should _always_ be in the To: or Cc: fields according to RFC's).
If your mail is not being received into WebUMake then the last Received: header record is not being formatted with a "for" statement for the intended recipient by your SMTP server either and so the product has no way of knowing who the email is for.
If you can configure mailman to send the emails and include the recipient in the To: field, or configure your SMTP server to specifying the "for" element of the Received: header record then WebUMake Mail will pick it up.
Is there any particular setting i have to change?
many thanks
webmaster, webmaster@carpemail.com on 25/02/2002
Mailman-Users maillist - Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users