[Mailman-Users] slow "out" queue

[Anil Jangity]

Actually, this is a internal SmartHost that doesn't require SMTP auth.
I think a while back I had configured Mailman with --with-mailhost=localhost, a bunch of pages also showed "localhost" as the email domain for some of the list details. That's not what I wanted.

I assume there won't be issues if all I do is change that variable to SmartHostA in the mm_cfg.py file. I would like everything else to be in tact, and only want the outgoing mail to be directed to smart host. I will test it out in our UAT.

Thanks!
Anil


On Mar 8, 2012, at 2:23 PM, Mark Sapiro wrote:

> Anil Jangity wrote:
>> 
>> Mailman receives the mail and then posts to the same local MTA on the host which sends it out to Smart host.
>> I am not sure we can't just have mailman send directly to the smarthost?
>> 
>> What are the implications (on the web site as well as how Mailman functions) if I change DEFAULT_EMAIL_HOST to be SmartHostA?
> 
> 
> Most likeley, SmartHostA will refuse to relay the mail because Mailman
> hasn't authenticated to it as an authorized user.
> 
> See <https://bugs.launchpad.net/mailman/+bug/558281> for a patch that
> implements SMTP authentication for Mailman.
> 
> -- 
> Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
> San Francisco Bay Area, California    better use your sense - B. Dylan
>