> Look in the logs if james has made delivery attempts.
> apps/james/logs/*.log
>
> Stefano

As stefano says, check the (James) logs!  More specifically,
apps/james/logs/mailet-*.log

Look for lines like:
[date] [time] INFO  James.Mailet: RemoteDelivery: ...

They should point you in the right direction.

The problem you are seeing is probably nothing to do with james.

>From the server running james, check that you can do MX record lookups using
the configured dns server.  Some adsl routers that provide dns
proxying/caching only allow A/CNAME/NS lookups, and don't support MX
lookups. (use a tool like nslookup or dig to check it out):
dig @213.239.57.3 yahoo.com mx
Should return lots of mx records.

If you cant do mx lookups then use a dns server that can - eg your ISP's dns
server.

Second, check that you can connect to an external mail server via telnet.
Lots of ISPs, block these connections to try and cut down on spam/viruses
coming from their networks.

telnet mx1.mail.yahoo.com 25

You should get "220 YSmtp mta152.mail.re2.yahoo.com ESMTP service ready"

If this doesnt work, then it's a router/ISP issue.

If this does work, then check the james logs carefully.
Also look for the message in the address-error, or error repositories.

Daniel.







---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to