Hi all,
Further digging (and then some more) revealed that dovecot wasn't the problem (of course). The port numbers (10001, 10002) finally put me on the right track. It turned out that de SRS daemon (pfix-srsd) had stopped for some reason. Doing
/etc/init.d/pfix-srsd restart
solved the issue. Now I'm only facing an SASL error, but that's outside the scope of this mailing list.
Hope I didn't waste too much of anyone's time with this question.
Aldo
-----Oorspronkelijk bericht----- Van: dovecot-bounces@dovecot.org [mailto:dovecot-bounces@dovecot.org] Namens Aldo & Caroline Verzonden: vrijdag 6 september 2013 11:59 Aan: dovecot@dovecot.org Onderwerp: [Dovecot] Dovecot 2.1.7 not starting properly, mail not delivered
On my debian box dovecot does not start properly any more, and mails don't get delivered or sent. I've googled around without finding any useful leads. Hopefully someone is willing to educate me. My guess is it must be a config problem after an upgrade, since I didn't change anything myself directly. Not sure when it started, since I this mail server is not our default machine (yet).
Symptoms
Upon
/etc/init.d/dovecot restart
my command line says
[ ok ] Restarting IMAP/POP3 mail server: dovecot.
But I find in /var/log/mail.log:
Sep 6 11:17:36 debian2 dovecot: master: Warning: Killed with signal 15 (by pid=19112 uid=0 code=kill) Sep 6 11:17:36 debian2 dovecot: master: Dovecot v2.1.7 starting up (core dumps disabled) Sep 6 11:17:37 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:38 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:39 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:40 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:41 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:42 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:43 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:44 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:45 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:45 debian2 postfix/cleanup[18466]: warning: tcp:127.0.0.1:10001 lookup error for "aldo@alcatoka.nl" Sep 6 11:17:45 debian2 postfix/cleanup[18466]: warning: 57B7D3640073: sender_canonical_maps map lookup problem for aldo@alcatoka.nl Sep 6 11:17:45 debian2 postfix/pickup[17004]: warning: maildrop/4EA313640071: error writing 57B7D3640073: queue file write error
I do NOT see a line like ... dovecot: auth-worker(default): pgsql: Connected to 127.0.0.1 (mailserver) as mentioned in this <https://workaround.org/ispmail/squeeze/setting-up-dovecot?page=1> tutorial, which I used to set up the previous Dovecot version (which worked OK).
When starting Dovecot from the command line with
dovecot -F -c /etc/dovecot/dovecot.conf
nothing is printed (as if the process is waiting for more input), while it should at least produce some output, right?
I'm running Debian 7.1 with an ext3 filesystem together with Postfix 2.9.6 on an x86 machine. CPU info: processor : 0 vendor_id : AuthenticAMD cpu family : 16 model : 6 model name : AMD Sempron(tm) 140 Processor cpu MHz : 800.000 cache size : 1024 KB
As far as I can tell, Postfix is running OK.
/etc/dovecot/dovecot.conf says:
# 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-686-pae i686 Debian 7.1 ext3 auth_mechanisms = plain login disable_plaintext_auth = no log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/var/vmail/%d/%n/Maildir mail_privileged_group = mail passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocols = imap pop3 service auth { unix_listener auth-master { group = vmail mode = 0600 user = vmail } user = root } ssl_cert = </etc/dovecot/dovecot.pem ssl_key = </etc/dovecot/private/dovecot.pem userdb { args = uid=3000 gid=3000 home=/var/vmail/%d/%n allow_all_users=yes driver = static } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } protocol lda { auth_socket_path = /var/run/dovecot/auth-master log_path = mail_plugins = sieve postmaster_address = aldo@alcatoka.nl }
As far as I understand, there must be a process (dovecot-auth?) that takes care of translating mail adresses, taking a string at port 10001 and returning the translated string on 10002. This process does not seem to kick off when dovecot restarts.
Please tell me if I'm thinking in the right direction, and - more importantly - what I need to do to get dovecot running. I will be happy to provide more test results if that helps, just tell me what you need.
Regards,
Aldo Verlinde