==================================================================
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=8753
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
==================================================================
Bug ID: 8753
Summary: Automatic expiry of vacation messages in SOGo broken
(Authentication failure for sogo user)
Classification: Contribs
Product: SME Contribs
Version: 9.0
Hardware: ---
OS: ---
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: smeserver-sogo
Assignee: [email protected]
Reporter: [email protected]
QA Contact: [email protected]
NOTE
====
Bug reproduced on a clean test install of SME9 (with only a single test user
account).
DESCRIPTION
===========
SOGo comes with support for vacation messages through sieve: in the settings in
sogo webmailer, users can define an expiration date for their vacation
messages. The following entry in /etc/cron.d/sogo in theory checks once a day
if any user's vacation message has expired:
-----------------------------
# Vacation messages expiration
# Make sure to set authname and authpassword with the credentials of a sieve
admin
0 0 * * * sogo /usr/sbin/sogo-tool expire-autoreply
sogo:<some_long_string>
-----------------------------
but this does not have the desired effect of disabling expired vacation
messages in sogo.
EXPECTED RESULT
===============
User's vacation auto-reply messages should expire once the expiration date is
met (ie. the corresponding sieve filter in user's home dir should be removed,
and sogo should uncheck the corresponding setting)
ACTUAL RESULT
=============
User's vacation auto-reply messages are not expired automatically.
REPRODUCE
=========
A vacation auto-reply including an expiration date was set and activated for
user test in SOGo webmailer settings.
I did not catch any related error messages in sogo logs, but was able to
reproduce the problem by running the command line from cron in a shell:
----------------------------
[root@smeserver ~]# sudo -u sogo /usr/sbin/sogo-tool -v expire-autoreply
sogo:<some_long_string>
2014-12-29 11:35:58.131 sogo-tool[4368] Checking user test
<0x0x1fffb88[SOGoCache]> Cache cleanup interval set every 1800.000000 seconds
<0x0x1fffb88[SOGoCache]> Using host(s) '127.0.0.1' as server(s)
2014-12-29 11:36:00.153 sogo-tool[4368] Could not login 'test' on Sieve server:
<0x0x228eb18[NGSieveClient]: socket=<NGActiveSocket[0x0x2297d88]: mode=rw
address=<0x0x229acd8[NGInternetSocketAddress]: host=localhost port=34462>
connectedTo=<0x0x2293068[NGInternetSocketAddress]: host=localhost port=4190>>>:
{RawResponse = "{ok = 0; reason = \"Authentication failed.\"; }"; result = 0; }
2014-12-29 11:36:00.162 sogo-tool[4368] An error occured while removing
auto-reply of user test
----------------------------
I noticed that sogo-tool attempted to login the 'test' user to sieve in order
to disable the vacation auto-reply message, so I tried the following on CLI:
----------------------------
[root@smeserver test]# sudo -u sogo /usr/sbin/sogo-tool -v expire-autoreply
test:<sme_password_of_testuser>
2014-12-29 11:49:09.899 sogo-tool[9336] Checking user test
<0x0x1e53268[SOGoCache]> Cache cleanup interval set every 1800.000000 seconds
<0x0x1e53268[SOGoCache]> Using host(s) '127.0.0.1' as server(s)
2014-12-29 11:49:10.041 sogo-tool[9336] Removed auto-reply of user test
----------------------------
which voila disabled the 'test' user's vacation auto-reply message as intented.
ADDITIONAL INFO
===============
- The erroneous behaviour is probably related to sogo now being a system
account, rather than a "real" user account as it was in previous versions. I
found a somewhat similar report on
http://comments.gmane.org/gmane.comp.groupware.sogo.user/16994 - and the way
sogo, sieve and dovecot interoperate on SME server.
- Note that in order to explore this bug, I manipulated the expiry date by
doing a doing a backup of the user's sogo preferences, manipulating the
Vacation End date in the backup file and restoring afterwards.
- There's a possibly related issue with the sogo-ealarms-notify entry in
/etc/cron.d/sogo leading to mails bouncing every minute between cron and a
(non-existant) sogo user account on the system. As both the expire-autoreply
and the sogo-ealarms-notify are designed to be run by the sogo user in the cron
entry, the cause for both problems may be the same?
INSTALLED RPMs
==============
Sogo installed as per Wiki (sans setting up the fws repo, because
smeserver-dovecot-extras seems to come from stephdl nowadays :-)
[root@smeserver ~]# rpm -qa *sogo* *dovecot*
smeserver-dovecot-1.4.0-16.el6.sme.noarch
dovecot-2.0.9-8.el6_6.1.x86_64
sogo-tool-2.2.12a-1.centos6.x86_64
dovecot-pigeonhole-2.0.9-8.el6_6.1.x86_64
sogo-ealarms-notify-2.2.12a-1.centos6.x86_64
sogo-activesync-2.2.12a-1.centos6.x86_64
smeserver-dovecot-extras-0.1.1-1.el6.sme.noarch
smeserver-sogo-1.3-7.el6.sme.noarch
sogo-2.2.12a-1.centos6.x86_64
--
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/
