Hmm... maybe I didn't state that correction.

I have a user ( [EMAIL PROTECTED] ) that is trying to send an email to ( [EMAIL PROTECTED] ). After adding my own domain (domainA) to the James config and trying to send email to dude - James threw my email in the spam list (and yeah I checked the lists and my domain isn't on the lists - we only send out 20 or so emails a day... very small shop ).

What I was expecting was that after I added my own domain (domainA) to the James config that users of domainA would be able to send mail to anyone, but that didn't work until after I removed RemoteAddrInLocal's matcher.

On Tuesday, October 14, 2003, at 05:11 PM, Noel J. Bergman wrote:

There must be a bug somewhere or something. I went into the James block
and in the <servernames>. I left autodetect="true". Same for
autodetectIP. I then added <servername>domainA.com</servername> blah
blah blah.

I then restarted the server and connected from an email client and
tried to sent mail from a user at domainA.com and the mail was sent
to spam.

If you enable DEBUG for the spoolmanager, you can see what path caused the
message to go into SPAM. If domainA.com is added to <servernames>, then it
should be consider a local domain, and should not have gone to
RemoteDelivery at all.


--- Noel


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



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



Reply via email to