similar to: LMTP tcp listener with auth?

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 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

Op 12-9-2018 om 11:13 schreef Andreas Thienemann: > 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

Hi Sami, On Sun, 9 Sep 2018, Sami Ketola wrote: > Is it possible to get imapc rawlogs to analyze? create a directory that > is writeable and add -o imapc_rawlog_dir=/path/to/directory to command > line. Tried that. Thanks for the suggestion, that is actually really helpful. If anyone wants to play along at home, the files in that directory are created with the permissions of

Dear list, We are finally back to our task of migrating from cyrus to dovecot. dovecot mostly does what we want in terms of POP3/IMAP server. Now we are preparing for migration. The plan is to use dovecot as proxy for not-yet migrated accounts. This works wonderfully for IMAP but not for LMTP. Here's what I find in the logs when I try to deliver e-mail to the dovecot lmtp port: Jun 25

hi, we have IMAP and SMTP (sendmail(solaris)) on different hosts. Sendmail delivers Mails via LMTP to Cyrus and Cyrus puts the mails into the (hopefully) right box. Now I want to replace the Cyrus host with Dovecot. I've searched a bit in Google but there isn't much about LMTP via TCP in combination with DoveCot. Version 2 seems to be get the feature, but we have round about 5k users, so

Hello. First, I want to thank those responsible for Dovecot IMAP as it was a real treat to implement in comparison to my mostly-failed attempts with Cyrus. The passwd-file authentication was exactly what I needed as I really didn't want to have to deal with PAM or LDAP but where I am setting up a server with virtual accounts. I'm using Postfix as an MTA, and it quite handily passes

Hi all, I'm at the stage of planning our new mail system and am evaluating dovecot for it. For large mailstore setups, it makes sense to split maildirs across many directories. I see that setting default_mail_env to something like maildir:/var/imap/domain/%1d/%d/%1u/user/%u/ would create almost identical on-disk layout as multidomain cyrus setup. Now, as dovecot does not have its own

>But can you explain why you use globally: > >ssl_cert = </etc/ssl/dovecot.pem >ssl_key = </etc/ssl/private/dovecot.pem > >and certs for any additional Domain each? > >## >local_name mail.pettijohn-web.com { > ssl_cert = </etc/ssl/mail.pettijohn-web.com.crt > ssl_key = </etc/ssl/private/mail.pettijohn-web.com.key >} >## he configured the top

Hello everyone, I have set up postfix to deliver mails to dovecot (2.0.16) using LMTP. On the other hand, I've successfully configured the IMAP proxy setting in dovecot in order to be able to distribute mailboxes among different servers. I wanted to do the same proxy at LMTP level, but it's not working. If I put lmtp_proxy = no, then everything works ok (assuming the mailbox is local),

Hi Aki, I also tried with changing the original ldap source to svr2. Although everywhere svr2 is configured, still mails keep being delivered locally on svr1. Do I need to configure more than 20-lmtp.conf? [@svr1 conf.d]# cat 20-lmtp.conf | grep -v '^#' lmtp_proxy = yes protocol lmtp { # Space separated list of plugins to load (default is global mail_plugins). mail_plugins

Hi all, I start this on in a new thread. I setup the deny-user setting to temporarily prevent users from logging in and (that would be great) also stop mail delivery for said user. All this is because of our upcoming migration. Now it seems that lmtp is ignoring this setting. This is from the logfile: Aug 21 13:01:00 klee dovecot: lmtp(pid): Connect from IP Aug 21 13:01:00 klee dovecot:

Hello, has anyone a running setup for LMTP proxy and the director service ? pop3/imap/managesieve is properly working, but i have problems with LMTP. I set it up as described in the conf.d/10-director.conf From the user_db i get proxy=y and no proxyhost as described for imap/pop3 But lmtp is complaining about the missing host: Jul 07 15:00:48 auth: Debug: master in: PASS 1 user56

On Mon, Nov 02, 2020 at 09:33:08PM +0100, R. Diez wrote: > OK, so I gather that the Submission Server cannot do that (yet). And probably would never do. It isn't its job description. Actually, it is just a convenience/workaround feature, which comes handy only if your own MTA cannot handle dovecot's SASL authentication (must be something real strange) or there are some

Hi all, Reverted back to 2.2.34 and pigeonhole 0.4.22 and (after reverting config changes) it's working again including Sieve. I was notified of commit https://github.com/stephanbosch/dovecot-core/commit/6553f20bb31b5f0eebb73a0db526f00816b47d71 which I'll try. It's in a different option -f (not -d) but will try. Cheers, Bernard. 2018-04-08 20:10 GMT+02:00 Bernard Spil <brnrd at

When changing in a working setup sendmail.mc From this MAILER(smtp)dnl MAILER(procmail)dnl To this FEATURE(`local_lmtp',`[IPC]',`FILE /var/run/dovecot/lmtp')dnl MAILER(local)dnl I am getting these errors '501 5.6.0 Data format error' and ' Unrecognized host name'. What should I change in my lmtp config? Could this be related that messages are being relayed from

Hello We have migrated our email services from a server, which did not support IMAP and folders, therefore threated the plus sign + as a normal character in a part of an email address. Our new server delivers the emails via lmtp to dovecot. the few users which got a + character in the username first could not log-in (fixed by adding + to auth_username_chars). Now the next problem turn out to

Just having another look at http://wiki2.dovecot.org/MailServerOverview , it seems to have some statements in it which are misleading, and some which are really ... well ... wrong. Quote: "With the possible, optional, exception of the deliver MDA, Dovecot is not involved with reception, delivery, and storage of mail. That function is provided by a MTA such as postfix

I have spent a long time looking into this and can't find the answer I'm looking for, so I'm asking here. I'm cutting the example down to just the bare minimums. This is NOT my actual configuration, but is sufficient for asking this question: How can I use dovecot's deliver LDA to deliver to virtual users, but then have unknown virtual users fall back to catch-all

Hi, Ok, so I got rid of my procmail in favor of dovecot lmtp as my MDA. However, I lost the ability to tag the emails as SPAM or not. Before, this is done by procmail. Filtering is done by the Evolution client. Is there a way to do something similar now? I still want my filtering to be done by the Evolution. So I need something similar what procmail is doing i.e. altering the email header and