similar to: lmtp + tcpwrap

Hello, I just installed dovecot2-beta2 and configured the lmtp-server + postfix (no virtual users) postfix: mail_version = 2.7-20100117 mailbox_transport = lmtp:unix:lmtp-server lmtp_assume_final = yes dovecot: service lmtp { executable = lmtp protocol = lmtp unix_listener /var/spool/postfix/lmtp-server { group = postfix mode = 0660 user = postfix } } Mail gets delivered to

Hello list, I use currently a non-dovecot pop3 proxy which has the ability to scan all passing mails for viruses. And I like dovecot. I have to combine both. One (and the only) idea is to call a virusscanner a shellscript, installed as PostLoginScript. But I see multiple disadvantages: 1. it's a shellscript which tents to be slow. 2. it's called *on* the mailbox-host, not on a dedicated

Hi Timo, today I've started Dovecot v2.2.rc2 (976bf9e69367) for the first time. /var/log/mail.log: Mar 3 14:28:33 mail dovecot: master: Dovecot v2.2.rc2 (976bf9e69367) starting up Mar 3 14:28:38 mail dovecot: master: Error: service(tcpwrap): command startup failed, throttling for 2 secs Mar 3 14:28:38 mail dovecot: tcpwrap: Fatal: master: service(tcpwrap): child $PID killed with signal

Hello, recently I inspected the sourcecode of the lmtp server. I searched for changes that would add return-path header. ( http://www.dovecot.org/list/dovecot/2010-February/046401.html ) But I found, that all mails are spooled via files in /tmp. ( dovecot2/srv/lmtp/commands.c ~line 695 ) has somebody experiences while delivering huge ammount of mail via dovecot2 lmtp service? - is it

Hello, we want to use dovecot LMTP for efficient mail delivery from our MX servers (running postfix 2.8) to our storage servers (dovecot 2.0.17). However, the one problem we see is the lack of access control when using LMTP. It apears that every client in our network who has access to the storage machines can drop a message in a Maildir of any user on that storage server. To prevent this

Hello, I have a system using postfix multi instance feature. The first, main postfix-instance is a nullclient as suggested by http://www.postfix.org/MULTI_INSTANCE_README.html#split The second instance is for real use. Postfix receive mail and handover them to the dovecot lmtp server. Thats working. The lmtp server supports sieve. One account has activated a vacation rule. So while delivering

Hello, after upgrading to 2.2.22 the lmtp service is crashing (segfault) a few times per hours. >From the logs: Mar 19 16:37:29 lmtp(redacted at ruhr-uni-bochum.de): Info: ohZXLe1x7VaUeQAAEc+Mrg: sieve: msgid=<redacted at async.facebook.com>: discarding vacation response to mailinglist recipient <redacted at facebookmail.com> Mar 19 16:37:29 lmtp(31124): Info: Disconnect from

Hi Stephan, On Wed, 12 Sep 2018, Stephan Bosch wrote: > LMTP currently does not support AUTH. Bummer. Thought so. > What is your use case? Most people hide LMTP behind a firewall, or don't > expose it through TCP/IP in the first place. The port is currently only available to a few trusted machines, but having auth available would have been a nice benefit in case the firewall

I've had 18 instances of this error the last 24 hours: Sep 8 08:56:00 popimap1 dovecot:: lmtp(10529, first.last at example.om): mGdAOtdlaE4hKQAAg/aw4w: msgid=<B8FA3D5B230184409450D51D522678404E5052 at ASP-EX02.ASP.lan>: save failed to INBOX: BUG: Unknown internal error 17 on lmtp-server A, and one on lmtp-server B. On server A it was a message with 55 recepients, where 17 failed

Hallo, I am playing arround with dovecot I hat version 1.0.beta7 running fine. After installing beta9 there is a problem with default_mail_env setting. I have all users in ldap. there is an attribute "mailMessageStore" which contains a relative path to users maildir mailMessageStore: sca/ my mailer completes this relative pathinformation to /var/mail/sca/ therefor I setup

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

Steffen Kaiser: > Is the detail delived to Dovecot by the MTA at all? sure! have to say: I faked that example. In reality I tested the inverse way: My lab setup actually *do* deliver to folders and I saw, setting lmtp_save_to_detail_mailbox to 'no' still deliver to folder while INBOX was expected. so, correct hint: I should really try on an other system ... But from my debug logs it

Hello, I'm providing IMAP+Starttls on port 143 for users with legacy MUA. So I've to enable TLS1.0 up to TLS1.3 For IMAPS / port 993 I like to enable TLS1.2 and TLS1.3 only. Is this possible with dovecot-2.2.36 / how to setup this? Thanks for suggestions, Andreas

Hello, is it possible to use differnent ssl certs for pop3 and imap ? I like to have differnet dnsnames for pop3 an imap services configured at customers clients. I tried to configure ssl_key and ssl_cert inside a <protocol>-login {} section but this failed. Of course I know sslcerts containing multiple dnsnames. But this seemes not a real, clean solution to me. Thanks, Andreas --

hello, dovecot2 implements "!include conf.d/*.conf" to build the configuration from multiple configfiles. So the settings for pop3, imap or lmtp may stay in different files. unfortunately the "protocol = " does not allow a += logic to enables or disable inet listeners. It would be nice to have protocols += imap in conf.d/imap.conf and protocols += managesieve in

I'm upgrading my configuration to use director and lmtp for delivery. (doveconf -n at end of the mail). I use the same config for auth on mail backends and see no errors. My setup seem to work nicely but i have some auth process crashing when using lmtp protocol. Everything is working a sexpected then i've got 5-6 errors like this in logs and a crach of the auth process: dovecot:

Hello! Since experiments on my testserver two days ago /var/spool/postfix/private/dovecot-lmtp is not created anymore. This the setting in /etc/dovecot/conf.d/10-master.conf service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } I searched nearly the whole system for lmtp but can't find the reason why. What can

<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> <br> </div> <blockquote type="cite"> <div> On 14 November 2018 at 21:19 "A. Schulze" < <a href="mailto:sca@andreasschulze.de">sca@andreasschulze.de</a>> wrote: </div>

I am wondering if it's possible to have a tcp listener for LMTP do authentication and not accept any unauthenticated mail. My configuration looks like the following: service lmtp { inet_listener lmtp { address = 192.168.0.1 127.0.0.1 port = 24 } } This gives me a network reachable lmtp socket, but of course no autentication. When reading the docs, it seems though that only

Hello ? I have the dmesg loaded with lmtp crash messages. My OS: ? No LSB modules are available. Distributor ID:?? ?Debian Description:?? ?Debian GNU/Linux 7.4 (wheezy) Release:?? ?7.4 Codename:?? ?wheezy ? My postfix version: ? i? postfix??????????????????????????? 2.9.6-2?????????????????????? amd64??????? High-performance mail transport agent ii? postfix-doc???????????????????????