Re: hide Recieved 127.0.0.1 Header

2011-08-18 Thread mouss
Le 14/08/2011 01:59, spamv...@googlemail.com a écrit : > Hi.. > > Im running postfix with amavisd-new and everything works well but when > i send a email the Header looks like: > > Return-Path: > Received: from ms16-1.1blu.de (ms16-1.1blu.de [89.202.0.34]) > by mb8-4 (Cyrus v2.1.18-IPv6-

Re: envelope spoofing

2011-08-18 Thread mouss
Le 15/08/2011 17:29, Drizzt a écrit : > Hi, > > I have a setup whereby we check for spoofing. That is, anyone using an > envelope from in our domain is blocked. In a similar fashion we stop our > own hosts from spoofing others. > > For reference: > - external spoofing: > check_sender_access: my

Re: Remove header on reinjection

2011-08-18 Thread mouss
Le 18/08/2011 01:31, Steve Fatula a écrit : > - Original Message - > >> From: Steve Fatula >> To: Postfix Users >> Cc: >> Sent: Wednesday, August 17, 2011 6:18 PM >> Subject: Remove header on reinjection >> >> Sounded easy (and probably is), but, don't see it. I know I can add >> heade

Re: Request For Port 587

2011-08-18 Thread mouss
Le 18/08/2011 14:53, Carlos Mennens a écrit : > Today I received a ticket for altering the way my Postfix server > handles mail and I don't understand it. The ticket / request is pasted > below: > > ** > According to RFC 4409 client mail submission to an

Re: Request For Port 587

2011-08-18 Thread Ansgar Wiechers
On 2011-08-18 Jeroen Geilman wrote: > On 2011-08-18 14:59, Reindl Harald wrote: >> 587 is AUTHENTICATED submission > > Says who ? Chapter 4.3 of RFC 4409, unless I'm misunderstanding something. Regards Ansgar Wiechers -- "Abstractions save us time working, but they don't save us time learning."

RE: Request For Port 587

2011-08-18 Thread Murray S. Kucherawy
> -Original Message- > From: owner-postfix-us...@postfix.org > [mailto:owner-postfix-us...@postfix.org] On Behalf Of Jeroen Geilman > Sent: Thursday, August 18, 2011 9:03 AM > To: postfix-users@postfix.org > Subject: Re: Request For Port 587 > > This is now a Draft standard, meaning you'd

Re: Request For Port 587

2011-08-18 Thread John Hinton
On 8/18/2011 11:39 AM, Thomas Berger wrote: Am Donnerstag, 18. August 2011, 15:23:28 schrieb Jeroen Geilman: On 2011-08-18 14:59, Reindl Harald wrote: 587 is AUTHENTICATED submission Says who ? Port 587 is AUTHORIZED submission, NOT AUTHENTICATED. A limitation to a local network ist also a

Re: Request For Port 587

2011-08-18 Thread Jeroen Geilman
On 2011-08-18 17:39, Thomas Berger wrote: Am Donnerstag, 18. August 2011, 15:23:28 schrieb Jeroen Geilman: On 2011-08-18 14:59, Reindl Harald wrote: 587 is AUTHENTICATED submission Says who ? Port 587 is AUTHORIZED submission, NOT AUTHENTICATED. Um, no. RFC 4409, section 4.3 states that

Re: Request For Port 587

2011-08-18 Thread Thomas Berger
Am Donnerstag, 18. August 2011, 15:23:28 schrieb Jeroen Geilman: > On 2011-08-18 14:59, Reindl Harald wrote: > > > 587 is AUTHENTICATED submission > > > Says who ? Port 587 is AUTHORIZED submission, NOT AUTHENTICATED. A limitation to a local network ist also a kind of authorization. --

Re: Request For Port 587

2011-08-18 Thread Jeroen Geilman
On 2011-08-18 15:27, Reindl Harald wrote: Am 18.08.2011 15:23, schrieb Jeroen Geilman: On 2011-08-18 14:59, Reindl Harald wrote: 587 is AUTHENTICATED submission Says who ? have you ever seen submission as open-relay? if yes - where and why does nonone shutdown this machine? Submission can

Re: Request For Port 587

2011-08-18 Thread Reindl Harald
Am 18.08.2011 15:23, schrieb Jeroen Geilman: > On 2011-08-18 14:59, Reindl Harald wrote: >> 587 is AUTHENTICATED submission > > Says who ? have you ever seen submission as open-relay? if yes - where and why does nonone shutdown this machine? signature.asc Description: OpenPGP digital signatu

Re: Request For Port 587

2011-08-18 Thread Jeroen Geilman
On 2011-08-18 14:59, Reindl Harald wrote: 587 is AUTHENTICATED submission Says who ? -- J.

Re: Request For Port 587

2011-08-18 Thread Matt Hayes
On 8/18/2011 9:13 AM, Carlos Mennens wrote: On Thu, Aug 18, 2011 at 9:02 AM, Matt Hayes wrote: Carlos, This is a direct quote from a bot running in #postfix on freenode: Port 587 is submission, for user submission of mail, NOT suitable for mail exchange. See the commented example in master.cf

Re: Request For Port 587

2011-08-18 Thread Ralf Hildebrandt
* Carlos Mennens : > On Thu, Aug 18, 2011 at 9:02 AM, Matt Hayes wrote: > > Carlos, > > > > This is a direct quote from a bot running in #postfix on freenode: > > > > Port 587 is submission, for user submission of mail, NOT suitable for mail > > exchange. See the commented example in master.cf. al

Re: Request For Port 587

2011-08-18 Thread Carlos Mennens
On Thu, Aug 18, 2011 at 9:02 AM, Matt Hayes wrote: > Carlos, > > This is a direct quote from a bot running in #postfix on freenode: > > Port 587 is submission, for user submission of mail, NOT suitable for mail > exchange. See the commented example in master.cf. also >                      see !ms

Re: Request For Port 587

2011-08-18 Thread Matt Hayes
On 8/18/2011 8:53 AM, Carlos Mennens wrote: Today I received a ticket for altering the way my Postfix server handles mail and I don't understand it. The ticket / request is pasted below: ** According to RFC 4409 client mail submission to an email ser

Re: Request For Port 587

2011-08-18 Thread Reindl Harald
587 is AUTHENTICATED submission and should be preferred since more and more providers blocking spam-bots by clsoing outgoing port 25 for homeusers submission inet n - n - 50 smtpd -o smtpd_sasl_auth_enable=yes -o smtpd_client_restrictions=permit_sasl_authenticated,reject he is NOT requesting to a

Re: Request For Port 587

2011-08-18 Thread Ralf Hildebrandt
* Carlos Mennens : > Today I received a ticket for altering the way my Postfix server > handles mail and I don't understand it. The ticket / request is pasted > below: > > ** > According to RFC 4409 client mail submission to an email server is > supposed

Request For Port 587

2011-08-18 Thread Carlos Mennens
Today I received a ticket for altering the way my Postfix server handles mail and I don't understand it. The ticket / request is pasted below: ** According to RFC 4409 client mail submission to an email server is supposed to use port 587. Server to serve