On Wed, June 27, 2018 17:02, James B. Byrne wrote:
>
> On Wed, June 27, 2018 15:55, Viktor Dukhovni wrote:
. . .
>> And you should still try to find the real cause of the
>> "queue file write error" issue. The DANE bounce backlog
>> was a related symptom not a cause.
>>
>
> I believe that I
* James B. Byrne :
> I am configuring a new Postfix-3.3.0 service to act as one of our
> public MX providers.
> Out: 250 2.1.0 Ok
> In: RCPT TO:
> Out: 250 2.1.5 Ok
> In: DATA
> Out: 354 End data with .
> Out: 451 4.3.0 Error: queue file write error
> In: QUIT
> Out: 221 2.0.0 Bye
>
On Wed, June 27, 2018 15:55, Viktor Dukhovni wrote:
Thank you for your assistance.
>
> And you should still try to find the real cause of the
> "queue file write error" issue. The DANE bounce backlog
> was a related symptom not a cause.
>
I believe that I have uncovered that as well.
> On Jun 27, 2018, at 11:47 AM, James B. Byrne wrote:
>
> Last week Viktor Dukhovni reported to me that our domain had a problem
> with our DNSSEC.
For what it is worth, your DNS looks 100% clean now, the previous
"denial of existence" issues are gone:
On Wed, June 27, 2018 13:49, Wietse Venema wrote:
> James B. Byrne:
>> This still does not clarify for me why the double-bounce address was
>> being reported given that the postconf reported values for notify
>> did
>> not include bounces.
>
> Asl someone else on the list noted, this was
James B. Byrne:
> This still does not clarify for me why the double-bounce address was
> being reported given that the postconf reported values for notify did
> not include bounces.
Asl someone else on the list noted, this was triggered by the
'queue file write error' condition. Postfix is quote
On Tue, Jun 26, 2018 at 02:34:19PM -0400, James B. Byrne wrote:
> When we do we frequently (always?) get messages like this in
> the mail queue:
Well, I may not have solved the problem, but I have identified what it
is and provided a work-around for now.
The issue is this:
On Tue, Jun 26, 2018 at 02:34:19PM -0400, James B. Byrne wrote:
> When we do we frequently
> (always?) get messages like this in the mail queue:
Such important mails must not lay around in the queue, but needs to be
delivered.
> In: RCPT TO:
> Out: 250
On Tue, Jun 26, 2018 at 04:47:57PM -0400, Wietse Venema wrote:
> > Out: 451 4.3.0 Error: queue file write error
> You have "notify_classes = ... bounce ..." somewhere, otherwise
> you would not receive the above SMTP session recording.
>
> Try: postconf -P | grep notify_classes
Are you sure
On Tue, June 26, 2018 16:47, Wietse Venema wrote:
> James B. Byrne:
>> I am configuring a new Postfix-3.3.0 service to act as one of our
>> public MX providers. The address of this new MX service has been
>> published in our DNS but with a lower precedence (higher priority
>> number) than our
James B. Byrne:
> I am configuring a new Postfix-3.3.0 service to act as one of our
> public MX providers. The address of this new MX service has been
> published in our DNS but with a lower precedence (higher priority
> number) than our active MX service.
>
> Naturally enough there are
I am configuring a new Postfix-3.3.0 service to act as one of our
public MX providers. The address of this new MX service has been
published in our DNS but with a lower precedence (higher priority
number) than our active MX service.
Naturally enough there are countless spam bots regularly
12 matches
Mail list logo
