Quantcast

Postfix error message to Postmaster

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Postfix error message to Postmaster

James B. Byrne
We continue to receive messages addressed to Postmaster from our MX
host.  All appear to be related to a single original transmission.
The issue seems to be some sort of time-out with the Amavis proxy.  
Is there some way of determining exactly what is wrong with this
specific sender's message?

The Postmaster receives this messages:

Transcript of session follows.

 Out: 220 inet08.hamilton.harte-lyne.ca ESMTP Postfix
 In:  EHLO mail-it0-f47.google.com
 Out: 250-inet08.hamilton.harte-lyne.ca
 Out: 250-PIPELINING
 Out: 250-SIZE 20480000
 Out: 250-ETRN
 Out: 250-STARTTLS
 Out: 250-ENHANCEDSTATUSCODES
 Out: 250-8BITMIME
 Out: 250 DSN
 In:  STARTTLS
 Out: 220 2.0.0 Ready to start TLS
 In:  EHLO mail-it0-f47.google.com
 Out: 250-inet08.hamilton.harte-lyne.ca
 Out: 250-PIPELINING
 Out: 250-SIZE 20480000
 Out: 250-ETRN
 Out: 250-AUTH LOGIN PLAIN
 Out: 250-AUTH=LOGIN PLAIN
 Out: 250-ENHANCEDSTATUSCODES
 Out: 250-8BITMIME
 Out: 250 DSN
 In:  MAIL FROM:<x> SIZE=1701895
 Out: 250 2.1.0 Ok
 In:  RCPT TO:<y>
 Out: 250 2.1.5 Ok
 In:  DATA
 Out: 354 End data with <CR><LF>.<CR><LF>
 Out: 451 4.3.0 Error: queue file write error

Session aborted, reason: lost connection

For other details, see the local mail logfile

The maillog contains these types of entries:

    66  Apr  8 10:50:27 inet08 postfix-p25/smtpd[18374]: warning:
timeout talking to proxy 127.0.0.1:10024
    67  Apr  8 10:50:27 inet08 postfix-p25/smtpd[18374]: proxy-reject:
END-OF-MESSAGE: 451 4.3.0 Error: queue file write error; from=<x>
to=<y> proto=ESMTP helo=<mail-it0-f49.google.com>
    68  Apr  8 10:50:27 inet08 postfix/cleanup[18523]: AE20261ED8:
message-id=<[hidden email]>
    69  Apr  8 10:50:27 inet08 postfix-p25/smtpd[18374]: disconnect
from mail-it0-f49.google.com[209.85.214.49]
    70  Apr  8 10:50:27 inet08 postfix/qmgr[17396]: AE20261ED8:
from=<[hidden email]>, size=1429,
nrcpt=1 (queue active)
    71  Apr  8 10:50:28 inet08 postfix/smtp[18524]: AE20261ED8:
to=<[hidden email]>,
orig_to=<postmaster>,
relay=inet07.hamilton.harte-lyne.ca[216.185.71.27]:25, delay=0.56,
delays=0.07/0.05/0.32/0.12, dsn=2.0.0, status=sent (250 2.0.0 Ok:
queued as 2FA418A69E)
    72  Apr  8 10:50:28 inet08 postfix/qmgr[17396]: AE20261ED8: removed



--
***          e-Mail is NOT a SECURE channel          ***
        Do NOT transmit sensitive data via e-Mail
 Do NOT open attachments nor follow links sent by e-Mail

James B. Byrne                mailto:[hidden email]
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Postfix error message to Postmaster

Wietse Venema
James B. Byrne:
>     66  Apr  8 10:50:27 inet08 postfix-p25/smtpd[18374]: warning:
> timeout talking to proxy 127.0.0.1:10024
>     67  Apr  8 10:50:27 inet08 postfix-p25/smtpd[18374]: proxy-reject:
> END-OF-MESSAGE: 451 4.3.0 Error: queue file write error; from=<x>
> to=<y> proto=ESMTP helo=<mail-it0-f49.google.com>

The spam proxy is taking a long time to do something. To find out what
that is, see the spam proxy's log.

        Wietse
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Postfix error message to Postmaster

James B. Byrne

On Mon, April 10, 2017 11:29, Wietse Venema wrote:

> James B. Byrne:
>>     66  Apr  8 10:50:27 inet08 postfix-p25/smtpd[18374]: warning:
>> timeout talking to proxy 127.0.0.1:10024
>>     67  Apr  8 10:50:27 inet08 postfix-p25/smtpd[18374]:
>> proxy-reject:
>> END-OF-MESSAGE: 451 4.3.0 Error: queue file write error; from=<x>
>> to=<y> proto=ESMTP helo=<mail-it0-f49.google.com>
>
> The spam proxy is taking a long time to do something. To find out what
> that is, see the spam proxy's log.
>
> Wietse
>

