similar to: lmtp proxy logging

Hi All, is there any way to enable logging of users' IP address in dovecot director host? It actually logs only: Sep 14 07:32:29 mailgw-lb dovecot: lmtp(17615): Connect from xx.xx.xx.xx Sep 14 07:32:29 mailgw-lb dovecot: lmtp(17615): Disconnect from xx.xx.xx.xx: Client quit Thanks Luca

Hi, I have a timeout problem only when I have heavy load in my system. I have two director servers directing to 4 backend servers. The problem is when my smtp relays tries to deliver mail to my users via lmtp (proxied with director). In the smtp logs I have: Jun 12 11:41:18 xenon13 postfix/lmtp[4248]: 4433E5D5A0: to=<myuser at um.es>, relay=pop.um.es[155.54.212.106]:24, delay=31,

Hi. I'm using exim that delivers email over LMTP to dovecot 2.2.13. I noticed that dovecot LMTP service is sometimes (reare but repeats) mixing users. Example below. There is one mail (msgid=<1ACE53B70631CA45B62348E4EE8757493731A59E at KRMXA41>) that is going to be delivered to multiple local recipients. Some recipients are delivered properly: Sep 1 05:40:33 host dovecot:

Hello, I am having a problem with the lmtp delivery of mail addressed to multiple recipients. ?The first recipient receives the mail correctly but the next recipients do not. ?ltmp apparently tries to create a link from the subsequent recipients' mail store to the first recipient mail store and fails. This returns 451 smtp codes to the sender which then resends at some later time. Please see

Looks like I have a correct working proxy on pop3. On both backend servers I can run cat /tmp/test.msg | /usr/libexec/dovecot/lmtp Giving 250 2.1.5 OK 354 OK Info: Disconnect from local: Connection closed (in DATA) However if I run the same command on the proxy, I am getting this error 'Invalid FROM: Missing domain'. How is this FROM even relevant if message just needs to be

Hello, I encountered a problem when trying to send an email to multiple recipients. === LOG === ... cut ... Jul 3 12:34:57 dhcp90 dovecot: lmtp(24106): Debug: none: root=, index=, control=, inbox= Jul 3 12:34:57 dhcp90 dovecot: lmtp(24106): Connect from local Jul 3 12:34:57 dhcp90 dovecot: lmtp(24106): Debug: Loading modules from directory: /usr/lib64/dovecot Jul 3 12:34:57 dhcp90

Hi, I am not yet completely happy with the logging behavior of the lmtp. It logs informative messages like 'lmtp: Info: Connection closed' or 'lmtp: Info: Disconnected for inactivity'. Hm, which server was connected to the lmtp? Who was disconnected for inactivity? I think it would be useful if the lmtp would also log new connections. For example: a) TCP connections: lmtp: Info:

Hi, After updating some of our director servers from 2.2.36 to 2.3.3 (dcead646b) we experience crashes in about 1/5000 mails in lmtp delivery: Nov 13 12:23:36 Fatal: lmtp(113620): master: service(lmtp): child 113620 killed with signal 6 (core dumped) Nov 13 12:23:36 Panic: lmtp(113623): file ostream-dot.c: line 208 (o_stream_dot_sendv): assertion failed: ((size_t)ret == sent + added) Nov 13

Dovecot version: 2.1.3 lmtp config: protocol lmtp { mail_plugins = zlib acl sieve } Running strace on lmtp reveals that when lmtp delivers a message to multiple recipients it saves the message to a file in the first mailbox and hard links that file to other mailboxes. But when in the meantime of delivery that file is deleted, lmtp fails to deliver the message to remaining mailboxes. For

Hello, i am trying to proxy a LMTP connection with version 2.0b3 Currently i have the problem when trying to use a named based proxy for LMTP the process doesn't resolve the hostname and crashes: Feb 26 16:53:26 auth: Debug: ldap(vodafonemail56 at vodafone.de,::1): pass search: base=ou=mailboxes,ou=vfag,c=de,o=vodafone scope=subtree filter=(&(objectClass=uco)(mail=vodafonemail56 at

Hello, when trying to set up a migration scenario from my old mailbox-servers to my new dovecot-cluster, I get a coredump from dovecot/lmtp when proxying mail-delivery to more than one recipient on the old mailbox-server. My setup: 3 director-hosts (Debian stretch) are proxying to a pair of replicator-hosts and during migration also to the old mailbox-server. For migration the not-migrated

I just tried switching to lmtp from lda. Messages are being delivered, but I now see messages similar to: Jul 26 22:59:21 bubba dovecot: lmtp(20508): Disconnect from local: Client quit (in reset) in my log for every message. Is this a normal sign-off - or does this indicate a misconfiguration? -- Daniel

How exactly is LMTP proxying supposed to work? According to the example on http://wiki2.dovecot.org/PasswordDatabase/ExtraFields/Proxy I'm only seeing "proxy" in the password_query statements. But LMTP never sends a password. IMAP Proxying is working OK: Sep 24 12:51:09 imap-login: Info: proxy(ralf.hildebrandt at charite.de): started proxying to dovecot.charite.de:993:

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

Hi, I have dovecot running for IMAP4/POP3 and also local delivery through LMTP. It's working just fine, absolutely no problem on that, setup is fine. Anyway, sometimes LMTP seems to not be able to deliver some messages and keep them on postfixqueue. And on the next or third try, the message gets delivered successfully. The logged message, however, is not helping me identify

Hey I got a server setup where the Postfix and dovecot is on separated servers. In the postfis log is goes like this on mail in: Jul 26 10:23:13 edimailsl2 postfix/smtpd[12812]: 41blTs18Bzz40nl: client=unknown[172.0.0.12] Jul 26 10:23:21 edimailsl2 postfix/cleanup[12825]: 41blTs18Bzz40nl: message-id=<> Jul 26 10:23:21 edimailsl2 postfix/qmgr[10666]: 41blTs18Bzz40nl: from=<tk at

Hi again, I've not heard anything further regarding this bug, so I've had a look at the code. To restate the bug in a more precise way: LMTP in dovecot treats external RFC822 email addresses in the envelope recipient and internal usernames as almost identical/interchangeable. This is incorrect and leads to issues when attempting to use director as an LMTP proxy to proxy to recipients

During the early Dovecot LDA brainstorming discussions, there was some talk about the possibility of including an LMTP interface, and I've noticed that there's an "is it needed?" question about LMTP in Dovecot's TODO file. I'd like to put in a vote for LMTP, and I'm wondering if anyone else has a need for it. Specifically, I'd love an LMTP-enabled LDA that uses

Hi Aki, you have some ingenious remark that could help? -----Original Message----- To: aki.tuomi; dovecot Subject: RE: Local lmtp proxy on backend server I am staring constantly at the same logs, this is what I get from dovecot[1]. Sendmail[2] is sending with test at svr1 maybe this overrides lmtp proxying? This is a test with a special-userdb passwd-file also having host=svr2 [1] Dec

Sorry for offtopic, don't know where to ask it after updating from `ubuntu` 18 to 20 started getting this on running golang binary from sieve rules file ``` Sep 17 08:54:00 lonjemail spamd[3231]: spamd: connection from ::1 [::1]:57844 to port 783, fd 5 Sep 17 08:54:00 lonjemail spamd[3231]: spamd: setuid to Debian-exim succeeded Sep 17 08:54:00 lonjemail spamd[3231]: spamd: processing message