[Mailman-Users] problem solved, list up and running...

Hi! Just a quick note to say thank you once again to Mark and everyone else. I sincerely appreciate the support, guidance, and advice and have a tremendous amount of respect and admiration for you gurus. Most of the time we tend to post to this list with our problems and I thought it would be ref

Re: [Mailman-Users] Problem solved: it was the MTA

No, it was not a typo, just an ellipsis :-) I am very careful when it comes to changing things. I read that changes are not to go into Defaults, and I made the changes in mm_cfg.py. I just omitted the gory details :-) (that what I put in mm_cfg.py in the end becomes Defaults). But you are rig

Re: [Mailman-Users] Problem solved: it was the MTA

Thank you, Todd, for acting so irate ;-) about my bypassing the warnings and setting up sendmail "in the raw" as opposed to going to it via SMTPDirect. I guess I have demonstrated to be truly a newbie but... there is hope for me. I decided to look into the sendmail.cf file, and it turns out that

Re: [Mailman-Users] Problem solved: it was the MTA

> But, from the point of view of mailman, once the correct > Delivery_Module was specified in Defaults.py, it works fast > as a whistle. That was a typo, right? There is ample warning in the documentation (and, IIRC, in the Defaults.py file itself) that changes go in mm_cfg.py, not in Defaults.

Re: [Mailman-Users] Problem solved: it was the MTA

So, I got this: #telnet localhost 25 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 mafalda.math.indiana.edu ESMTP Sendmail bla bla bla versions Well, let me play with the fun parts :-) Best, elena -- Mailman-Users

Re: [Mailman-Users] Problem solved: it was the MTA

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Elena Fraboschi wrote: > ugh, you must be a developer... :-) Not even close. (I don't even play one on TV. :) > My problem was that mailman received all fine, queued all fine, > and never delivered a thing. Obviously my sendmail was running. > When

Re: [Mailman-Users] Problem solved: it was the MTA

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Elena Fraboschi wrote: > Thank you, Todd, for acting so irate ;-) about my bypassing the warnings > and setting up sendmail "in the raw" as opposed to going to it via > SMTPDirect. I guess that's like 'tough love.' ;-) > I guess I have demonstrated

Re: [Mailman-Users] Problem solved: it was the MTA

ugh, you must be a developer... :-) (just in case, here comes another one ;-)) My problem was that mailman received all fine, queued all fine, and never delivered a thing. Obviously my sendmail was running. When I changed DELIVERY_MODULE from SMTPDirect to Sendmail, it worked just fine. Now, I

Re: [Mailman-Users] Problem solved: it was the MTA

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Elena Fraboschi wrote: > and there I learned that the makers of mailman, in an over-protective > move, commented out "Sendmail" as the Delivery_Module, and put > "SMTPDirect" instead. All that is fine, except that there should > be a warning about thi

[Mailman-Users] Problem solved: it was the MTA

Well, I reasoned that mailman was working just fine, save for the fact that it was not delivering any messages. I went to Mailman/Defaults.py and there I learned that the makers of mailman, in an over-protective move, commented out "Sendmail" as the Delivery_Module, and put "SMTPDirect" instead.

[Mailman-Users] problem solved

DOH! I was forgetting the '=' sign in my --with-mail-gid argument to ./configure. I think things are working fine now... Thanks! cheers, J. -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- Joshua S. Freeman | preferred email: [EMAIL PROTECTED]