similar to: LMTPs between proxy and backend

Displaying 20 results from an estimated 1000 matches similar to: "LMTPs between proxy and backend"

2013 Dec 03
1
disconnecting (disconnected by server)
Hi all, I just recognized a lot of log entries like this on my proxy: Dec 03 13:50:54 imap-login: Info: proxy(mail at example.com): disconnecting 1.2.3.4 (Disconnected by server): user=<mail at example.com>, method=PLAIN, rip=1.2.3.4, lip=2.4.6.8, TLS, session=<qk02v6DsJwBTlUQX> There are no similar entries on the backends. What does this mean? Something I have to worry about?
2017 Aug 23
0
socketpair failed: Too many open files on Debian 9
You probably need to increase ulimit -n Aki On 23.08.2017 14:10, Patrick Westenberg wrote: > Hi @all, > > after re-installing one of my two frontends/proxy-servers I get the > following error messages after some time (sometimes after 1h, sometimes > after 24h): > > > 11:23:55 imap-login: Error: socketpair() failed: Too many open files > 11:23:55 imap-login: Error:
2017 Aug 23
0
socketpair failed: Too many open files on Debian 9
Hello, are you using systemd? May be you have to edit unit-file for dovecotservice and increase filelimit LimitNOFILE=infinity Hajo Am 23.08.2017 um 14:21 schrieb Patrick Westenberg: > I haven't done this on the old, working machine. > > So there must be a difference between Debian 7 and 9 how open files are > handled? > > Regards > Patrick > > > > Aki
2018 Aug 06
2
AW: 2.3.2.1 - relay to lmtps from other lan host
You have lmtp as unix socket configured but want to access from remote via tcp socket? I think you need inet_listener instead of unix_ listener ----- Originale Nachricht ----- Von: "?????" <vtol at gmx.net> Gesendet: 06.08.18 - 20:14 An: dovecot <dovecot at dovecot.org> Betreff: 2.3.2.1 - relay to lmtps from other lan host > Hi, > > looked into the [ dovecot wiki
2018 Aug 06
2
2.3.2.1 - relay to lmtps from other lan host
Hi, looked into the [ dovecot wiki ] but a search for [ lmtps ] came up empty and thus hoping to get some assistance here. I am trying to relay with [ msmtp ] via [ lmtps ] from a lan host other than [ dovecot ] is running on. [ dovecot config ] > service lmtp { > ? unix_listener lmtp { > ??? #mode = 0666 > ? } [ ss -wxl | grep lmtp ] > u_strLISTEN 0????? 100???
2018 Aug 06
0
AW: 2.3.2.1 - relay to lmtps from other lan host
Right, now I got then > service lmtp { > ? unix_listener lmtp { > ??? #mode = 0666 > ? } > > ? inet_listener lmtp { > ???? address = 172.24.109.6 > ??? port = 24 > ? } > } and [ msmtp ] is connecting indeed. Does TLS/STARTTLS need to be added to [ inet_listener lmtp ] in order to facilitate [ lmptps ]? If so what is the syntax? Right now this error comes up: >
2017 Oct 21
2
Proxy lmtps
Hi, when proxying lmtp from director to backend, director does not use STARTTLS. Delivering mails with postfix via lmtps to backend or director works encrypted. Is there a way to force the use of STARTTLS on dovecot director lmtp proxy? Regards, Matthias -- BOFH excuse #446: Mailer-daemon is busy burning your message in hell. (hbox storage?)
2017 Aug 23
3
socketpair failed: Too many open files on Debian 9
Hi @all, after re-installing one of my two frontends/proxy-servers I get the following error messages after some time (sometimes after 1h, sometimes after 24h): 11:23:55 imap-login: Error: socketpair() failed: Too many open files 11:23:55 imap-login: Error: socketpair() failed: Too many open files 11:23:56 imap-login: Error: socketpair() failed: Too many open files 11:23:56 imap-login: Error:
2017 Aug 23
2
socketpair failed: Too many open files on Debian 9
I haven't done this on the old, working machine. So there must be a difference between Debian 7 and 9 how open files are handled? Regards Patrick Aki Tuomi schrieb: > You probably need to increase ulimit -n > > Aki > > > On 23.08.2017 14:10, Patrick Westenberg wrote: >> Hi @all, >> >> after re-installing one of my two frontends/proxy-servers I get
2017 Oct 22
0
Proxy lmtps
https://wiki2.dovecot.org/PasswordDatabase/ExtraFields/Proxy says "NOTE: LMTP/doveadm proxying doesn't support SSL/TLS currently - any ssl/starttls extra field is ignored" Aki > On October 22, 2017 at 12:24 AM Matthias Kueth <listabo at die-b.org> wrote: > > > Hi, > > when proxying lmtp from director to backend, director does not use STARTTLS. >
2013 Nov 09
1
Dovecot replication not redirecting if server is down
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:
2013 Sep 09
1
Ring SYNC appears to have got lost, resending after upgrade
Hi @all, on Saturday I upgraded two dovecot servers from squeeze to wheezy and dovecot from 2.1.x to 2.2.5 (compiled from sources). After the upgrade everything worked fine at first. On Sunday Morning I recognized these errors (they occured after a reload for logging purpose on midnight) on one server: director: Error: Ring SYNC appears to have got lost, resending After reloading/restarting
2014 Jun 16
0
connection to director (lmtp) time out
Hi all, I'm running two directors with lmtp proxy as relay transport for my mail exchangers. relay_transport = lmtp:inet:dovecot-directors.example.net dovecot-directors.example.net resolves to 172.17.1.3 and 172.17.1.4 Now, .3 is down and Postfix tries to deliver it to .4 but this connection gets a timeout: (delivery temporarily suspended: connect to 172.17.1.4[172.17.1.4]:24: Connection
2012 Oct 21
2
No failover from director to backend?
Hi everyone, short version: Is there no built in failover mechanism for the director service to handle a backend failure? Long version: I have a frontend server running the director service and two backends. Due to maintenance I had to shut down one of the backends which caused connection errors for the users being directed to this backend. I was very surprised as I expected the director to
2014 Nov 17
2
LMTPS : TLS over LMTP not working
Hello, I tried to activate SSL on LMTP service, to secure connections between Postfix and Dovecot on my LAN, but Dovecot is not negociating a TLS session with Postfix. If I enforce TLS for LMTP at Postfix's side, communication between Postfix and Dovecot is not working. I put ssl = yes ssl_cert = </dovecot/ssl/ssl-LMTP.pem ssl_key = </dovecot/ssl/ssl-LMTP.key in section protocol
2012 Jun 05
1
dsync backup doubles quota
Hi everyone, I recognized a very strange behavior when doing backups of my mdbox mailboxes. After the backup the quota for each mailbox is twice as much as before the backup and I have to recalculate the quota to get the former/correct information. root at mb01:~# doveadm quota get -u test at example.com User quota STORAGE 5 10240 User quota MESSAGE 11 - root at mb01:~# doveadm backup
2014 Jan 22
1
dovecot produces messages dupes after nfs problems
Hi everyone, some days ago I had trouble with my NFS-Server (high delays) which caused dovecot lmtp to deliver the same message several times (up to 10x). I recognized some old/unused .nfsXXXX files in the maildirs which seemed to be index files. I deleted them and everything was fine again. However, there are still 2-3 mailboxen where mails (old and new ones) are delivered multiple times. All
2004 Jun 10
3
"virgin" mail accounts
Hello, I'm willing to swear that with the 0.99.10.4 Debian package in my rather extensive tests with mailbox format dovecot created not only any missing parental directories but also the INBOX file, but the later I can't prove/test now as I upgraded all respective boxes. However 0.99.10.5 will still create (if needed and possible) missing directories for mbox storage, just not an
2004 Jun 16
2
Return (revenge?) of the "pop-lock".
Hello, The users here have been migrated to the new mail system with dovecot 0.99.10.5 (Debian package) on the backends. Storage is maildir, only pop3 access for now. I see very seldom occurrences (compared to the session wide pop lock of qpopper on the old system) like this: --- Jun 16 14:35:52 mb01 pop3(user at gol.com): Timeout while waiting for release of exclusive fcntl() lock for index
2018 Feb 01
2
Upgrading a ctdb cluster: samba not listening on TCP port 445
Am Do 01.02.2018 um 12:04 schrieb Martin Schwenke: > Hi Nicolas, > > On Thu, 1 Feb 2018 10:57:59 +0100, Nicolas Zuber via samba > <samba at lists.samba.org> wrote: > >> I try to update two clustered samba file servers. Right now samba 4.7.0 >> with ctdb is running on both of them. To update samba I stopped ctdb on >> one of the servers, and compiled and