[Building Sakai] James email issues

[Soo-il Kim]

So if you are not sure... turn off James(smtp.enabled=false...
actually that's default)
Use other SMTP server. (Ask your system administrator with estimated
volume of messages about port number. He/She will configure your Sakai
server as permitted mailer.)

SOO

On Wed, Oct 7, 2009 at 11:55 PM, Soo-il Kim <kimsooil at gmail.com> wrote:
> James is not only SMTP but also POP3 and NNTP server. The James has
> its own setting. Default server name would be "localhost" somewhere.
> You have to make sure James has configured properly. I guess... some
> of message would be stucked in the loop of mail process.
>
> See more: http://james.apache.org/server/index.html
>
> SOO
>
> On Wed, Oct 7, 2009 at 11:43 PM, Joshua Swink <joshua.swink at gmail.com> wrote:
>> On Wed, Oct 7, 2009 at 8:14 PM, Soo-il Kim <kimsooil at gmail.com> wrote:
>>> Actually first of all, you should not have smtp.enabled=true in
>>> sakai.properties if you use other SMTP server. this setting turns on
>>> James mail server which is built-in with Sakai distribution.
>>>
>>> SOO
>>
>> What is the difference when it's turned off?
>>
>>
>>>
>>> On Wed, Oct 7, 2009 at 10:45 PM, Joshua Swink <joshua.swink at gmail.com> wrote:
>>>> We've had a few email issues and I just wanted to run them by the list
>>>> in case other people have dealt with the same problems.
>>>>
>>>> 1) When messages are unspooled and sent out, it tries to send them to
>>>> the server named in the email address rather than using our configured
>>>> SMTP server. In other words if the message is intended for
>>>> "user at ucmerced.edu" it tries to connect to ucmerced.edu port 25. This
>>>> does not work, obviously.
>>>>
>>>> 2) About every other message is spooled. There's no apparent reason
>>>> for this, and nothing in the tomcat or the james log. We're talking
>>>> about 1 message per minute coming in at most.
>>>>
>>>> 3) We had one incident where the incoming connections to James (from
>>>> our email relay servers) were piling up in CLOSE_WAIT state. After 30
>>>> of them piled up, it was impossible for mail to be delivered to Sakai
>>>> any more. The connections did not close until I restarted Sakai.
>>>>
>>>> I am going to change all of the logging in James' environment.xml to
>>>> DEBUG. It would be especially helpful if there were any other places
>>>> that debugging output could be turned on.
>>>>
>>>> --
>>>> Joshua Swink
>>>> _______________________________________________
>>>> sakai-dev mailing list
>>>> sakai-dev at collab.sakaiproject.org
>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>>
>>>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>>>>
>>>
>>
>