Date: Thu, 18 Nov 2010 00:55:44 -0500
From: victor.ducho...@morganstanley.com
To: postfix-users@postfix.org
Subject: Re: Invalid response code: 503 5.7.0 Error: access denied
On Wed, Nov 17, 2010 at 03:27:20PM -0500, Wietse Venema wrote:
I had a similar patch that I was going to post
Wietse:
I had a similar patch that I was going to post 30 mins ago when
someone walked into my room:
Victor:
OK, we are on the same page then.
George Forman:
I've made the change to my local code base. Will this change make
it into a 2.7.x release or 2.8?
It is in Postfix 2.8. I haven't
Date: Fri, 19 Nov 2010 12:12:43 -0500
From: victor.ducho...@morganstanley.com
To: postfix-users@postfix.org
Subject: Re: Invalid response code: 503 5.7.0 Error: access denied
On Fri, Nov 19, 2010 at 10:08:19AM -0500, Wietse Venema wrote:
Wietse:
I had a similar patch that I
All,
We are experiencing a problem where Postfix (Using 2.6.2) continuously returns
a 503 5.7.0 Error: access denied response.
The scenario is as follows (see log snipet below for sequence details):
The client MTA attempts to send a message. On the DOT command, Postfix
returns: '451 4.3.0
On Wed, Nov 17, 2010 at 05:24:12PM +, George Forman wrote:
The scenario is as follows (see log snipet below for sequence details):
The client MTA attempts to send a message. On the DOT command, Postfix
returns: '451 4.3.0 Error: queue file write error'
This happens when a milter
On Wed, Nov 17, 2010 at 01:01:05PM -0500, Victor Duchovni wrote:
I am looking for suggestions on a longer term solution.
I have made a change in smtpd_proto function:
New code:
/* XXX We use the real client for connect access control. */
if
Date: Wed, 17 Nov 2010 13:01:05 -0500
From: victor.ducho...@morganstanley.com
To: postfix-users@postfix.org
Subject: Re: Invalid response code: 503 5.7.0 Error: access denied
On Wed, Nov 17, 2010 at 05:24:12PM +, George Forman wrote:
The scenario is as follows (see log snipet
Victor Duchovni:
On Wed, Nov 17, 2010 at 01:01:05PM -0500, Victor Duchovni wrote:
I am looking for suggestions on a longer term solution.
I have made a change in smtpd_proto function:
New code:
/* XXX We use the real client for connect access control. */
On Wed, Nov 17, 2010 at 07:26:35PM +, George Forman wrote:
No, RFC 2821/5321 notwithstanding, Postfix must reject RSET, to give
clients a chance to disconnect before before real mail is rejected.
So DO NOT exempt rset_cmd. Otherwise, the change makes sense. Postfix
gives the intended
On Wed, Nov 17, 2010 at 02:37:27PM -0500, Wietse Venema wrote:
The problem here is that smtpd_access_denied is misused from its original
intent of reporting 503 after a client fails to heed a 554 banner. Perhaps
the intended 421 disconnect on the next command should use a different
Victor Duchovni:
On Wed, Nov 17, 2010 at 02:37:27PM -0500, Wietse Venema wrote:
The problem here is that smtpd_access_denied is misused from its original
intent of reporting 503 after a client fails to heed a 554 banner. Perhaps
the intended 421 disconnect on the next command should
George Forman put forth on 11/17/2010 11:24 AM:
All,
We are experiencing a problem where Postfix (Using 2.6.2) continuously
returns a 503 5.7.0 Error: access denied response.
Looks like you're also experiencing a problem with someone else gaining
access to your Hotmail account and
On Wed, Nov 17, 2010 at 03:27:20PM -0500, Wietse Venema wrote:
I had a similar patch that I was going to post 30 mins ago when
someone walked into my room:
OK, we are on the same page then.
On a somewhat related note, should the documentation explicitly warn that
with
13 matches
Mail list logo
