similar to: Dovecot wiki LMTP description

Currently I'm having massive problems with LMTP delivery into dovcot. dovecot/lmtp processes are piling up, eas using considerable amounts of CPU: # ps auxwww|fgrep dove root 20537 0.0 0.0 18124 1196 ? Ss 15:18 0:00 /usr/sbin/dovecot -c /etc/dovecot/dovecot.conf dovecot 20541 0.0 0.0 9620 1084 ? S 15:18 0:00 dovecot/anvil root 20542 0.0 0.0 9752

I updated dovecot today and all over a sudden I'm getting: Mar 6 14:40:46 mail postfix/lmtp[3150]: 3kz95y3nX3zCtTS: to=<recipient at backup.invalid>, relay=127.0.0.1[private/dovecot-lmtp], delay=88, delays=87/0.94/0.01/0.01, dsn=4.3.0, status=deferred (host 127.0.0.1[private/dovecot-lmtp] said: 451 4.3.0 <recipient at backup.invalid> Too many concurrent deliveries for user (in

Hi altogether, I am switching from dbmail 2.2 to dovecot 2.1.7, and I was able to do a successful transition of IMAP. But I had a very hard time with receiving mail, and in the end -- after loads of reading and debugging -- I broke down and failed. This is why I am asking you for your kind help. I only have virtual users and have set mail_uid = dovemail mail_gid = dovemail For authentication,

Am 18.02.2015 um 18:15 schrieb Robert Fantini: > I'm trying to figure out the exact line to put to /etc/postfix/main.cf > > for local lmtp deliver we use: > mailbox_transport = *lmtp:unix:private/dovecot-lmtp* > > for remote it is supposed to be:* lmtp:host:port* > > yet at the remote lmtp does not use ports. UNIX domain sockets are used > instead so just

Hi, I have a mailsystem where i have some local users with shell access and full home dirs which receive mail and also several SQL virtual users only for mail. With the virtual users, everything works fine. Mail is delivered via LMTP and also sieve works :) The SQL Lookup knows what to do with username at domain.com The problem is the system user. If exim delivers the mail to the lmtp

Ladies and gentlemen, good morning! With my first post to the list, may I begin by saying how impressed I have been by Dovecot's performance on our Debian server. We've configured it to run with Exim and Fetchmail, using Dovecot to manage professional and domestic emails for a small home office, serving a number of Windows and Linux clients both on the internal network and, when

Hi, what are the following messages supposed to tell me and does this indicate a problem? # systemctl status cyrus-imapd [...] master[3766]: unable to setsocketopt(IP_TOS): Operation not supported master[3766]: unable to setsocketopt(IP_TOS): Operation not supported [...] Exim says it can not connect to the lmtp socket even when selinux doesn?t get in the way. The configuration looks like

OK I got delivery from postfix to lmtp working , by changing from unix_listener to inet_listener . Reindl wrote "don't open the port for any other machine as the postfix server" I see that is important.. I assume that just a firewall setting? Or does the 'address' line in inet_listener lmtp have something to do with it? On Wed, Feb 18, 2015 at 12:37 PM,

I've been trying for some days to get postfix + dovecot + pigeonhole/sieve working on a CentOS-7 home server. I think I may have detected the problem; I read in /var/log/maillog Aug 4 11:29:13 alfred postfix/lmtp[14871]: 9C04C220A99: to=<tim at localhost.gayleard.eu>, orig_to=<tim at localhost>, relay=alfred.gayleard.eu[private/dovecot-lmtp], delay=971,

Hi there, I am trying to move from lmtpd (lmtpd.sf.net) to dovecot sieve. One thing used by some of powerusers are archiving mail automatically with autocreated folders based on year + month. Is there any good way to make that with sieve... One example require "fileinto"; if address :is ["From", "To"] "dovecot at dovecot.org" { fileinto

Hello again Reindl Harald I always thought Wietse Venema was only as smart as me ;-) seriously thank you for the help. On Tue, Feb 17, 2015 at 4:57 PM, Reindl Harald <h.reindl at thelounge.net> wrote: > > Am 17.02.2015 um 22:51 schrieb Robert Fantini: > >> I want to make sure that the postfix delivery does not give up trying to >> get the email delivered when the

On 29.03.2017 13:44, Steffen Kaiser wrote: > On Tue, 28 Mar 2017, chaouche yacine wrote: > > > I would like to study how dovecot manages quota, especially how it > deals with the maildirsize file if one chooses to implement quota > according to the maildir++ specification. > > Quota is managed by the plugin, which hooks into some events. Check out > >

Hello, given a Debian 9 system with Dovecot 2.2.34 installed from self-built packages made from the official tarball combined with Stephan Bosch's debian files (upgraded multiple times from packages made in a similar way). Today, I updated this system to 2.3.0.1 from the official repository at repo.dovecot.org. After the update, dovecot wouldn't start because of: > dovecot: master:

Hello Reindl, thank you for the response. I want to make sure that the postfix delivery does not give up trying to get the email delivered when the lmtp host is not reachable. I do not just want to assume that the default settings are correct for us. Are there postfix or other settings which can be checked and adjusted? On Tue, Feb 17, 2015 at 4:37 PM, Reindl Harald <h.reindl at

Hi, we are getting some core dumps with signal 6 in ltmp on a dovecot director proxy server, like this: Dec 5 14:31:51 sproxy1 dovecot: lmtp(29999): Panic: file lmtp-proxy.c: line 376 (lmtp_proxy_output_timeout): assertion failed: (proxy->data_input->eof) Dec 5 14:31:51 sproxy1 dovecot: lmtp(29999): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0() [0x363323d99a] ->

Several times we already had the problems, that accounts with more the 1.3 or 1.7 billion e-mails in one folder run out-of-memory, even if vsize_limit of 750 MB is set. In this case, the lmtpd-process haven't been able to allocate more memory to read/write/update the index-files and crashed (and the index-files become corrupted at the end.) [Please -- don't discuss about the need of

Hi, I hope you're all right. I describe below the scenario where the problem occurs. I'm trying to activate a master user [1] to be able to access all the boxes of all users by imap. I have configured the dovecot-master-users [2] file with the appropriate permissions. When I try to access, for example with roundcube, through user at mydomain.com*my_master_user at not-exist.com I see in the

?? Saw the new repository notification, and figured what the heck I would try letting it upgrade me from the current v2.2.22 release that apparently is in the Ubuntu 16.04 packages, to the new repository release of v2.3.0. ?I followed the info on repo.dovecot.org, and first it started bitching about lmtp (dovecot: master: Fatal: service(lmtp) access(/usr/lib/dovecot/lmtp) failed: No such

https://dovecot.org/releases/2.2/dovecot-2.2.34.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.34.tar.gz.sig * CVE-2017-15130: TLS SNI config lookups may lead to excessive memory usage, causing imap-login/pop3-login VSZ limit to be reached and the process restarted. This happens only if Dovecot config has local_name { } or local { } configuration blocks and attacker uses

https://dovecot.org/releases/2.2/dovecot-2.2.34.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.34.tar.gz.sig * CVE-2017-15130: TLS SNI config lookups may lead to excessive memory usage, causing imap-login/pop3-login VSZ limit to be reached and the process restarted. This happens only if Dovecot config has local_name { } or local { } configuration blocks and attacker uses