Hi Matt >starting of james 3.4 so I wasn't aware of this screw up. So, according >to the current master branch the prefered way is to just comment it out. > Neither doing that nor changing the tag to <priority> fixes the problem I see though. As already said, everything looks fine - I can log in and my webmail client behaves as expected, including interacting with the SMTP side of things.
To rule out any oddness from my webmail client (which there should not be), I can test by telnet to port 25. James says 250 2.6.0 Message received and just as when sending from webmail, the message is spooled according to the logs, but never delivered; no errors or warnings in the logs, so no clue where to look next. If something in the smtpserver config needs a tweak it's not obvious what that is and much of the docs seem to be inapplicable to this version of james. The one thing that occurs is that maybe maildir storage has not been well tested; I'll revert the configs to use the default Derby database and if I see anything better with that, I'll post an update. -- David Matthews [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
