Right now the postmaster mails generated by notify_classes do not
contain any timing information (except for the date of the
notification mail sent). If theses mails had timing information (see
example below), timeout problems could be diagnosed much easier:
Mar 28 08:30:00 Out: 220 octree.de ESMTP Postfix
Mar 28 08:30:00 In: EHLO mailout07.t-online.de
Mar 28 08:30:00 Out: 250-octree.de
Mar 28 08:30:00 Out: 250-PIPELINING
Mar 28 08:30:00 Out: 250-SIZE 102400000
Mar 28 08:30:00 Out: 250-VRFY
Mar 28 08:30:00 Out: 250-ETRN
Mar 28 08:30:00 Out: 250-AUTH PLAIN
Mar 28 08:30:00 Out: 250-AUTH=PLAIN
Mar 28 08:30:00 Out: 250-ENHANCEDSTATUSCODES
Mar 28 08:30:00 Out: 250-8BITMIME
Mar 28 08:30:00 Out: 250 DSN
Mar 28 08:30:00 In: MAIL FROM:<info at sender.example.com> SIZE=112002
Mar 28 08:30:00 Out: 250 2.1.0 Ok
Mar 28 08:30:00 In: RCPT TO:<architekten at recipient.example.com>
Mar 28 08:30:00 Out: 250 2.1.5 Ok
Mar 28 08:30:00 In: DATA
Mar 28 08:30:00 Out: 354 End data with <CR><LF>.<CR><LF>
Mar 28 08:35:00 Out: 451 4.3.0 Error: queue file write error
========
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Charité - Universitätsmedizin Berlin
Campus Benjamin Franklin
Hindenburgdamm 30 | D-12203 Berlin
Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
ralf.hildebra...@charite.de | http://www.charite.de
