September 2011 - dovecot

[Dovecot] Crash in director/lmtp-proxy (lmtp_proxy_output_timeout)
by Jan-Frode Myklebust 01 Sep '11

01 Sep '11

FYI, we saw one panic on our director/lmtp-proxy yesterday. It's running dovecot v2.0.13, so it very well might have been fixed already.., but here it is anyway: Aug 31 11:33:31 loadbalancer1 dovecot:: lmtp(4119): Panic: file lmtp-proxy.c: line 370 (lmtp_proxy_output_timeout): assertion failed: (proxy->data_input->eof) Aug 31 11:33:31 loadbalancer1 dovecot:: lmtp(4119): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0 [0x3aabc3bb70] -> /usr/lib64/dovecot/libdovecot.so.0 [0x3aabc3bbc6] -> /usr/lib64/dovecot/libdovecot.so.0 [0x3aabc3b083] -> dovecot/lmtp [0x406c90] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handle_timeouts+0xcd) [0x3aabc46a8d] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x68) [0x3aabc47a48] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x2d) [0x3aabc466fd] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x3aabc34fe3] -> dovecot/lmtp(main+0x144) [0x404034] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x32ae81d994] -> dovecot/lmtp [0x403e39] Aug 31 11:33:31 loadbalancer1 dovecot:: master: Error: service(lmtp): child 4119 killed with signal 6 (core dumps disabled) On postfix side at the same time, we saw a few different messages about: postfix/lmtp[5178]:: 849FD1C024: lost connection with loadbalancers.example.com[192.168.42.15] while sending end of data -- message may be sent more than once so I suspect this crash took down all active lmtp-proxyed connections. -jf

1 0

[Dovecot] lmtp bouncing -- Invalid parameters (in reply to MAIL FROM command)
by Jan-Frode Myklebust 01 Sep '11

01 Sep '11

I just configured postfix' virtual_transport to point at my dovecot director, but am seeing occational problems like this: Aug 31 11:50:06 smtpgw postfix/lmtp[5339]: 69E2F5410D: to=<email(a)example.net>, relay=loadbalancers.example.net[192.168.42.17]:24, delay=0.15, delays=0.14/0.01/0/0, dsn=5.5.4, status=bounced (host loadbalancers.example.net[192.168.42.17] said: 501 5.5.4 Invalid parameters (in reply to MAIL FROM command)) but can't find anything interesting in the dovecot logs.. Anybody have ideas for how to make postfix play nice with dovecot's lmtp ? smtpgws% rpm -q postfix postfix-2.3.3-2.1.el5_2 loadbalancers% rpm -q dovecot dovecot-2.0.13-2 backendmailstorers% rpm -q dovecot dovecot-2.0.13-2 -jf

2 3

[Dovecot] Proprietary mail storage.
by Alex Cherniak 01 Sep '11

01 Sep '11

I have a large existing read-only collection of mails packaged in individual zip files as <rfc822 file>+<some additional info>. Is it possible (and how difficult) to create a proprietary plugin (like gzip) which will open a zip file, extract mail and pass it back to Dovecot? Where do I start? If plugin is not the right approach, what is? Another question is how will this affect Dovecot performance and how to avoid any significant degradation. Any help is appreciated.Thanks.

3 9

Re: [Dovecot] Multiple domains to one inbox and temporary redirects...
by Nick Rosier 01 Sep '11

01 Sep '11

Simon Brereton wrote: > Hi > > Can anyone point me to a howto to arrange for multiple domains to deliver to one inbox with Dovecot? For example, user1(a)example.com and user1(a)example.net should both be delivered to /var/spool/mail/virtual/example.net/user1 > > Currently, I have the dovecot LDA set as: > > dovecot unix - n n - - pipe > flags=DRhu user=mailsystem argv=/usr/lib/dovecot/deliver -f ${sender} -d ${user}@${nexthop} > > > and in dovecot.conf: > > mail_location: maildir:/var/spool/mail/virtual/%d/%n > > For some domains only, I need to override that mail_location. > > > Related to that, when user1 leave and user2 would like to receive user1's email, how can I get it so that email to user1(a)example.com is delivered to user2(a)example.com? Previously when I was using Postfix to deliver the mails, I could change the maildirloc in the DB - but I’m not sure how to accomplish this with dovecot LDA. > > I'm using Postfixadmin to manage users and have server alias-domains. All mail sent to an alias-domain is delivered to the other domain. Quite easy if you've got postfixadmin already setup. Otherwise I think you could configure virtual_alias_maps in postfix to something like hash:virtual_domains virtual_domains: @example.net @example.com N.

4 3