1

Topic: Mailbox is full with SOGo notifications after 0.9.0!

==== Required information ====
- iRedMail version: 0.9.0
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Linux/BSD distribution name and version: Ubuntu 14.04.1 LTS x64
- Related log if you're reporting an issue:

Topic: /usr/sbin/sogo-tool expire-sessions 30

2015-01-05 18:26:01.561 sogo-tool[8054] Table 'sogo.sogo_sessions_folder' doesn't exist
/usr/sbin/sogo-tool: Uncaught exception ExecutionFailed, reason: Table 'sogo.sogo_sessions_folder' doesn't exist


Topic: /usr/sbin/sogo-ealarms-notify

<0x0xd61ca8[GCSAlarmsFolder]> -[GCSAlarmsFolder recordsForEntriesFromDate:toDate:]: cannot execute fetch: <MySQL4Exception: 0xd80a98> NAME:ExecutionFailed REASON:Table 'sogo.sogo_alarms_folder' doesn't exist
<0x0xd66d88[GCSAlarmsFolder]> -[GCSAlarmsFolder deleteRecordsForEntriesUntilDate:]: cannot delete record: <MySQL4Exception: 0xd33b58> NAME:ExecutionFailed REASON:Table 'sogo.sogo_alarms_folder' doesn't exist

====

Installed version 0.9.0 on Ubuntu 14.04.1 and all went well, but now when I login to my postmaster-account I see alot of e-mails fron SOGo with the ones above.

Seems the guide on the site that I followed is not updated to include the setup of SOGo, and how do we solve this?

----

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

2

Re: Mailbox is full with SOGo notifications after 0.9.0!

So I did a little digging on the server to help you further:

mysql> show databases;
+--------------------+
| Database           |
+--------------------+
| information_schema |
| amavisd            |
| cluebringer        |
| iredadmin          |
| mysql              |
| performance_schema |
| phpmyadmin         |
| roundcubemail      |
| sogo               |
| vmail              |
+--------------------+

And:

mysql> use sogo;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
mysql> show tables;
+----------------------+
| Tables_in_sogo       |
+----------------------+
| sogo_alarms_folder   |
| sogo_folder_info     |
| sogo_sessions_folder |
| sogo_user_profile    |
| users                |
+----------------------+

Then why the heck is it complaing that the table don´t exist when it does?

3

Re: Mailbox is full with SOGo notifications after 0.9.0!

Looks like a bug in iRedMail, will try to reproduce this issue and fix it.

Btw, did you install sogo manually or install it by iRedMail?

4

Re: Mailbox is full with SOGo notifications after 0.9.0!

ZhangHuangbin wrote:

Looks like a bug in iRedMail, will try to reproduce this issue and fix it.

Btw, did you install sogo manually or install it by iRedMail?

I did installed it with iRed, but my postmaster inbox was drained in mails from all the warning so I had to wipe the server. Now I´m running fine (after much as you will see on all the topics from today big_smile).

5

Re: Mailbox is full with SOGo notifications after 0.9.0!

Okay, so can we close this forum topic now?

6

Re: Mailbox is full with SOGo notifications after 0.9.0!

ZhangHuangbin wrote:

Okay, so can we close this forum topic now?

You can close it, but u need to try and reproduce it to see if u will see the bug like I did. smile

7

Re: Mailbox is full with SOGo notifications after 0.9.0!

I am also experiencing this issue, fresh install on CentOS 6.6.

What info/configs could I supply that might help you trace this issue?

Thanks!

8

Re: Mailbox is full with SOGo notifications after 0.9.0!

I cannot reproduce this issue, no notification emails from sogo at all.

9

Re: Mailbox is full with SOGo notifications after 0.9.0!

Hi,
also the same problem: fresh minimal install debian 7.7 + iredmail (mysql and only SOGo no iredmail)

10

Re: Mailbox is full with SOGo notifications after 0.9.0!

Does it happen if you login to SOGo once?

11

Re: Mailbox is full with SOGo notifications after 0.9.0!

Yes I was still connected in sogo and cycling in  ~ 30s is arrived 2 new mail  cron  : /usr/sbin/sogo-tool expire-sessions 30 &
cron /usr/sbin/sogo-tool: Uncaught exception ExecutionFailed, reason: Table 'sogo.sogo_sessions_folder' doesn't exist
I dont know if i am not connected in sogo as well come this email.I stopped the srv today will continue the config/debug

12

Re: Mailbox is full with SOGo notifications after 0.9.0!

Could you please show me your full /etc/sogo/sogo.conf file? Note: please remove password in this file before pasting.

13

Re: Mailbox is full with SOGo notifications after 0.9.0!

As an addition, I only received these messages 7 times (over 5 minutes) before it stopped.

14

Re: Mailbox is full with SOGo notifications after 0.9.0!

bennn wrote:

As an addition, I only received these messages 7 times (over 5 minutes) before it stopped.

Did you login to SOGo after 5 minutes?

15

Re: Mailbox is full with SOGo notifications after 0.9.0!

