==================================================================
  Please DO NOT REPLY to this mail or send email to the developers
  about this bug. Please follow-up to Bugzilla using this link:
    http://bugs.contribs.org/show_bug.cgi?id=5524

  Have you checked the Frequently Asked Questions (FAQ)?
    http://wiki.contribs.org/SME_Server:Documentation:FAQ

  Please also take the time to read the following useful guide:
    http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
==================================================================





--- Comment #2 from H. de Visser <[email protected]>  2009-10-24 17:28:56 ---
(In reply to comment #1)
> I would report in zarafa's forums.. maybe this was corrected in more recent
> releases

Done that: http://forums.zarafa.com/viewtopic.php?f=11&t=3008

Only response i get in relation to preventing this is upping the
max_allowed_packet parameter in \etc\my.cnf.

Thing is, the max_allowed_packet in sme by default is set to 16M which is also
above the default SME qmail MaxMessageSize of 15M and php's UploadMaxFilesize
of 10M. Zarafa is also set to store attachments to the filesystem. So i think
it's weird for mysql to complain about a big message.

The original sent message was not denied because it was to big (it's still in
my sent items, Thunderbird reports: 9955KB), it's the returned delivery
failure. So maybe it's something in the way SME is configured or something else
there can be done to avoid this from happening to others.

I hope to get some help here and if it is determined that it's all down to
Zarafa then this could happen to all of us using this contrib and more people
might 'complain' about this at Zarafa.

-- 
Configure bugmail: http://bugs.contribs.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
_______________________________________________
Mail for each SME Contribs bug report
To unsubscribe, e-mail [email protected]
Searchable archive at http://lists.contribs.org/mailman/public/contribteam/

Reply via email to