This is all that I see in /var/log/spamd for the relevant time period.

# cat /var/log/spamd.log-20170409
. . .
Sat Apr  8 00:06:25 2017 [3845] info: spamd: server started on port
783/tcp (running version 3.3.1)
Sat Apr  8 00:06:25 2017 [3845] info: spamd: server pid: 3845
Sat Apr  8 00:06:25 2017 [3845] info: spamd: server successfully
spawned child process, pid 3851
Sat Apr  8 00:06:25 2017 [3845] info: spamd: server successfully
spawned child process, pid 3852
Sat Apr  8 00:06:25 2017 [3845] info: prefork: child states: IS
Sat Apr  8 00:06:25 2017 [3845] info: prefork: child states: II
Sun Apr  9 03:29:27 2017 [3845] info: spamd: server killed by SIGTERM,
shutting down

There are no entries at all between midnight on the 8th and a
maintenance reboot on the 9th.  Or have I misunderstood your
reference?


--
***          e-Mail is NOT a SECURE channel          ***
        Do NOT transmit sensitive data via e-Mail
 Do NOT open attachments nor follow links sent by e-Mail

James B. Byrne                mailto:[hidden email]
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Postfix error message to Postmaster

Wietse Venema
James B. Byrne:
[ Charset ISO-8859-1 converted... ]

>
> On Mon, April 10, 2017 11:29, Wietse Venema wrote:
> > James B. Byrne:
> >>     66  Apr  8 10:50:27 inet08 postfix-p25/smtpd[18374]: warning:
> >> timeout talking to proxy 127.0.0.1:10024
> >>     67  Apr  8 10:50:27 inet08 postfix-p25/smtpd[18374]:
> >> proxy-reject:
> >> END-OF-MESSAGE: 451 4.3.0 Error: queue file write error; from=<x>
> >> to=<y> proto=ESMTP helo=<mail-it0-f49.google.com>
> >
> > The spam proxy is taking a long time to do something. To find out what
> > that is, see the spam proxy's log.
> >
> > Wietse
> >
>
> This is all that I see in /var/log/spamd for the relevant time period.
>
> # cat /var/log/spamd.log-20170409
> . . .
> Sat Apr  8 00:06:25 2017 [3845] info: spamd: server started on port
> 783/tcp (running version 3.3.1)
> Sat Apr  8 00:06:25 2017 [3845] info: spamd: server pid: 3845
> Sat Apr  8 00:06:25 2017 [3845] info: spamd: server successfully
> spawned child process, pid 3851
> Sat Apr  8 00:06:25 2017 [3845] info: spamd: server successfully
> spawned child process, pid 3852
> Sat Apr  8 00:06:25 2017 [3845] info: prefork: child states: IS
> Sat Apr  8 00:06:25 2017 [3845] info: prefork: child states: II
> Sun Apr  9 03:29:27 2017 [3845] info: spamd: server killed by SIGTERM,
> shutting down
>
> There are no entries at all between midnight on the 8th and a
> maintenance reboot on the 9th.  Or have I misunderstood your
> reference?

If this is all the logging, then I suggest that you ask the people
who created this product how to get more insight into the handling
of individual mail transactions.

        Wietse
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Postfix error message to Postmaster

Juri Haberland
In reply to this post by James B. Byrne
On 10.04.2017 18:33, James B. Byrne wrote:
>
> On Mon, April 10, 2017 11:29, Wietse Venema wrote:
>> James B. Byrne:

>>> The issue seems to be some sort of time-out with the Amavis proxy.

>>>     66  Apr  8 10:50:27 inet08 postfix-p25/smtpd[18374]: warning:
>>> timeout talking to proxy 127.0.0.1:10024
>>>     67  Apr  8 10:50:27 inet08 postfix-p25/smtpd[18374]:
>>> proxy-reject:
>>> END-OF-MESSAGE: 451 4.3.0 Error: queue file write error; from=<x>
>>> to=<y> proto=ESMTP helo=<mail-it0-f49.google.com>
>>
>> The spam proxy is taking a long time to do something. To find out what
>> that is, see the spam proxy's log.

> This is all that I see in /var/log/spamd for the relevant time period.
>
> # cat /var/log/spamd.log-20170409
> . . .
> Sat Apr  8 00:06:25 2017 [3845] info: spamd: server started on port
> 783/tcp (running version 3.3.1)

You are talking about amavis - this is spamassassin. Please check what you
have configured.

Is amavis running (ps aux|grep amavis)?
Does amavis listen on port 10024 (netstat -lntp|grep 10024)?
What does your mail.log say about amavis?

  Juri

Loading...