RE: [Mailman-Users] Relaying denied

> Canonical name: vanuatu.eos.elro > a.k.a.: vanuatu > UUCP nodename: vanuatu > a.k.a.: [172.16.7.37] > a.k.a.: [127.0.0.1] > > SYSTEM IDENTITY (after readcf) > (short domain name) $w = vanuatu > (canonical domain name) $j = vanuatu.eos.el

RE: [Mailman-Users] Relaying denied

> [EMAIL PROTECTED] # ls > Mail.rc aliases.dblocal-host-names main.cf > sendmail.hf subsidiary.cf > aliases helpfile mailx.rc > sendmail.cf submit.cf trusted-users I don't know sendmail enough to give you this info (I'm

RE: [Mailman-Users] Relaying denied

> denied">[EMAIL PROTECTED] > >... Relaying denied Did you check your MTA conf files regarding IP access to the SMTP server ? If only one IP or subnet was allowed to pass emails thru your mailman server, and you change that IP and/or subnet when migrating to a new serv

RE: [Mailman-Users] using the web interface to confirm subscription

I once had such problem with a list. You can search this list for more infos about this one (thread name was "Mailman 2.1.1 crashing when approving a new member"). It looks like a deep bug somewhere between Python and Mailman. In my case, I noticed that it happened only when the list name contains

RE: [Mailman-Users] archiving

> > I had an archive up and running and doing fine. I did not > change anything to > the setting but messages are being send but not archived. > Anyone have a hint > as to what the problem might be? IIRC, I once got this problem with HTML messages produced with standard email client. If your list