We know that there is a problem if the error messages can't get sent 'cos they too are pointed to non-local addresses, I'm not sure how this affects your situation though.
d. > -----Original Message----- > From: Lucas Gonze [mailto:[EMAIL PROTECTED]] > Sent: Saturday, January 26, 2002 5:39 PM > To: James Users List > Subject: bug: resend doesn't work > > > [N.B.: As you can see from the recent flurry of messages, I just > spent a few > minutes writing a better bug report for the "takes forever" bug. > The root cause > was a user error on my part. However, there is a real James bug, > as follows.] > > Bug summary: > If the initial send of a message fails, the resend will never happen. > > Steps to reproduce: > 1) Ensure that forwarding won't work. One way is to unset the DNS server > setting in james.conf.xml. > 2) Compose a user message and send it out via a James user > account. The message > forward will fail and the message will be left in the James > outbound queue. > 3) Fix forwarding. One way is to correct the DNS server setting in > james.conf.xml and restart James. > 4) The unsent message left in the outbound spool will not get sent. > > Comments: > This bug might also be triggered if the machine hosting James had > a temporary > service disruption, such as a reboot or connectivity outage. > > > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