{
    // Official SOGo documents:
    //  - http://www.sogo.nu/english/support/documentation.html
    //  - http://wiki.sogo.nu
    //
    // Mailing list:
    //  - http://www.sogo.nu/english/support/community.html

    // Enable verbose logging. Reference:
    // http://www.sogo.nu/nc/support/faq/artic … -sogo.html
    //ImapDebugEnabled = YES;
    //LDAPDebugEnabled = YES;
    //MySQL4DebugEnabled = YES;
    //PGDebugEnabled = YES;

    // Daemon address and port
    WOPort = 127.0.0.1:20000;

    // PID file
    //WOPidFile = /var/log/sogo/sogo.log;

    // IMAP connection pool.
    // Your performance will slightly increase, as you won't open a new
    // connection for every access to your IMAP server.
    // But you will get a lot of simultaneous open connections to your IMAP
    // server, so make sure he can handle them.
    // For debugging it is reasonable to turn pooling off.
    //NGImap4DisableIMAP4Pooling = NO;

    SOGoProfileURL = "mysql://sogo:xxxxx@127.0.0.1:3306/sogo/sogo_user_profile";
    OCSFolderInfoURL = "mysql://sogo:xxxxx@127.0.0.1:3306/sogo/sogo_folder_info";
    OCSSessionsFolderURL = "mysql://sogo:xxxxx@127.0.0.1:3306/sogo/sogo_sessions_folder";

    // Default language in the web interface
    SOGoLanguage = English;

    // Specify which module to show after login: Calendar, Mail, Contacts.
    SOGoLoginModule = Mail;

    // Must login with full email address
    SOGoForceExternalLoginWithEmail = YES;

    // Allow user to change full name and email address.
    SOGoMailCustomFromEnabled = YES;

    // Enable email-based alarms on events and tasks.
    SOGoEnableEMailAlarms = YES;
    OCSEMailAlarmsFolderURL = "mysql://sogo:xxxxxx@127.0.0.1:3306/sogo/sogo_alarms_folder";

    // IMAP server
    //SOGoIMAPServer = "imaps://127.0.0.1:143/?tls=YES";
    // Local connection is considered as secure by Dovecot.
    SOGoIMAPServer = "imap://127.0.0.1:143/";

    // SMTP server
    SOGoMailingMechanism = smtp;
    SOGoSMTPServer = 127.0.0.1;
    //SOGoSMTPAuthenticationType = PLAIN;

    // Enable managesieve service
    //
    // WARNING: Sieve scripts generated by SOGo is not compatible with Roundcube
    //          webmail, don't use sieve service in both webmails, otherwise
    //          it will be messy.
    //
    SOGoSieveServer = sieve://127.0.0.1:4190;
    SOGoSieveScriptsEnabled = YES;
    SOGoVacationEnabled = YES;
    SOGoForwardEnabled = YES;

    // Memcached
    SOGoMemcachedHost = 127.0.0.1;

    SOGoTimeZone = "America/New_York";

    SOGoFirstDayOfWeek = 1;

    SOGoRefreshViewCheck = every_5_minutes;
    SOGoMailReplyPlacement = below;

    SOGoAppointmentSendEMailNotifications = YES;
    SOGoFoldersSendEMailNotifications = YES;
    SOGoACLsSendEMailNotifications = YES;

    // PostgreSQL cannot update view
    SOGoPasswordChangeEnabled = YES;

    // Authentication using SQL
   
    SOGoUserSources = (
        {
            type = sql;
            id = vmail_mailbox;
            viewURL = "mysql://sogo:xxxxxxx@127.0.0.1:3306/sogo/users";
            canAuthenticate = YES;

            // Default algorithm used when changing passwords.
            userPasswordAlgorithm = ssha;
            prependPasswordScheme = YES;

            // Use vmail.mailbox as global address book.
            // WARNING: This will search all user accounts, not just accounts
            // under same domain as login user.
            //isAddressBook = YES;
            //displayName = "Global Address Book";
        }
    );
   

    // Authentication using LDAP
    /* LDAP backend
    SOGoUserSources = (
        {
            type = ldap;
            hostname = "PH_LDAP_URI";
            baseDN = "PH_LDAP_BASEDN";
            //bindAsCurrentUser = YES;
            bindDN = "PH_LDAP_ADMIN_DN";
            bindPassword = "PH_LDAP_ADMIN_PW";
            filter = "objectClass=mailUser AND accountStatus=active AND enabledService=mail";
            scope = SUB;

            // The algorithm used for password encryption when changing
            // passwords without Password Policies enabled.
            // Possible values are: plain, crypt, md5-crypt, ssha.
            userPasswordAlgorithm = ssha;

            IDFieldName = mail;
            bindFields = (mail);
            CNFieldName = cn;
            // value of UID field must be unique on whole server.
            UIDFieldName = mail;
            IMAPLoginFieldName = mail;
            SearchFieldNames = (cn, sn, displayName, telephoneNumber, mail, shadowAddress);
            canAuthenticate = YES;
            displayName = "Global Address Book";
            id = ldap_auth;
            isAddressBook = YES;
        }
    );
    LDAP backend */
}

16

