----- Original Message -----
From: "Stuart Roebuck" <[EMAIL PROTECTED]>
2000.12.01 05:46:34 337 (INFO) from Mailets: RemoteDelivery: Exception
deliverin
g mail (Mail975692793011-9-to-stuartroebuck.freeserve.co.uk:
javax.mail.Messagin
gException: 501 syntactically invalid HELO argument(s)
at
com.sun.mail.smtp.SMTPTransport.issueCommand(SMTPTransport.java:707)
at com.sun.mail.smtp.SMTPTransport.helo(SMTPTransport.java:417)
at
com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:24
9)
at javax.mail.Service.connect(Service.java:227)
at javax.mail.Service.connect(Service.java:131)
at javax.mail.Service.connect(Service.java:87)
at com.sun.mail.smtp.SMTPTransport.connect(SMTPTransport.java:105)
at
org.apache.james.transport.mailets.RemoteDelivery.deliver(RemoteDeliv
ery.java:127)
at
org.apache.james.transport.mailets.RemoteDelivery.run(RemoteDelivery.
java:274)
at java.lang.Thread.run(Thread.java:479)
Stuart,
This is a stack trace from the JavaMail API... it's apparently having
trouble negotiating with the remote mail server. In the RemoteDelivery
mailet, there should be a place to turn on debugging for that Session, and
then you'll be able to see the complete communication being sent between
JavaMail and the outgoing server.
Aside from this, here's one hunch... you've put something other than a valid
domain name in the <helloName> tag in james.conf.xml. That's what I would
guess is the problem if the remote server is choking on JavaMail sending a
helo command.
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives: <http://www.mail-archive.com/james%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
