Re: [Mailman-Developers] Mailman and Submission port

* Patrick Ben Koetter : > From my daily work with mailman the following "modified in some way"-tasks > come to my mind immediately: > > - apply client and content policy that differs from the port 25 anti-spam > policy > - add DKIM signatures because it is clear mailman messages are ORIGINATING

Re: [Mailman-Developers] Mailman 3 and LMTP

Patrick Ben Koetter wrote: * Barry Warsaw : - send the web interface off to a usability lab +1. IIRC, Terri was going to look into this, but I'm not sure what's happened with that. She did and offered a contact. As soon as the web interface has come to a usable state I will try to set the te

Re: [Mailman-Developers] MM 3 alpha 4: UnicodeWarning

On Nov 29, 2009, at 6:03 PM, Patrick Ben Koetter wrote: I just sent a message to my freshly installed MM 3 alpha 4 (on Ubuntu 9.04) and got the following warning: Nov 29 23:53:51 mailman postfix/lmtp[8620]: D409D32E12: to=>, relay=127.0.0.1[127.0.0.1]:8025, delay=1.8, delays=0.07/0.01/0/1.7

Re: [Mailman-Developers] Mailman and Submission port

On Nov 29, 2009, at 8:55 PM, Stephen J. Turnbull wrote: I still don't think it's a good idea until we've checked that most popular OS distros supply all their MTAs configured to accept on port 587, and we had better have a bullet-proof autoconfigurator for it. MTA issues are the biggest FAQ that

Re: [Mailman-Developers] Mailman and Submission port

Patrick Ben Koetter writes: > To clarify: I don't want to require users to authenticate in order > to allow them to send. I want mailman to use a stanardized port for > message submission (and that brings in the authentication > requirement). Oh, so this is outgoing? Now I see. I still don'

[Mailman-Developers] MM 3 alpha 4: UnicodeWarning

I just sent a message to my freshly installed MM 3 alpha 4 (on Ubuntu 9.04) and got the following warning: Nov 29 23:53:51 mailman postfix/lmtp[8620]: D409D32E12: to=, relay=127.0.0.1[127.0.0.1]:8025, delay=1.8, delays=0.07/0.01/0/1.7, dsn=2.0.0, status=sent (250 Ok) Nov 29 23:53:51 mailman post

Re: [Mailman-Developers] Mailman 3 and LMTP

On Nov 29, 2009, at 3:29 PM, Patrick Ben Koetter wrote: +1. IIRC, Terri was going to look into this, but I'm not sure what's happened with that. She did and offered a contact. As soon as the web interface has come to a usable state I will try to set the testing on the tracks. Cool. -Barr

Re: [Mailman-Developers] Mailman 3 and LMTP

* Barry Warsaw : > >May I complement the list? > > > >- logo contest > > Yep, it's actually on my TODO list after I get 3.0a4 out. I also > need to finish setting up i18n. > > >- send the web interface off to a usability lab > > +1. IIRC, Terri was going to look into this, but I'm not sure > w

[Mailman-Developers] Mailman 3.0 alpha 4

I'm happy to announce the release of Mailman 3.0 alpha 4. Things are getting quite real now. It's pretty easy to hook Mailman up to Postfix for both incoming and outgoing mail[1] and you can create mailing lists and populate them with addresses. Currently, you must do this through the com

Re: [Mailman-Developers] Mailman and Submission port

* Barry Warsaw : > On Nov 29, 2009, at 4:30 AM, Patrick Ben Koetter wrote: > > >What would we have to do, to make port 587 the default port? In > >section 4 the > >RFC says, a MSA MUST do all of the following: > > > >1. General Submission Rejection Code > >2. Ensure All Domains Are Fully-Qualified

Re: [Mailman-Developers] Mailman 3 and LMTP

On Nov 29, 2009, at 1:39 PM, Patrick Ben Koetter wrote: Thanks, I've added this to the wiki page. consulting /var/spool/postfix/etc/hosts, and I had to change both /etc/hosts That's because LaMont Jones delivers the Debian/Ubunt

Re: [Mailman-Developers] Mailman and Submission port

On Nov 29, 2009, at 4:30 AM, Patrick Ben Koetter wrote: What would we have to do, to make port 587 the default port? In section 4 the RFC says, a MSA MUST do all of the following: 1. General Submission Rejection Code 2. Ensure All Domains Are Fully-Qualified 3. Require Authentication To cut

Re: [Mailman-Developers] Mailman 3 and LMTP

* Barry Warsaw : > >>It seems that Karmic is playing tricks with /etc/hosts. I've got DNS set > >>up to correctly resolve the VM's hostname, but there was actually an entry > >>in /etc/hosts that set xxx.example.com to 127.0.1.1. I'm not entirely > >>sure which process looks at what, when, but cl

Re: [Mailman-Developers] Mailman 3 and LMTP

On Nov 29, 2009, at 3:22 AM, Patrick Ben Koetter wrote: Hi! * Barry Warsaw : I'm getting very near ready to release another alpha of Mailman 3, and on the prompting of a private message from Robert Niederreiter I took some time to fire up a VM and actually try Postfix+LMTP delivery in an

Re: [Mailman-Developers] Mailman and Submission port

* Stephen J. Turnbull : > Patrick Ben Koetter writes: > > > I'd like to propose a change in MM3s default SMTP client port from port 25 > > (transport) to port 587 (submission). > > I don't see a real justification for such a change, given the > authentication requirement. While Mailman can be

[Mailman-Developers] Mailman and Submission port

Patrick Ben Koetter writes: > I'd like to propose a change in MM3s default SMTP client port from port 25 > (transport) to port 587 (submission). I don't see a real justification for such a change, given the authentication requirement. While Mailman can be used in relatively closed setups, its

[Mailman-Developers] Mailman and Submission port

MM developers, I'd like to propose a change in MM3s default SMTP client port from port 25 (transport) to port 587 (submission). Why? From my point of view mailman rather is a mail component that introduces messages into a mail system than one that sits between MTAs and assists in transporting mes

Re: [Mailman-Developers] Mailman 3 and LMTP

Hi! * Barry Warsaw : > I'm getting very near ready to release another alpha of Mailman 3, and on the > prompting of a private message from Robert Niederreiter I took some time to > fire up a VM and actually try Postfix+LMTP delivery in an experimental > production system. I'd like to get some fee