View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0002065||SOGo||Web Mail||public||2012-10-24 06:02||2012-11-15 10:45|
|Target Version||2.0.2a||Fixed in Version||2.0.2a|
|Summary||0002065: Reply-to equals NULL|
Randomly, when a user composes a new message, the field reply-to equals null@domain. The issue occurs rarely.
See the message https://inverse.ca/sogo/lists/arc/users/2012-10/msg00291.html
|Tags||No tags attached.|
I know it a lot to ask but it would be nice to try to isolate this problem, in a reproducible manner. Try to toy around with memcached when you're about to compose a mail, etc.
We'll have to do the same thing to reproduce the issue, so a little bit of help here would be good.
I have never faced the issue directly.
Nevertheless, I'll try to catch it when occuring.
Awaiting the opportunity to reproduce the issue, I show here an excerpt of the content of a malformed mail:
You wrote: "The users haven't the right to modify this field in the options." How do yo control this? Have you modified the template of the preferences module? The "reply to email" field is always editable in the official version of SOGo.
For the problematic account, does the "reply to email" field appear empty in the preferences module?
This is not account specific.
In our installation approx. 10 emails per day will have that wrong "Reply-To:" out of an average of 20,000 emails send per day via SOGo.
Sorry, we could not reproduce this relyable.
Is the preference value set when you query sogo-tool?
sogo-tool user-preferences get defaults <uid> SOGoMailReplyTo
When not set, you should see :
2012-11-12 13:28:11.525 sogo-tool Value for key "SOGoMailReplyTo" not found in defaults
For the user stephan (whose part of one mail is reproduced above), the command displays:
/usr/sbin/sogo-tool user-preferences get defaults stephan SOGoMailReplyTo
Nov 12 19:50:03 sogo-tool : <0x0x2762200[SOGoCache]> Cache cleanup interval set every 300.000000 seconds
Here are his preferences:
preferences = (
Please try the next nightly builds. They should build this night ..
I've installed the nightly builds of the 14th of november and I'm going to log the reply-to on the mail gateway.
The fix for attachments "corruption" is also included in the nightly builds. The fix is in SOPE.
Okay. The nightly build of the 14th of November is now installed and is being used by our users. Let's see.
The nightly build is up for 20 hours and there has not been any header which equals null@...
Reopen the ticket if the problem still occurs.
|2012-10-24 06:02||flevee||New Issue|
||Target Version||=> 2.0.3|
|2012-10-29 14:21||ludovic||Note Added: 0004733|
|2012-10-29 14:48||flevee||Note Added: 0004734|
|2012-11-05 08:02||flevee||Note Added: 0004772|
|2012-11-06 08:33||francis||Note Added: 0004780|
|2012-11-08 08:39||Christian Mack||Note Added: 0004800|
|2012-11-12 13:30||francis||Note Added: 0004825|
|2012-11-12 13:54||flevee||Note Added: 0004826|
|2012-11-12 16:42||francis||Note Added: 0004832|
|2012-11-14 05:57||flevee||Note Added: 0004844|
|2012-11-14 06:50||ludovic||Note Added: 0004845|
|2012-11-14 08:43||flevee||Note Added: 0004846|
|2012-11-15 04:01||flevee||Note Added: 0004850|
|2012-11-15 10:44||francis||Fixed in Version||=> 2.0.2a|
|2012-11-15 10:44||francis||Target Version||2.0.3 => 2.0.2a|
|2012-11-15 10:45||francis||Note Added: 0004858|
|2012-11-15 10:45||francis||Status||new => resolved|
|2012-11-15 10:45||francis||Resolution||open => fixed|
|2012-11-15 10:45||francis||Assigned To||=> francis|