Eddie:
I had exactly the same problem recently when going through a reconfiguration using new name servers, domain names etc. The problem (I think) was that I was posting an email to a remote address and the remote processor was sending the message using a from address "<name>@<machine-name>". For memory I manged to resolve it by turning off autodetect on the james host names configuration (but is was very much a case of trying this and that and the other until I had something working).
Steve.
Eddie Bush wrote:
I've setup James per the instructions on the web site - in the FAQ. My server runs behind a firewall - and I'm non-static. I use dyndns.org to set my IP for public consumption - this all works just fine for web access.
When I send mail TO an account on the server, the mail goes through and it is delivered. However, when I send mail FROM an account on the server to the "outside world" - or even to someone local - my mail looks like it is going out, but it never arrives. Closer inspection shows it's going to the spam folder.
I have set my local IP pool up in the "not a local address" handler, but I still have this same behavior. Would any of you nice folks be able to shoot me some advice?
(I think it's possible my domain/ip-range or something has been tagged as a spammer, as the email I sent to my SBC account wound up in the "bulk mail" folder there. Could this have some affect?)
Thanks!
Eddie Bush
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.519 / Virus Database: 317 - Release Date: 9/20/2003
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
