Using JAMES to handle outgoing email

[Byron Appelt]

We have a system that we point to JAMES as the outgoing email server.  We occasionally see instances where emails get queued up and do not get sent until JAMES is restarted. We also see a fair amount of the following in the logs although I am not yet sure if it is related.   17/11/05 23:41:39 WARN spoolmanager.orbcomm: Message Mail1132292499074-10 reached the end of this processor, and is automatically deleted. This may indicate a configuration error.   While researching this I ran across the following:   http://bugs.sakaiproject.org/jira/browse/SAK-1449;jsessionid=F4424E53F6C1D0A6E41AD38DE5F0E9A2?actionOrder=desc   which contains the following:   % James is not *supposed* to be handling outgoing email, only incoming. % % The "smtp" setting in your config is to identify the smtp server to % contact for outgoing email. % % While it's an interesting idea to point at your local James for % this, this is not something I've ever tried. I recommend you setup % a valid smtp server that will take mail from your application % server. % % All that said, I have seen James take over outgoing email even when % so configured with a valid smtp server not localhost, which is % naughty of it, and not a great idea, because of problems I've seen % in the way it does this. This is one reason we don't run James on % port 25 in our environments.   Is it a valid configuration to point an application to JAMES to send email?   Byron K. Appelt Lead Developer - Devices and Gateways   Connect. Control. Create. byron@sensorlogic.com www.SensorLogic.com