BTW - I ran into this same issue using qmail/vpopmail. The problem continued when I switched over to James. I decided it was the firewall issue you describe because the problem did not exist when I moved qmail/vpopmail or James outside the firewall.
I found that enabling the smtp-auth (as has been suggested in this thread) AND disabling the HostsNotInNetwork solved the problem. Did you disable the hosts list and still experience the problem? It may become cumbersome to maintain the list of exact IP addresses as computers are added and removed from your network. Steve B. BTW - at that time I was using WinProxy - in case it matters. ----- Original Message ----- From: "Randahl Fink Isaksen" <[EMAIL PROTECTED]> To: "'James Users List'" <[EMAIL PROTECTED]> Sent: Thursday, May 23, 2002 12:12 AM Subject: RE: Relay prevention > Problem solved! > > I just got the green light from ordb.org: > > "The host you submitted at ORDB.org (212.242.50.198), has been > thoroughly checked, and does not seem to permit relaying." > > It turned out to be right what a couple of you suggested (thanks Serge > and others): Using the wildcard 10.0.0.* was the root of the problem > because as soon as I listed the exact IP-adresses, everything worked > fine. I could not prove this from what I found in the log files, but it > must have been a firewall issue. As Serge suggested maybe my firewall, > which is at 10.0.0.1 made it look like people from the outside came from > 10.0.0.1 which matches 10.0.0.*. So what I have done now is simply to > list most of the PCs in this network in the list of PCs which should be > allowed transmitting e-mails to the outer world. If I find the time, I > will check up on this to see if can figure out a smarter solution. <snip!> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
