ISPConfig 3.1.2 & SuSE Leap 42.2 - mail problems

Discussion in 'ISPConfig 3 Priority Support' started by macguru, May 2, 2017.

  1. macguru

    macguru Member HowtoForge Supporter

    Hi !
    After considerable amount of time and hackwork I've got ISPConfig 3.1.2 running on SuSE Leap 42.2. Apart from fixing multiple path and permissions, the real obstacle was AppArmor, which needs to be completely removed. syslog-ng needs to be installed instead of default logging daemon.
    Data was migrated from ISPConfig 3.0.5 running on SuSE 13.1 with migration tool.

    1) I had to copy "master.cf" and "main.cf" from my old 3.0.5 installation, otherwise it didn't worked. May be it wasn't best method, but debugging Postfix is a nightmare.
    SMTP seems to work fine although there are a lot of these messages. How to turn off mailman in ISPConfig completely?
    May 1 21:04:00 mail postfix/proxymap[5468]: error: open /etc/postfix/mysql-virtual_outgoing_bcc.cf: No such file or directory
    May 1 19:14:31 mail postfix/smtpd[16053]: error: open database /etc/mailman/virtual-mailman.db: No such file or directory
    May 1 19:14:31 mail postfix/smtpd[16053]: fatal: no SASL authentication mechanisms

    2) POP3/Dovecot. 3.0.5 had Dovecot 1.2. With 3.1.2 I have default for SuSE package Dovecot 2.2 - is it mistake to use newer version? During installation ISPConfig added its options - they are clearly visible. It works in a weird fashion - mail may arrive (in vmail folder) after 20 - 40 min, or may not arrive at all.
    Additionally, there are countless numbers of timed-out requests (Request 25063.1 timed out after 150 secs, state=1).
    Clam and Amavis seem to run fine.
    Anyone have a clue which options need to be changed in Dovecot along with the ones updated by ISPConfig installer ?

    PS. I'm ready to outsource this issue to anyone who can solve it for a reasonable fee. The only problem real tests can be done after work hours/late evening time.

    Thanks in advance.
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    The old ISPConfig 3.0.5 config is not fully compatible with ISPConfig 3.1, so some functions like dkim mail signing will not work when you copy over a old configuration.

    Create a file:

    /etc/postfix/mysql-virtual_outgoing_bcc.cf

    with this content:

    Code:
    user = ispconfig
    password = 3a887878eef32da26edd81b42e3b07e6
    dbname = dbispconfig
    table = mail_user
    select_field = sender_cc
    where_field = email
    additional_conditions = and postfix = 'y' and disabledeliver = 'n' and disablesmtp = 'n' and sender_cc != ''
    hosts = 127.0.0.1
    
    Replace the password string with one from the other .cf files that are in the postfix directory.

    then run:

    touch /etc/mailman/virtual-mailman
    postmap /etc/mailman/virtual-mailman

    ISPConfig writes the complete dovecot config, so there are no other changes needed on supported operating systems. But as your OS is not tested (supported), it is possible that it requires some changes.

    You might want to contact Florian from ISPConfig Business support, he is a mail server specialist: http://www.ispconfig.org/get-support/?type=ispconfig
     

Share This Page