> 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.
You should post your configuration and mailet*.log for the delivery attempts. > 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. You should post your configuration. > Is it a valid configuration to point an application to JAMES to send email? Sure, James RemoteDelivery mailet has been created to send mails. If your james is on a dial-up/dynamic IP you could find problems sending mails to some server. This is not a problem in james but a feature/filter of other servers: you can configure James to use a relay server (see RemoteDelivery configuration). Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
