On Nov 30, 2009, at 6:28 AM, Ian Eiloart wrote:
Autoconfiguration shouldn't be too hard. Mailman has to be
configured with a hostname. There are three options for the port:
custom configuration
587
25
Mailman can test the connectivity of each in turn, on the first
message that it sends. Ca
--On 29 November 2009 21:07:28 -0500 Barry Warsaw wrote:
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-proo
* 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
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
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'
* 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
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
* 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
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
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
10 matches
Mail list logo
