similar to: Avoid "451 4.4.0 Remote server not answering (timeout while waiting for reply to DATA reply)"

Hi Timo and All, how does Dovecot act when an MTA tries to deliver a multiple recipient message to a LMTP proxied system? Does it uses server affinity table for each recipient? I use lmtp_destination_recipient_limit = 1 setting in postfix to avoid multiple recipient delivery. Is it right? I use lmtp_destination_concurrency_limit = 1 too, but i think that it's useless or, maybe, it can

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 >

Hi all, I tried Tinc 1.1 from git on 4 nodes, each one in a datacenter. They were able to ping each other, etc... but I had problem with multicast, nothing seemed to pass (all is OK with Tinc 1.0.23). I checked logs and on every nodes I have a lot of: Failed to decrypt and verify packet And Error while decrypting: error:00000000:lib(0):func(0):reason(0) So I get back to 1.0.23 which works

Hi, we are experiencing similar sporadic data timeout issues with dovecot 2.0.20 as in http://dovecot.org/pipermail/dovecot/2011-June/059807.html at least once a week. Some mails get temporarily deferred in the postfix queue since dovecot director lmtp refuses them and the mails are delivered at a later time. The problem applies to mails delivered to single users as well as distribution lists

You could remove them with sieve in the latest version of pigeonhole. On Mar 24, 2015 7:33 AM, Florent B <florent at coppint.com> wrote: > > I know about RFC's, but that could be an option, not enabled by default.

Thank you for your report, we'll look into it! Aki > On December 27, 2017 at 8:16 PM Florent B <florent at coppint.com> wrote: > > > Hi, > > This repository does not work with Aptly. > It seems "architecture" line is wrong in InRelease file (needs to be > "Architectures:" instead of "Architecture:"). > And

* Reindl Harald <dovecot at dovecot.org>: > lmtp_destination_concurrency_limit on postfix side It's not a postfix issue. postfix is merely reporting what Dovecot said. -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer

Hello Florent, How did you proceed with the upgrade? Did you follow the recommended steps guide to upgrade ceph? (mons first, then OSDs, then MDS) Did you interrupt dovecot before upgrading the MDS specially? Did you remount the filesystem? Did you upgrade the ceph client too? Give people the complete scene and someone might be able to help you. Ask on ceph-users list too. Regards, Webert

Hi all, I just joigned this list, so I'm sorry if this problem has already been reported. I'm running Dovecot 2.0.13 on many servers, one for POP/IMAP access, others for LDA, others for authentification only, etc. All servers are accessing a shared file system, based on MooseFS (www.moosefs.org). The FS is mounted using FUSE. All my Dovecot servers have this configuration :

> On October 20, 2017 at 12:37 PM Florent B <florent at coppint.com> wrote: > > > Hi, > > We use Dovecot packages from http://xi.dovecot.fi/debian/. > > Could it be possible to serve it with HTTPS ? > > Thank you. > > Florent Hi! It has now https enabled with valid certificate. Aki

On Mon, Dec 7, 2015 at 7:20 PM, Florent B <florent at coppint.com> wrote: > Hi everyone, > > I already posted about this issue, but I can't find the old thread. > > I have a cluster of 5 nodes, running Proxmox 4, and Tinc as "virtual > switch" for my nodes : on each node, a bridge "vmbr1" where Tinc is > connected, provides me a secured network

why dont you place a service dependency on your tinc service init/systemd files to depend on your fuse/mount service? On Tuesday, 23 August 2016, Florent B <florent at coppint.com> wrote: > Hi everyone, > > I have a special setup were hosts files of Tinc are stored in a > directory mounted by fuse and shared across my hosts (Proxmox /etc/pve). > > On boot, sometimes Tinc

Try to disable ExperimentalProtocol. Florent B <florent at coppint.com> 于2018年8月10日周五 下午9:16写道： > > Hi, > > Is it possible to completely disable encryption with Tinc 1.1 ? > > I set in my configuration : > > ExperimentalProtocol = no > Cipher = none > Digest = none > > But it does not seem to disable encryption (same performance). > > Is it possible

Hi all, I have a little problem with Dovecot 2.1.17 and MailDir accounts. I was using a shared file system (MooseFS), and all was pretty stable. Now I'm switching to CephFS, and Dovecot LMTP have problem to deliver mails. Very often, on large accounts, LMTP processes are running for a few hours before delivering the message. When I strace it, I can see that they are reading (open and stat

Hi all, I have two nodes, connected to a switch, using Tinc 1.1 from git. They connect each other with sptps, and to other nodes in the Internet with old protocol because they have Tinc 1.0. There is no problem with remote nodes, but between my 2 local nodes, they see 1518 PMTU. But local network is 1500 MTU !!! So nodes can ping each other but larger data does not go. test1=sllm1 test2=sllm2

It's not. In fact it's explicitly telling you that it's *not* forwarding. On 22 December 2015 at 15:55, Florent B <florent at coppint.com> wrote: > Hi, > > I have a lot of messages like this in my Tinc 1.1-git log : > > Sending packet from host5 (MYSELF port 655) to host4 (192.168.0.4 port > 655) via host4 (192.168.0.4 port 655) (UDP) > > Is it expected ?

This smells like https://github.com/gsliepen/tinc/pull/104 - are you sure you're using latest HEAD? How often does this occur? Does it correlate with other events such as nodes joining or leaving? Does it occur more often if you reduce the value of KeyExpire? On 22 December 2015 at 16:10, Florent B <florent at coppint.com> wrote: > Hi, > > With latest Tinc 1.1 git code, I have

seems that you want your others services to depend on tinc, and not to set tinc to stop after the network has stopped On Wednesday, 24 August 2016, Florent B <florent at coppint.com> wrote: > Hi everyone, > > On many systems (Debian Jessie, Tinc 1.1 from git) using unit file > provided in git, I can see that when I "reboot", Tinc seems to stop > before others

On 7 December 2015 at 17:20, Florent B <florent at coppint.com> wrote: > I have a cluster of 5 nodes, running Proxmox 4, and Tinc as "virtual > switch" for my nodes : on each node, a bridge "vmbr1" where Tinc is > connected, provides me a secured network for my VMs (connected to that > bridge). > > When I move (hot move) a VM from a host to another, I

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