Bowie Bailey wrote: > > It reproduces quite nicely for me. I've got several messages in my > queue that give this error whenever they attempt delivery. Anything I > can do to help you track it down? > > I'm not familiar with debugging C code, but I will gladly trace > processes and send you dumps or whatever you need if you can give me > instructions.
One of the things you can do to watch for errors is install "ngrep" or "ethereal" and use them to watch the network traffic to and from the host receiving the message that's causing a problem. ngrep is very simple: ngrep host <remote MX> If you want to get a trace of the process, first determine the PID of the "courieresmtp" process that's running as a child of courierd. Next, get the queue ID of one of the messages that causes the problem. "mailq" should provide you with that. Then, start tracing the process using strace: strace -f -p <pid> -o /tmp/couriersmtp-trace.pid -s 512 And, in a separate terminal, flush the message: courier flush <qid> Watch the logs while you do this. As soon as you see the error message in the log file, you can use Ctrl+c to stop tracing the smtp process. You may want to restart courierd afterward, since strace leaves processes stopped under some circumstances, and I don't recall if courierd would be affected. _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
