> On Wed, 1 Feb 2023, Wietse Venema wrote:
>
> > post...@fongaboo.com:
> >> Jan 31 20:06:15 h6lix postfix/smtp[6552]: 7128C4089C:
> >> to=, relay=50.75.172.140[50.75.172.140]:25,
> >> delay=2.5, delays=0.64/0.01/1.6/0.23, dsn=4.3.0, status=deferred
> >> (host 50.75.172.140[50.75.172.140] said: 451
So those log snippets are from the logs on 50.75.172.140 (my postfix
server). What more might I be looking for?
On Wed, 1 Feb 2023, Wietse Venema wrote:
post...@fongaboo.com:
Jan 31 20:06:15 h6lix postfix/smtp[6552]: 7128C4089C:
to=, relay=50.75.172.140[50.75.172.140]:25,
delay=2.5, delay
post...@fongaboo.com:
> Jan 31 20:06:15 h6lix postfix/smtp[6552]: 7128C4089C:
> to=, relay=50.75.172.140[50.75.172.140]:25,
> delay=2.5, delays=0.64/0.01/1.6/0.23, dsn=4.3.0, status=deferred
> (host 50.75.172.140[50.75.172.140] said: 451 4.3.0 Error: queue
> file write error (in reply to end of DAT
Eliezer Croitoru:
> it seems that this problem is not postfix specific but a more runtim\io
> or other low level problem.
Hypervisors are known to have problems delivering timer events.
Without proper timer support, Postfix processes cannot detect
timeout conditions and will hang indefinitely.
it seems that this problem is not postfix specific but a more runtim\io
or other low level problem.
Eliezer
On 03/05/2012 11:56, Nikolaos Milas wrote:
On 3/5/2012 11:43 πμ, Eliezer Croitoru wrote:
the thing is it seems like a FS issue or VM cpu\clock issues from the
log.
It might. In the m
On 3/5/2012 11:43 πμ, Eliezer Croitoru wrote:
the thing is it seems like a FS issue or VM cpu\clock issues from the
log.
It might. In the meantime, I found the following in /var/log/messages
(which occurred when Postfix problems started).
Such errors have never occurred in the past (nor oc
On 03/05/2012 11:04, Nikolaos Milas wrote:
On 3/5/2012 10:29 πμ, Eliezer Croitoru wrote:
just out of curiosity, does this KVM host uses some nas\san for VMs HD?
Yes. It is a cluster of physical servers using a SAN/NAS for data
storage. However, I don't know much more, because it is operated b
On 3/5/2012 10:29 πμ, Eliezer Croitoru wrote:
just out of curiosity, does this KVM host uses some nas\san for VMs HD?
Yes. It is a cluster of physical servers using a SAN/NAS for data
storage. However, I don't know much more, because it is operated by a
different organization (you may see:
just out of curiosity, does this KVM host uses some nas\san for VMs HD?
On 03/05/2012 10:10, Nikolaos Milas wrote:
On 3/5/2012 1:54 πμ, Wietse Venema wrote:
For other details, see the local mail logfile
Look at the last line!
Thank you Wietse,
The only thing probably related to the issue,
On 3/5/2012 1:54 πμ, Wietse Venema wrote:
For other details, see the local mail logfile
Look at the last line!
Thank you Wietse,
The only thing probably related to the issue, logged with the same
timestamp *for the particular case I reported* is:
May 2 23:25:03 vmail postfix/cleanup[28676
Nikolaos Milas:
> In: DATA
> Out: 354 End data with .
> Out: 451 4.3.0 Error: queue file write error
>
> Session aborted, reason: lost connection
>
> For other details, see the local mail logfile
Look at the last line!
Wietse
are you using postscreen by any chance?
it's seems like the network layer between the client and the server is fine.
can you see anything on the maillog when the session was started?
is this happening on every session or just part of them?
as i remember a 4XX errors aborted transmissions will b
Am Montag, 27. Februar 2012, 13:03:46 schrieb Wietse Venema:
> Stefan Jakobs:
> > What makes me wonder is, that I can't find a hint about the 'queue file
> > write error' in the logfile. From the log it looks as if there wasn't any
> > problem with the message a all. Is that the intended behavior o
Stefan Jakobs:
> What makes me wonder is, that I can't find a hint about the 'queue file write
> error' in the logfile. From the log it looks as if there wasn't any problem
> with the message a all. Is that the intended behavior or are there some
> missing log lines?
Postfix logs a timeout erro
K bharathan:
> thanks Mr.Wietse for ur time
>
> details are logged into log files named - warn,mail.error,mail and mail.info;
> i checked all of these for this particular error but not available; only
> information related to the message from mail.info is as follows:
Postfix sends "queue file wri
thanks Mr.Wietse for ur time
details are logged into log files named - warn,mail.error,mail and mail.info;
i checked all of these for this particular error but not available; only
information related to the message from mail.info is as follows:
Oct 7 10:35:23 relay1 postfix/smtpd[827]: connect f
K bharathan:
> hi all
> i got a notice from my relay saying queue file write error; the details are
> as follows:
Postfix logs the details to syslogd. If your syslogging is spread out
across separate files for normal, warning and error, you will have to
look in all those files.
Wietse
Vidar Salberg Normann:
> The asterisks are mine, I've just removed the IP-adresses, servernames and
> email-adresses. I've had a hard time finding info about what might give this
> error, any ideas?
http://www.postfix.org/DEBUG_README.html#logging
Look for obvious signs of trouble
Postfix logs a
* Vidar Salberg Normann <[EMAIL PROTECTED]>:
> The asterisks are mine, I've just removed the IP-adresses, servernames and
> email-adresses. I've had a hard time finding info about what might give this
> error, any ideas?
Look at your log!
--
Ralf Hildebrandt ([EMAIL PROTECTED]) [EMAIL
19 matches
Mail list logo
