Well at this point I will say that the upgrade to James 3.4 SNAPSHOT has worked, I finally found the remaining problem that had been overlooked. (this is a rather bad user trap IMHO and probably should be re-addressed.) There is a mailet defined in the mailetcontainer.xml that needs to be removed, (commented out) -
<mailet match="RemoteAddrNotInNetwork=127.0.0.1" class="ToProcessor"> <processor>relay-denied</processor> <notice>550 - Requested action not taken: relaying denied</notice> </mailet> if one is going to enable SMTP authorization. Yeah there is a lot of comments that say as much, in that file, but this is easily overlooked IMHO. Would be safer to automate the removal of this mailet when SMTP authorization is enabled and then in the rare cases where this is also wanted, require the installer to opt in rather than having to opt out. Just a thought.... Anyways thanks everyone for all your help, I will now start to set up all the rest of my domains and users that I need to support and see how far I get... If I have more questions I will start a new thread... Funny that I wasn't getting the notice "550 - Requested action not taken: relaying denied" in a bounce email... (but even that is a really bad error message that most users will not understand nor know what to do about it.) Marc.. On 02/19/2019 06:57 PM, Marc Chamberlin wrote: > Oh well never mind this exception about localhost, my bad, I had added > localhost to the domainlist as an experiment and that was not a good > idea. Removing it cleared up this exception, but I still cannot send > anything out... Still looking for a solution... > > Marc... > -- Linux Counter