Re: Mailbox is full with SOGo notifications after 0.9.0!

Sorry to inform you that even though I uncheck the SOGo on the new install, I still recive notifications about SOGo and some errors.

17 (edited by lemmings125 2015-01-16 04:04:50)

Re: Mailbox is full with SOGo notifications after 0.9.0!

I have had the same issue with install on Debian Wheezy, i followed the install guide and have had to shut VPS down because the mailbox is flooded with same mails.

I have already reinstalled VPS and tried again.

I will investigate but if anyone has shed any light on the reason would be greatly appreciated.

When I looked this morning 1056 emails in Inbox and installed 11 hours.

UPDATE 15/01/2015

I have reinstall VPS image and tried again but had the same problems, I reinstalled again but this time did not select Roundcube when carrying out installation and I did not get the SoGo notification in my inbox any further once I had logged in to Sogo email and rebooted ????

Confused - why does iRedMail install to webmail interfaces SoGo and Roundcube, Am I missing something here.  Why not have one or other other ??

I need to do some further set-up as I have had to stop Apache (even though I selected Apache as my default webserver the installed still installed Nginx ??)

Was iRedMail-0.9.0 too early to be released on Debian Wheezy as its a complete mess.

18

Re: Mailbox is full with SOGo notifications after 0.9.0!

Hi,
yesterday I reinstalled the OS + downloaded the lest iredmail again and now all is ok...

19

Re: Mailbox is full with SOGo notifications after 0.9.0!

gh0st wrote:

Sorry to inform you that even though I uncheck the SOGo on the new install, I still recive notifications about SOGo and some errors.

I will try to reproduce this issue and come back to you with a fix.

20

Re: Mailbox is full with SOGo notifications after 0.9.0!

Hi ZhangHuangbin,

Were you able to figure out the root cause of this issue?
I installed a fresh 0.9.0 and having the same issue now.

The config:
  Debian Wheezy
  backend: ldap
  roundcube _not_ selected
  sogo _is_ selected

The error:

mail from sogo every 30 sec. there are two different messages, both originated from the two cronjobs that run every 1 min:

# iRedMail: SOGo session cleanup, should be run every minute.
# Ajust the [X]Minutes parameter to suit your needs
# Example: Sessions without activity since 30 minutes will be dropped:
*   *   *   *   *   /usr/sbin/sogo-tool expire-sessions 30

# iRedMail: SOGo vacation messages expiration
# The credentials file should contain the sieve admin credentials (username:passwd)
0   0   *   *   *   /usr/sbin/sogo-tool expire-autoreply -p /etc/sogo/sieve.cred

Error messages:

root@server:/var/spool/cron/crontabs# /usr/sbin/sogo-tool expire-sessions 30
2015-01-22 14:06:40.997 sogo-tool[5591] Table 'sogo.sogo_sessions_folder' doesn't exist
/usr/sbin/sogo-tool: Uncaught exception ExecutionFailed, reason: Table 'sogo.sogo_sessions_folder' doesn't exist

root@server:/var/spool/cron/crontabs# /usr/sbin/sogo-tool expire-autoreply -p /etc/sogo/sieve.cred
/usr/sbin/sogo-tool: Uncaught exception NoFetchInProgress, reason: No fetch in progress (channel=<MySQL4Channel[0x0x1feb170] connection=0x0x1e1b8e0>)
root@server:/var/spool/cron/crontabs#

Now looking at the mysql db, well, the tables are nto there. sogo db exists, but it's empty, no tables:


mysql> show databases;
+--------------------+
| Database           |
+--------------------+
| information_schema |
| amavisd            |
| cluebringer        |
| iredadmin          |
| mysql              |
| performance_schema |
| sogo               |
+--------------------+
7 rows in set (0.01 sec)

mysql> use sogo
Database changed
mysql> show tables
    -> ;
Empty set (0.00 sec)

mysql>



Cheers,
t

21

Re: Mailbox is full with SOGo notifications after 0.9.0!

chiby wrote:

Were you able to figure out the root cause of this issue?

Yes, fixed on Jan 14. here's commit log:
https://bitbucket.org/zhb/iredmail/comm … at=default

The root cause is, we installed and configured sogo, added cron jobs immediately. but we didn't run SOGo immediately to let SOGo populate required SQL tables. Commands in cron jobs will try to access SOGo SQL tables, but failed due to obvious reason (no SQL tables yet) with these error message.

if you start sogo service, no new error messages.

22

Re: Mailbox is full with SOGo notifications after 0.9.0!

ZhangHuangbin wrote:
chiby wrote:

Were you able to figure out the root cause of this issue?

Yes, fixed on Jan 14. here's commit log:
https://bitbucket.org/zhb/iredmail/comm … at=default

The root cause is, we installed and configured sogo, added cron jobs immediately. but we didn't run SOGo immediately to let SOGo populate required SQL tables. Commands in cron jobs will try to access SOGo SQL tables, but failed due to obvious reason (no SQL tables yet) with these error message.

if you start sogo service, no new error messages.

Thanks mate!
I restarted the service now and all good!

Thanks a lot your quick reply and fix!