Today a message registered an unfamiliar error in postfix:

Jan  7 20:10:26 geulah postfix/smtpd[2021]: connect from
host67.72.248.165.conversent.net[72.248.165.67]

Jan  7 20:10:28 geulah postfix/smtpd[2021]: 0C846439E2:
client=host67.72.248.165.conversent.net[72.248.165.67]

Jan  7 20:10:28 geulah postfix/bounce[2024]: fatal: open file trace
0C846439E2:Permission denied

Jan  7 20:10:29 geulah postfix/cleanup[2023]: warning: 0C846439E2: trace
service failure

Jan  7 20:10:29 geulah postfix/cleanup[2023]: warning: 0C846439E2: trace
logfile update error

Jan  7 20:10:29 geulah postfix/master[31394]: warning: process
/usr/lib/postfix/bounce pid 2024 exit status 1

Jan  7 20:10:29 geulah postfix/master[31394]: warning:
/usr/lib/postfix/bounce:bad command startup -- throttling

and I got a double-bounce message, which I can display if helpful.

To my mind, this looks like a file system error on the Postfix (appears
to be 2.0.6) box, except:

a) I've verified that I can create files in the directories in
/var/spool/postfix, and the disk has plenty of space;

b) messages have gone by normally, before and since (hundreds of
messages) and

c) this message series appears three times, one for each time (3) 
that this particular SMTP server (client? I always get confused) 
tries to send this particular message. (Each time a different file
name, though.)

So, scratching my head, the only thing that I can think that, somehow,
the message body itself is causing the filesystem to throw up.

Eh?

Reply via email to