[Building Sakai] Email archive - some emails not sending

[Sam Ottenhoff]

Right, I saw a "Size limit exceeded" error from another email of yours over
the weekend. This is an error from your LDAP server telling Sakai that it
has requested too many records from LDAP.  We tried to set the default for
maxObjectsToQueryFor low enough that it wouldn't be over any default LDAP
config while still being performant.  Is your limit of 50 a default from
the vendor or is it an aggressively-limited default set by your LDAP admin?
 The defaults I see are usually 1000 or 2000.

The maxObjectsToQueryFor was implemented in 2.9+ and changes the getUsers
method into a batch request method instead of iterating through single
requests.  So if you have a class roster of 500 students, the LDAP will
only receive 500/maxObjectsToQueryFor requests instead of the previous
behavior of 500 individual LDAP requests.

--Sam


On Mon, Sep 9, 2013 at 1:32 AM, Michael Osterman
<ostermmg.sakai at gmail.com>wrote:

> Hi Steve,
>
> I think I figured it out (way too late) last night.
>
> It seems to be an issue with our LDAP server configuration and the jldap
> provider's maxObjectsToQueryFor not getting along as documented in this
> comment:
>
> https://jira.sakaiproject.org/browse/SAK-15634?focusedCommentId=181037&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-181037
>
> I was able to reproduce this behavior in Site Info for a class with more
> than 50 students prior to adjusting the nsslapd-sizelimit on our LDAP;
> basically, the list of enrolled people is missing on a restart of Tomcat
> until you refresh Site Info to trigger getUsers() enough times to fill up
> the UserDirectory cache, 50 at a time. Once it got all the class cached,
> then the LDAP Exceptions went away. I could also see myself generating the
> errors on the LDAP server.
>
> I'm now 99% convinced this is why the professor's emails were failing (a
> subsequent test message today went through). The getUsers() was triggering
> an uncaught exception when the mail service was getting the list via
> getUsers(), and the outgoing email simply never happened.
>
> I also checked our mail server logs for all the prior failing mails for
> this professor, and I can see the email coming in to our @cleo.whitman.edulist address, and ZERO connections back from our Sakai server attempting to
> send the message.
>
> Keeping my fingers crossed that this fixed it.
>
> I'm still interested in debugging this more on our test instance to see
> where the actual exception is happening. Can your recommend the appropriate
> class to reference for increasing logging to DEBUG? Can't recall how to
> reference these.
>
> Cheers,
> Mike
>
>
> On Sun, Sep 8, 2013 at 4:03 PM, Steve Swinsburg <steve.swinsburg at gmail.com
> > wrote:
>
>> I've had an issue where certain email addresses were stopping the email
>> from going out to the entire list, but was never able to figure out why.
>> Can you try debug logging the emailservice to see exactly what it's doing?
>>
>> Cheers,
>> Steve
>>
>>
>> Sent from my iPad
>>
>> On 08/09/2013, at 12:35, Michael Osterman <ostermmg.sakai at gmail.com>
>> wrote:
>>
>> A professor just let us know that their students aren't received emails
>> sent to their class listserv (a.k.a. Email Archive address).
>>
>> The messages were indeed received by Sakai (we're on 2.9.x) as they are
>> listed in the Email Archive interface, but there is no log entry in
>> catalina.out that matches the messages.
>>
>> I've just sent a test message to confirm, that email does work to a
>> separate list, and the message is delivered as expected, and I have a log
>> entry like this as expected:
>>
>> 2013-09-07 16:14:51,622  INFO Thread-358570
>> org.sakaiproject.email.impl.BasicEmailService - sendToUsers
>> [rest removed]
>>
>> I checked the settings for the class, and everything seems to be correct:
>>
>> We've been getting intermittent reports of "email not working" since our
>> upgrade from 2.6.x to 2.9.x, sometimes related to Email Archive, sometimes
>> related to Announcements.
>>
>>  Has anyone experienced this problem, or does anyone have pointers for
>> getting more information on what's going on with the email service?
>>
>> Cheers,
>> Mike
>>
>> _______________________________________________
>> 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"
>>
>>
>
> _______________________________________________
> 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"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130909/b0a8b2a8/attachment.html