On 8/11/2010 8:44 PM, junkyardma...@verizon.net wrote:
With smtpd_delay_reject = yes
Which of the restriction sections was the following logged
rejection for?
Or put another way, in which of the restriction sections was
the rejection option "reject_rbl_client pbl.spamhaus.org" that
resulted in t
With smtpd_delay_reject = yes
Which of the restriction sections was the following logged rejection for?
Or put another way, in which of the restriction sections was the rejection
option "reject_rbl_client pbl.spamhaus.org" that resulted in the logged
rejection?
Restriction Options:
smtpd_clie
On 8/11/2010 6:54 AM, Stan Hoeppner wrote:
Noel Jones put forth on 8/11/2010 6:20 AM:
This is logged when the client disconnected in the middle of the
transaction -- postfix lost the connection -- NOT a reject.
You won't find reject log entries for the lost connections after EHLO or
CONNECT, a
Noel Jones put forth on 8/11/2010 6:20 AM:
> This is logged when the client disconnected in the middle of the
> transaction -- postfix lost the connection -- NOT a reject.
>
> You won't find reject log entries for the lost connections after EHLO or
> CONNECT, although the ones for RCPT and DATA *
On 8/11/2010 4:10 AM, Stan Hoeppner wrote:
Stan Hoeppner put forth on 8/11/2010 3:31 AM:
I was just looking at a Logwatch summary. The data the OP is requesting _is_
in the Postfix logs somewhere, as Logwatch is tallying the disconnection phases:
81 Connections lost (inbound)
Stan Hoeppner put forth on 8/11/2010 3:31 AM:
> I was just looking at a Logwatch summary. The data the OP is requesting _is_
> in the Postfix logs somewhere, as Logwatch is tallying the disconnection
> phases:
>
>81 Connections lost (inbound)
>61 After DATA
>11
Ralf Hildebrandt put forth on 8/11/2010 2:35 AM:
> * Stan Hoeppner :
>> Michael Orlitzky put forth on 8/10/2010 4:02 PM:
>>
>>> I think he just wants to know which smtpd restrictions list contains the
>>> rule that caused the rejection.
>>
>> This is relatively easy to accomplish with custom reject
* Stan Hoeppner :
> Michael Orlitzky put forth on 8/10/2010 4:02 PM:
>
> > I think he just wants to know which smtpd restrictions list contains the
> > rule that caused the rejection.
>
> This is relatively easy to accomplish with custom rejection messages. Simply
> insert a unique symbol at the
Michael Orlitzky put forth on 8/10/2010 4:02 PM:
> I think he just wants to know which smtpd restrictions list contains the
> rule that caused the rejection.
This is relatively easy to accomplish with custom rejection messages. Simply
insert a unique symbol at the beginning of each rejection mes
* junkyardma...@verizon.net :
> "I think he just wants to know which smtpd restrictions list contains
> the rule that caused the rejection."
>
> Correct.
Like I said, even with smtpd_delay_reject = no this is not given.
> >An almost-answer: each reject_foo rule has a certain log format
> >which,
Please don't top-post.
--
From: "Noel Jones"
Sent: Tuesday, August 10, 2010 1:27 PM
To:
Subject: Re: smtpd_delay_reject = yes & Reject Logging
On 8/10/2010 3:19 PM, junkyardma...@verizon.net wrote:
When using the “smtpd
"I think he just wants to know which smtpd restrictions list contains the
rule that caused the rejection."
Correct.
--
From: "Michael Orlitzky"
Sent: Tuesday, August 10, 2010 2:02 PM
To:
Subject: Re: smtpd_delay_reject =
In an older episode, on 2010-08-10 23:06, Ralf Hildebrandt wrote:
You still have to look up which restrictions list contains that rule,
though.
Yes, there could be different check_sender_access rules - even without
smtpd_delay_reject it would be hard to see WHICH ONE fired.
They way I do this
* Michael Orlitzky :
> I think he just wants to know which smtpd restrictions list contains
> the rule that caused the rejection.
Could be.
> An almost-answer: each reject_foo rule has a certain log format
> which, once learned, will give you a pretty good idea about the rule
> that caused the
On 08/10/2010 04:46 PM, Ralf Hildebrandt wrote:
* junkyardma...@verizon.net:
Yes it does cause a problem.
It does not indicate the stage the rejection is associated with
(CONNECT, HELO, FROM, RCPT, etc.).
The rejection always happens at the RCPT TO stage in those cases.
Thus it's called "smtpd
* junkyardma...@verizon.net :
> Yes it does cause a problem.
> It does not indicate the stage the rejection is associated with
> (CONNECT, HELO, FROM, RCPT, etc.).
The rejection always happens at the RCPT TO stage in those cases.
Thus it's called "smtpd_delay_reject".
Back in the dawn of Postfix
lay_reject = yes & Reject Logging
* junkyardma...@verizon.net :
When using the "smtpd_delay_reject = yes" option, all log messages
indicate RCPT stage rejection. e.g. "... NOQUEUE: reject: RCPT from
..."; regardless of which type of restriction an option is listed under.
Yes it does cause a problem.
It does not indicate the stage the rejection is associated with (CONNECT,
HELO, FROM, RCPT, etc.).
--
From: "Noel Jones"
Sent: Tuesday, August 10, 2010 1:27 PM
To:
Subject: Re: smtpd_delay_reject = ye
On 8/10/2010 3:19 PM, junkyardma...@verizon.net wrote:
When using the “smtpd_delay_reject = yes” option, all log
messages indicate RCPT stage rejection. e.g. “... NOQUEUE:
reject: RCPT from ...”; regardless of which type of
restriction an option is listed under.
For instance a rejection based on
* junkyardma...@verizon.net :
> When using the "smtpd_delay_reject = yes" option, all log messages indicate
> RCPT stage rejection. e.g. "... NOQUEUE: reject: RCPT from ..."; regardless
> of which type of restriction an option is listed under.
>
> For instance a rejection based on the following
When using the "smtpd_delay_reject = yes" option, all log messages indicate
RCPT stage rejection. e.g. "... NOQUEUE: reject: RCPT from ..."; regardless of
which type of restriction an option is listed under.
For instance a rejection based on the following will indicate RCPT rather than
CONNECT
21 matches
Mail list logo
