I've noticed that in the latest release a message in a file repository will get corrupted, and the remote delivery is incorrectly diagnosing it as a problem with the remote server, instead of the local server. It goes something like this...
outgoing spool -------------- message 321 (corrupted) message 322 (ok) message 323 (ok) It tries to send message 321, but there's a failure. It then creates an error and asks for spool for the next message. However, message 321 is corrupted and refuses to go away, so the thread grabs message 321 again. The result is the fast and furious loop you're seeing. I got a less than friendly call from a mail server admin that was effectively getting a DOS attack from this problem in James as his server was receiving a failed delivery of message 321 over and over again. I'm still checking into why this is happening. I need to figure out why message 321 isn't getting deleted, as that problem with the repository is what's creating this condition. I don't know a workaround for this as I'm not sure what the delivery thread can do if the repository isn't doing what it's being told to do. Serge Knystautas Loki Technologies - Unstoppable Websites http://www.lokitech.com ----- Original Message ----- From: "Jacques Lema" <[EMAIL PROTECTED]> To: "James Developers List" <[EMAIL PROTECTED]> Sent: Saturday, November 24, 2001 9:37 AM Subject: James Endless loop bringing machine down > I now use james 2.01a (the binary that can be found on the website). > > For some reason the non-existence of a specific SMTP host makes this > remotedelivery relaunch itself and repeat endlessly (When started, the > James.Mailet.log would fill about 150mb log in a few minutes). I can't > believe this is just because the smtp host is down.. there must be something > else? > > You can find the full log here... which is basically the snippet below > repeated a million times (note that this doesn't contain the line where it > all started since I had to reboot my machine to be able to access it again > through SSH. I just relaunched and I had this result. Of course deleting the > mail that was causing this problem brought all back to normal. I think there > should definitely be a system to avoid any mail processing to enter an > infinite loop. Isn't there a way to limit the number of times an email tries > to get processed? > > http://www.meet-u.com/jmbuglog.gz > > > This is what gets repeated: > > Sat Nov 24 06:43:08 CET 2001 [INFO ] (James.Mailet): RemoteDelivery: > Sending failure message Mail1006424053509-1886-!1376559019-to-msn.fr > Sat Nov 24 06:43:08 CET 2001 [INFO ] (James.Mailet): RemoteDelivery: > Exception caught in RemoteDelivery.run(): > java.lang.reflect.UndeclaredThrowableException > Sat Nov 24 06:43:08 CET 2001 [INFO ] (James.Mailet): RemoteDelivery: > Remote delivery thread (0) will process mail > Mail1006424053509-1886-!1376559019-to-msn.fr > Sat Nov 24 06:43:08 CET 2001 [INFO ] (James.Mailet): RemoteDelivery: > attempting to deliver Mail1006424053509-1886-!1376559019-to-msn.fr > Sat Nov 24 06:43:08 CET 2001 [INFO ] (James.Mailet): RemoteDelivery: > attempting delivery of Mail1006424053509-1886-!1376559019-to-msn.fr to host > cpinssmtpe03.msn.com. to [[EMAIL PROTECTED]] > Sat Nov 24 06:43:08 CET 2001 [INFO ] (James.Mailet): RemoteDelivery: > Exception delivering message > (Mail1006424053509-1886-!1376559019-to-msn.fr) - Unknown SMTP host: > cpinssmtpe03.msn.com.; > nested exception is: > java.net.UnknownHostException: cpinssmtpe03.msn.com. > Sat Nov 24 06:43:08 CET 2001 [INFO ] (James.Mailet): RemoteDelivery: > Temporary exception delivering mail > (Mail1006424053509-1886-!1376559019-to-msn.fr: > javax.mail.MessagingException: Unknown SMTP host: cpinssmtpe03.msn.com.; > nested exception is: > java.net.UnknownHostException: cpinssmtpe03.msn.com. > at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:865) > at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:156 ) > at javax.mail.Service.connect(Service.java:234) > at javax.mail.Service.connect(Service.java:135) > at javax.mail.Service.connect(Service.java:87) > at com.sun.mail.smtp.SMTPTransport.connect(SMTPTransport.java:93) > at > org.apache.james.transport.mailets.RemoteDelivery.deliver(RemoteDelivery.jav > a:190) > at > org.apache.james.transport.mailets.RemoteDelivery.run(RemoteDelivery.java:38 > 7) > at java.lang.Thread.run(Thread.java:539) > > > > > > > > -- > 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]>
