SMTP Problems

[Brent L Johnson <br...@bjohnson.net>]

When sending emails thru Jame's SMTP server they tend
to get put into the spool table (Im using 2.2.0a15)
as "outgoing" and after a few minutes I find them set
as "error" and they never go anywhere.

I've looked thru the logs in james/apps/james/logs/*
but didnt see any errors (other than fetchmail errors..
see my other fetchmail thread for info on that).

I also checked the james/logs/phoenix.log to see if
I saw anything there - nothing.  Anyone have any
ideas as to how I can track down whats going on?

I'm having to completely bypass my James server right
now due to some serious issues (some most likely
related to configuration issues on my part)..
but when I cant send or reliably receive email I can't use it :)

Thanks,

- Brent


---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org

RE: SMTP Problems

["Noel J. Bergman" <no...@devtech.com>]

> When sending emails thru Jame's SMTP server they tend
> to get put into the spool table (Im using 2.2.0a15)
> as "outgoing" and after a few minutes I find them set
> as "error" and they never go anywhere.

If they were in outgoing, they are in the RemoteDelivery queue.  You should
see delivery errors in the mailet log.  You might also check the dnsserver
log for messages.  My prediction is that your DNS configuration is the
problem for both RemoteDelivery and FetchMail.

	--- Noel


---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org