6 messages in net.sourceforge.lists.courier-users[courier-users] Re: courierdsn unable...
FromSent OnAttachments
Anand BuddhdevAug 12, 2003 4:41 am 
Sam VarshavchikAug 12, 2003 7:02 am 
Michael JürgensAug 27, 2003 1:42 pm 
list...@serv.chAug 27, 2003 2:50 pm 
Michael JürgensAug 28, 2003 3:13 am 
list...@serv.chAug 28, 2003 12:26 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[courier-users] Re: courierdsn unable to inject bouncesActions...
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Aug 12, 2003 7:02:56 am
List:net.sourceforge.lists.courier-users

Anand Buddhdev writes:

One of my courier installations at a remote site has been giving me this error in the logs:

"courierdsn: Problems injecting bounce - submit failed."

It is running courier 0.42.2, built and installed via RPM.

I looked at the permissions on the submit binary, and also the permissions on the courier spool directory, /var/spool/courier, and I cannot see anything odd. I even compared the permissions to another installation, but they are the same.

Unfortunately, this error has been in the log for about 4 weeks now, but I only just noticed it, and the older logs have been rotated away, so I am unable to determine when the problem started.

Any ideas how I can debug this to find out where the problem lies?

It's tricky. Something about the bounce itself causes submit to reject the bounce message.

Since this is never supposed to happen, errors from submit are not logged.

stracing the courierdsn with the -f child process will also trace the submit child process, and should show what error message it generates.