Unable to log in to send/receive mail.

Discussion in 'Installation/Configuration' started by Marc Chamberlin, Jul 5, 2018.

  1. Marc Chamberlin

    Marc Chamberlin New Member

    I have not yet been able to get postfix/dovecot to send/receive emails yet although both services are up and running. I am running on OpenSuSE Leap 42.3 and will add the output from htf_report.txt below. I suspect this problem has something to do with mysql/mariadb as indicted by the following rather ominous warning messages I am getting in the Mail log file whenever I try to access the email server -

    Code:
    2018-07-05T09:55:58.067522-07:00 bigbang postfix/pickup[3076]: 106698113B: uid=0 from=<root>
    2018-07-05T09:55:58.068560-07:00 bigbang postfix/proxymap[10708]: warning: mysql:/etc/postfix/mysql-virtual_outgoing_bcc.cf is unavailable. unsupported dictionary type: mysql
    2018-07-05T09:55:58.069352-07:00 bigbang postfix/cleanup[11104]: warning: proxy:mysql:/etc/postfix/mysql-virtual_outgoing_bcc.cf lookup error for "[email protected]"
    2018-07-05T09:55:58.070025-07:00 bigbang postfix/cleanup[11104]: warning: 106698113B: sender_bcc_maps map lookup problem -- message not accepted, try again later
    Any idea what this means and how to fix? Thanks in advance, Marc...

    Code:
    bigbang:/etc/dovecot # cat htf_report.txt | more
    
    ##### SERVER #####
    IP-address (as per hostname): ***.***.***.***
    IP-address(es) (as per ifconfig): ***.***.***.***, ***.***.***.***
    [INFO] ISPConfig is installed.
    
    ##### ISPCONFIG #####
    ISPConfig version is 3.1.12
    
    ##### VERSION CHECK #####
    
    [INFO] php (cli) version is 5.5.14
    
    ##### PORT CHECK #####
    
    [WARN] Port 465 (SMTP server SSL) seems NOT to be listening
    [WARN] Port 22 (SSH server) seems NOT to be listening
    
    ##### MAIL SERVER CHECK #####
    
    [WARN] I found no "submission" entry in your postfix master.cf
    [INFO] this is not critical, but if you want to offer port 587 for smtp connections you have to enable this.
    [WARN] I found no "smtps" entry in your postfix master.cf
    [INFO] this is not critical, but if you want to offer SSL for smtp (not TLS) connections you have to enable this.
    
    ##### RUNNING SERVER PROCESSES #####
    
    [INFO] I found the following web server(s):
            Unknown process (httpd-prefork) (PID 2466)
    [INFO] I found the following mail server(s):
            Unknown process (smtpd) (PID 13139)
    [INFO] I found the following pop3 server(s):
            Dovecot (PID 22154)
    [INFO] I found the following imap server(s):
            Dovecot (PID 22154)
    [INFO] I found the following ftp server(s):
            PureFTP (PID 22199)
    
    ##### LISTENING PORTS #####
    (only           ()
    Local           (Address)
    [anywhere]:110          (22154/dovecot)
    [anywhere]:143          (22154/dovecot)
    [anywhere]:8080         (2466/httpd-prefork)
    [anywhere]:80           (2466/httpd-prefork)
    [anywhere]:8081         (2466/httpd-prefork)
    ***.***.***.***:53              (12609/named)
    ***.***.***.***:53              (12609/named)
    [localhost]:53          (12609/named)
    [anywhere]:21           (22199/pure-ftpd)
    [localhost]:631         (2001/cupsd)
    [localhost]:953         (12609/named)
    [anywhere]:25           (13139/smtpd)
    [anywhere]:443          (2466/httpd-prefork)
    [anywhere]:993          (22154/dovecot)
    [anywhere]:995          (22154/dovecot)
    [localhost]:9000                (1998/php-fpm.conf))
    [localhost]10           (22154/dovecot)
    [localhost]43           (22154/dovecot)
    [localhost]716          (3498/kdeconnectd)
    *:*:*:*::*:53           (12609/named)
    *:*:*:*::*:21           (22199/pure-ftpd)
    *:*:*:*::*:25           (13139/smtpd)
    *:*:*:*::*:993          (22154/dovecot)
    *:*:*:*::*:995          (22154/dovecot)
    *:*:*:*::*:3306         (21956/mysqld)
    
    ##### IPTABLES #####
    
    (In order to shorten this message, I deleted the iptables report, but can post it later if needed...)
    
     
  2. florian030

    florian030 Well-Known Member HowtoForge Supporter

    unsupported dictionary type: mysql
    Did you installed postfix-mysql?

    Check the postfix modules with
    postconf -m
     
  3. Marc Chamberlin

    Marc Chamberlin New Member

    When I checked the postfix modules I got the following output -
    Code:
    postconf -m
    btree
    cidr
    environ
    fail
    hash
    inline
    internal
    ldap
    lmdb
    memcache
    mysql
    nis
    pcre
    pgsql
    pipemap
    proxy
    randmap
    regexp
    socketmap
    static
    tcp
    texthash
    unionmap
    unix
    However, when I checked to see if postfix-mysql package was installed I discovered that it wasn't, so I went ahead and installed it. That lead me to the next missing package error, the mailman package apparently is needed also and wasn't installed either.
    Question - Shouldn't the ispconfig.sh script have insured that these packages were installed?

    That got me further, though still no joy getting postfix/dovecot working. I know I got a number of issues remaining to solve but want to tackle these one at a time so the next issue I think I need to address is these warning messages I am seeing after I start up the postfix service -
    Code:
    
    Jul 06 09:37:54 bigbang postfix/proxymap[5261]: warning: mysql:/etc/postfix/mysql-virtual_outgoing_bcc.cf is unavailable. open /e...rectory
    Jul 06 09:37:54 bigbang postfix/cleanup[5260]: warning: proxy:mysql:/etc/postfix/mysql-virtual_outgoing_bcc.cf lookup error for "...in.com"
    Jul 06 09:37:54 bigbang postfix/cleanup[5260]: warning: 5C11481268: sender_bcc_maps map lookup problem -- message not accepted, t...n later
    Jul 06 09:37:54 bigbang postfix/pickup[5257]: warning: maildrop/446ED813BA: error writing 5C11481268: queue file write error
    Jul 06 09:37:54 bigbang postfix/pickup[5257]: warning: 6965C81268: message has been queued for 19 days
    Jul 06 09:37:54 bigbang postfix/pickup[5257]: 6965C81268: uid=0 from=<root>
    Jul 06 09:37:54 bigbang postfix/proxymap[5261]: warning: mysql:/etc/postfix/mysql-virtual_outgoing_bcc.cf is unavailable. open /e...rectory
    Jul 06 09:37:54 bigbang postfix/cleanup[5260]: warning: proxy:mysql:/etc/postfix/mysql-virtual_outgoing_bcc.cf lookup error for "...in.com"
    Jul 06 09:37:54 bigbang postfix/cleanup[5260]: warning: 6965C81268: sender_bcc_maps map lookup problem -- message not accepted, t...n later
    Jul 06 09:37:54 bigbang postfix/pickup[5257]: warning: maildrop/163AF81388: error writing 6965C81268: queue file write error
    
     
  4. florian030

    florian030 Well-Known Member HowtoForge Supporter

    As long as the /etc/postfix/mysql-* files are not used/readable by postfix, this can't work.
    There is no official script that installes ispconfig on opensuse. Beside this: i would not use ispconfig with opensuse. I prefer debian/ubuntu
     
  5. Marc Chamberlin

    Marc Chamberlin New Member

    Hi Florian030, thank for replying! I am not sure why you are making the assertion that the /etc/postfix/mysql-* files are not used/readable by postfix, my look at the permissions on these files show that they are indeed readable by all members of the postfix group. What is more relevant, I think, is that there is no such file called /etc/postfix/mysql-virtual_outgoing_bcc.cf and I don't know where to get this file.

    I don't have the luxury/option of changing distros and in the interest of finding a solution to make life easier for myself and my users, I am more than willing to work with the ISPConfig developers to help build and maintain support for OpenSuSE. I am willing to share any modifications I make that are necessary to get ISPConfig to work under OpenSuSE. Fair enough? ;)
     
  6. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    Did you re-install ISPConfig after installing the missing packages?
    Try doing resync from the ISPConfig panel, chapter 4.4.3.1 Resync in Manual.
    Have you made bug report for that install script that did not install all needed packages?
     
  7. Marc Chamberlin

    Marc Chamberlin New Member

    Yes
    I tried doing resync on all services, still no joy.
    Yes - I generally wait until developers or someone in authority tells me it is OK to submit a bug report since the issue could be already known, has a workaround, or... You can see my report at https://git.ispconfig.org/ispconfig/ispconfig3/issues/5074

    After I now to a restart of the postfix service the mail log file shows these sort of representative error/warning messages.
    Code:
    2018-07-08T15:50:20.844168-07:00 bigbang postfix/postfix-script[22867]: stopping the Postfix mail system
    2018-07-08T15:50:20.847816-07:00 bigbang postfix/master[22133]: terminating on signal 15
    2018-07-08T15:50:21.116584-07:00 bigbang postfix/postfix-script[22959]: warning: group or other writable: /etc/postfix/.
    2018-07-08T15:50:21.119399-07:00 bigbang postfix/postfix-script[22960]: warning: group or other writable: /etc/postfix/./ssl/cacerts
    2018-07-08T15:50:21.136477-07:00 bigbang postfix/postfix-script[22976]: starting the Postfix mail system
    2018-07-08T15:50:21.150123-07:00 bigbang postfix/master[22978]: daemon started -- version 3.2.0, configuration /etc/postfix
    2018-07-08T15:50:21.156345-07:00 bigbang postfix/cleanup[22982]: error: open database /etc/mailman/virtual-mailman.db: No such file or dire
    ctory
    2018-07-08T15:50:21.165394-07:00 bigbang postfix/proxymap[22983]: error: open /etc/postfix/mysql-virtual_outgoing_bcc.cf: No such file or d
    irectory
    2018-07-08T15:50:21.165588-07:00 bigbang postfix/pickup[22979]: warning: 2843A81372: message has been queued for 3 days
    2018-07-08T15:50:21.165775-07:00 bigbang postfix/pickup[22979]: 2843A81372: uid=0 from=<root>
    2018-07-08T15:50:21.173606-07:00 bigbang postfix/proxymap[22983]: warning: mysql:/etc/postfix/mysql-virtual_outgoing_bcc.cf is unavailable.
     open /etc/postfix/mysql-virtual_outgoing_bcc.cf: No such file or directory
    2018-07-08T15:50:21.173864-07:00 bigbang postfix/cleanup[22982]: warning: proxy:mysql:/etc/postfix/mysql-virtual_outgoing_bcc.cf lookup err
    or for
     
  8. florian030

    florian030 Well-Known Member HowtoForge Supporter

    You should fix "error: open /etc/postfix/mysql-virtual_outgoing_bcc.cf: No such file or". Either remove this from the main.cf or check, if the file exists with the right permissions and that you can connect to mysql with the credentilas from this file.

    As alreayd written in #4 : there is no official script for installing a server with ispconfig.
     
  9. Marc Chamberlin

    Marc Chamberlin New Member

    Thanks again Florian for your response. I have removed this line -

    Code:
    sender_bcc_maps = proxy:mysql:/etc/postfix/mysql-virtual_outgoing_bcc.cf
    doesn't seem like something I or our users would ever need or use, though I am not exactly sure what or how ispconfig uses this map or what it does specifically with it.

    Yes, understood, but if ispconfig is supplying this file, and configuring /etc/postfix/main.cf so it can be used by postfix and/or mysql, and the expectation is to find this file in /etc/postfix then isn't it the responsibility of the ispconfig installation and/or it's runtime scripts to set up and place a copy of mysql-virtual_outgoing_bcc.cf in the /etc/postfix directory. You seem to be implying that this issue is caused by a mistake in the installation of the servers, but I don't see how it could be.

    Anywise, since this seems to be a good enough solution for this particular issue, lets close this particular issue and move on to the next. Do you are anyone have any insight as to what is causing the other error -

    Code:
    x/cleanup[22982]: error: open database /etc/mailman/virtual-mailman.db: No such file or directory
     
  10. till

    till Super Moderator Staff Member ISPConfig Developer

    The file /etc/postfix/mysql-virtual_outgoing_bcc.cf should be created by the ISPConfig install.php script. It get's created for other distributions, so it's an issue in the OpenSuSE part. The OpenSuSE part has not been updated or tested for quite a while as there is no real demand for that Distribution from our users anymore. I've added it to the bug tracker.
     

Share This Page