similar to: LMTP with many aliases and replication

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 One other question; has anybody considered writing a tool that integrates Dovecot's deliver script and an LMTP server? I'm architecting my system so that my internet facing SMTP is Postfix, but the mail folders live on a different machine. Right now, I'm considering putting a highly restricted Postfix on the internal machine,

I have my MTA (Postfix) check Dovecot2 LMTP for existing users. No other delivery is done; this is a virtual/LMTP-only setup. I define known users in a Dovecot passwd-file, specified in conf.d/10-auth.conf passdb { args = ... username_format=%n /stor01/vmail/auth.d/%d/passwd e.g., vi /stor01/vmail/auth.d/mx1.domain1.com/passwd myuser:{scheme}####:... mail to: myuser at mx1.domain1.com

Op 08/05/2018 om 10:34 schreef Olaf Hopp: > Hi, > > I had an email with 58 recipients in the "To" and 13 in the "CC" > Delivering it from exim to dovecot lmtp panics (see below) > Panic: file smtp-address.c: line 533 (smtp_address_write): assertion > failed: (smtp_char_is_qpair(*p)) > > # 2.3.1 (c5a5c0c82): /etc/dovecot/dovecot.conf > # Pigeonhole

Hi, I've recently switched to LMTP as I'm now using mdbox. However since switching, mails sent to the root account do not get delivered due to the following error: May 1 18:20:17 Server1 postfix/lmtp[13019]: CAEE91F851: to=<root at test.com>, relay=mail.test.com[private/dovecot-lmtp], delay=1097, delays=1096/0.45/0.43/0.46, dsn=4.3.0, status=deferred (host

Hi everyone, I'm running a test environment with a proxy in front of working replication between two backends but redirecting in case of a backend failure is not working. Nov 09 21:03:59 imap-login: Error: proxy(mail at example.net): connect(10.5.29.211, 143) failed: Connection refused (after 0 secs, local=10.5.29.201:38333) I appreciate any advice. Regards Patrick Proxy: # 2.2.7:

Hi! I set up two mail servers with Postfix and Dovecot and I would like to sync all mails between the servers. So I set up replication. Now I'm still getting the following errors: =======Server 1======= Sep 11 13:43:52 mx0 dovecot: master: Dovecot v2.1.7 starting up (core dumps disabled) Sep 11 13:43:52 mx0 dovecot: auth-worker(4245): mysql(127.0.0.1): Connected to database mailserver Sep

Am 06.03.2015 um 14:44 schrieb Ralf Hildebrandt: > 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 >

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

This has been fixed in a later version of Dovecot, so your best course of action is to upgrade to some more recent version. I'd recommend 2.2.36. Aki > On 10 December 2018 at 18:28 admin via dovecot <dovecot at dovecot.org> wrote: > > > Dear suscribers. > > I just dont understand this error. Don't know where to look first. If > someone have already meet

Hello, when receiving mails for multiple recipients via LMTP, I often see the following messages on our servers: > May 22 11:06:10 sinon dovecot[44304]: lmtp(119718): Connect from $IP$ > May 22 11:06:11 sinon dovecot[44304]: lmtp($USER1$)<119718><2HnmOgIR5Vym0wEA22L5Rg>: msgid=<$MSGID$>: saved mail to INBOX > May 22 11:06:11 sinon dovecot[44304]:

Hi all, I hope it's okay to bump this once after four months. In the meantime we updated to 2.2.26.0 and our problem still persists: After unsubscribing from a shared mailbox, the subscription instantly re-appears. A pcap was attached to my original mail, in case it has something to do with dsync: http://dovecot.org/pipermail/dovecot/2016-September/105419.html Is anyone on this mailing list

Hi, Some time ago I posted the below but never got a reponse that I could work with. So i am retrying now in the hope that there might be a better idea/suggestion on how to approach this. Situation; I have two nodes, which should replicate to eachother. My main machine receives most mail and the other one receives mostly system messages and should get replicated. (This used to be delivered on

I'm getting the following error when using dovecot replication: dovecot: imap(foo at bar.com): Error: open(/var/dovecot/replication-notify-fifo) failed: No such file or directory I guess this has something to do with the fact that every user is chrooted in it's own homedir. Does dsync support dsync notification when all users are chrooted? lmtp does not seem to have this problem so new

I'm trying to set up replication between two servers and I've hit a snag. I have two users and am using mbox files. If anybody has a sample config file for a simple system like mine I would really be grateful to see it. Thanks, The error I'm getting is: Mar 23 14:07:31 knute2 dovecot: doveadm(192.168.3.100,nobody): Error: user nobody: Initialization failed: Namespace

Hi, I have just built a new pair of similar machines both running CentOS 8.2 (selinux disabled) and Dovecot 2.3.8 (9df20d2db). One machine is a VPS (host A) and one is on my home network (host B). The idea is that they are set up in a master/master config with Dovecot replication. I seem to have this 95% working but there is one strange issue I can?t work out. Currently B is a perfect replica

I have two dovecot instances that replicate to each other. Mail arrives into "post" and it is generally accessed via IMAP on "france". Changes (moves/expunge etc) on "france" seem to replicate back to "post" more or less immediately. But this seems to happen only for this user. (Some) other users' (e.g. me) mail generally replicates more or less

On 24.06.2019 16:25, Reio Remma wrote: > On 24.06.2019 8:21, Aki Tuomi wrote: >> On 22.6.2019 22.00, Reio Remma via dovecot wrote: >>> Jun 22 16:55:22 host dovecot: dsync-local(user at host.ee)<>: Error: >>> Remote command returned error 84: ssh -i /home/vmail/.ssh/vmail.pem -l >>> vmail backup.host.ee doveadm dsync-server -D -uuser at host.ee >>>

Hi, I have two Dovecot 2.3.8 (on RHEL 8.2) servers. Replication works great except in one situation. What works: * If one server receives an email, it is immediately available on the other server. * If an email is deleted via IMAP from one server, it is immediately deleted from the other server. What doesn't work: If a user retrieves (download + delete) an email via POP3 (Thunderbird), then

I'm running dovecots replicator successfully on 33 mailboxes. There is only one mailbox (the biggest one, 167000 mails) that is not replicating successfully. After 10 minutes the "source" starts logging these messages: dovecot: dsync-local(foo at example.com): Error: dsync(imap.netsend.nl): I/O has stalled, no activity for 600 seconds dovecot: dsync-local(foo at example.com):

Dear Dovecot community, As discussing on IRC with Aki, I have the following thing happening: I got an alert from my mailservice last night that I was running over quota. My quota reached almost 91% (coming from 30%) in one day. I do not recall receiving so much email (we talk about multiple gb?s additional space usage), so something was acting up. When I logged into my mailservers (I?ll