1

Topic: SOGo

==== Required information ====
- iRedMail version (check /etc/iredmail-release): 0.9.5-1
- Linux/BSD distribution name and version: Ubuntu 14.04.4 LTS (GNU/Linux 3.19.0-61-generic x86_64)
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): mysql
- Web server (Apache or Nginx): Apache
- Manage mail accounts with iRedAdmin-Pro? yes
- Related log if you're reporting an issue:
====

Dear,

Upgrade went smoothly. I initiated the upgrade after aptitude full-upgrade resulted in mails for postmaster every minute or so (14.04 fully updated).

Mails originate from cron

and typically contain

Return-Path: <sogo@email.xxxxxxx.be>
Delivered-To: postmaster@xxxxxxx.be
Received: by email.xxxxxxx.be (Postfix)
    id ABD67238530E; Sat, 11 Jun 2016 19:32:01 +0200 (CEST)
Delivered-To: sogo@email.xxxxxxx.be
Received: from email.xxxxxxx.be (localhost [127.0.0.1])
    by email.xxxxxxx.be (Postfix) with ESMTP id A4A30238530D
    for <sogo@email.xxxxxxx.be>; Sat, 11 Jun 2016 19:32:01 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at email.xxxxxxx.be
Received: from email.xxxxxxx.be ([127.0.0.1])
    by email.xxxxxxx.be (email.xxxxxxx.be [127.0.0.1]) (amavisd-new, port 10024)
    with ESMTP id polKBYTPGBu6 for <sogo@email.xxxxxxx.be>;
    Sat, 11 Jun 2016 19:32:01 +0200 (CEST)
Received: by email.xxxxxxx.be (Postfix, from userid 999)
    id 3BE4A238530A; Sat, 11 Jun 2016 19:32:01 +0200 (CEST)
From: root@email.xxxxxxx.be (Cron Daemon)
To: sogo@email.xxxxxxx.be
Subject: Cron <sogo@email> /usr/sbin/sogo-tool expire-sessions 30; /usr/sbin/sogo-ealarms-notify
Content-Type: text/plain; charset=ANSI_X3.4-1968
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/var/lib/sogo>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=sogo>
Message-Id: <20160611173201.3BE4A238530A@email.xxxxxxx.be>
Date: Sat, 11 Jun 2016 19:32:01 +0200 (CEST)

<0x0x20b1ea8[SOGoProductLoader]> SOGo products loaded from '/usr/lib/GNUstep/SOGo':
<0x0x20b1ea8[SOGoProductLoader]>   Appointments.SOGo, ContactsUI.SOGo, MailerUI.SOGo, Mailer.SOGo, CommonUI.SOGo, MainUI.SOGo, SchedulerUI.SOGo, Contacts.SOGo, AdministrationUI.SOGo, PreferencesUI.SOGo, MailPartViewers.SOGo
[so-category-info] did not find exported SoClass 'SOGo' in product <0x0x2308a18[SoProduct]: loaded code-loaded bundle=/usr/lib/GNUstep/SOGo/MainUI.SOGo #classes=8 #categories=4 rm=0x0x230b158>!


I’ve also found this : https://lists.inverse.ca/sogo/arc/users … 00247.html
quote: I have asked this a week ago, this is what has been replied by the developers:
"It's a warning that should be silenced - it should still work.”



Now, I would like to silence this cronjob (>/dev/null 2>&1) but, I can't find the crontab. If I change SOGo from
sogo:x:999:999:SOGo daemon:/var/lib/sogo:/usr/sbin/nologin
to
sogo:x:999:999:SOGo daemon:/var/lib/sogo:/bin/bash
I can still not edit cron of SOGo

Where is this located & how can I change it?

Thanks in advance,

Jord Wegge

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: SOGo

jwegge wrote:

Where is this located & how can I change it?

The cron job is for sogo user, you can edit it with 'crontab -e -u sogo'.

3

Re: SOGo

I am also having the same problem. I tried sending the cronjob output to /dev/null but still got e-mails. I ended up having to put MAILTO="" into the top of the crontab of the sogo to stop the incessant e-mails.

4

Re: SOGo

You may append this to the command:

2>&1 >/dev/null

Or:

&>/dev/null

5

Re: SOGo

Be mindful that the first line in the crontab is actually composed of 2 commands on one line, so you need to do something like:

 *   *   *   *   *   /usr/sbin/sogo-tool expire-sessions 30 >/dev/null 2>&1; /usr/sbin/sogo-ealarms-notify >/dev/null 2>&1