similar to: SUMMARY: LDA vs LMTP, Cyrus SASL, verbose_proctitle

Is there a reason I should prefer LMTP over LDA for local delivery? Performance? Security? The Wiki doesn't differentiates LMTP vs LDA with respect to sendmail configuration, so am I correct that I just need to replace mail.local with dovecot-lda, which will choose LDA/LMTP based on dovecot.conf? Also, can I consolidate authentication by configuring dovecot to use what sendmail uses (Cyrus

Hi, I have a Centos 5 system with sendmail running as my MTA. Normally I note from sendmail logs that mails get delivered using the 'local' mailer. I have therefore entered the following into my sendmail.mc file, from an earlier post on this list: define(`LOCAL_MAILER_PATH',`/usr/libexec/dovecot/deliver') define(`LOCAL_MAILER_FLAGS',`DFMPhfnu9')

I am stuck. I get nothing in the logs (about deliver). Sendmail complains about "User unknown". I am not sure I have my sendmail.mc configured right, can someone confirm or give me some sample config files that make use of Dovecot+LDAP and sendmail LDA? Dovecot is running as root. I am a little confused, so the auth-master is not even needed? (the whole socket listen {}, since I am

Hi, Im configuring sendmail with dovecot for virtual users using password file and file for user name. on centos. dovecot-1.0.7-7.el5 sendmail-8.13.8-2.el5 dovecot ?n # 1.0.7: /etc/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot.log ssl_disable: yes login_dir: /var/run/dovecot/login login_executable(default):

St?phane Cottin writes: >> You're stilling going to lose contents. If dspam fails, the mail >> is dumped, the LDA returns exit code 75, and the MTA will probably >> issue a bounce Email to the sender. > > from dovecot-lda man page : > > 75 A temporary failure. This is returned for almost all failures. See the log file for > details.

I don't really need logging of successful local deliveries since the MTA provides enough data. I can't get rid of LDA delivery logs by setting deliver_log_format = All this does is produce an empty log message e.g. Apr 16 01:22:05 dserver dovecot: lda(user): Timo, would you consider inclusion of this patch which will skip logging deliveries if deliver_log_format is empty: ---

St?phane Cottin writes: > dspam already send errors to syslog, the point here is to never loose > email contents. This was a wrong design, i'm now use a wrapper instead > ( see my previous post for details ). You're stilling going to lose contents. If dspam fails, the mail is dumped, the LDA returns exit code 75, and the MTA will probably issue a bounce Email to the sender.

Hi there, I'm using Dovecot together with Postfix; as I understand it, there are two ways to transfer the mail from Postfix to Dovecot. 1.) by using LDA with mailbox_command = /usr/libexec/dovecot/dovecot-lda -f "$SENDER" -a "$RECIPIENT" 2.) by using LMTP with mailbox_transport = lmtp:unix:private/dovecot-lmtp (currently using number 1) I'm interessted in the

We uograded our dovecot from version 2.1.10 -> 2.10.12, but within the first hour of use, dovecot-lda would segfault during delivery. This left a lock file lying around causing the user's mail readers to hang; much hilarity ensues. All further deliveries to the same user will result in a crash. The only thing that fixes this condition is to blow away the user's INBOX cache index.

Hi to all, my question is what is benefit implementing LMTP service replacing LDA i have dovecot 2.1.8 with vpoipmail+qmail and about 500 users now i'm using LDA and i'm interested on LMTP service. Thanks in advance -- */Davide Marchi /Teorema Ferrara Srl /(Tel: /**/+39 0532 783161)/**/ (Fax: +/**/39 0532 783368/**/)/**//**/ /**//**/Davide.Marchi at mail.cgilfe.it

Robert Schetterer <robert at schetterer.org> writes: >> Anyway, why use lmtp over lda ? > > i.e avoid backscatter by overquota A clarification on this: backscatter (or rather, ambiguous NDR notices that claim many users are over quota rather than just one) is a result of a local mailer that support multiple recipient delivery in one invocation, but can only return one result

Please forgive me if these are silly questions. I am a normal user, not a system administrator. I am using Dovecot as a kind of IMAP caching proxy, i.e. reading IMAP mail via Gnus + Dovecot + Offlineimap. I am trying to enable sieve functionality. *Desired behaviour* When Gnus (or whatever MUA) asks for new mail from Dovecot, that before Dovecot returns and answer, the sieve rules are

St?phane Cottin writes: > A typical .qmail file : > > | /usr/bin/dspam --client --deliver=stdout --user "$EXT@$USER" | /usr/bin/preline -f /usr/lib/dovecot/dovecot-lda -d "$EXT@$USER" -a "$EXT@$USER" -m "$EXT2" > > When dspam segfault or is killed, preline receive an empty content and > only pass to dovecot-lda two headers ( Return-Path

Hi all, I have setup dovecot 1.1.4 and sendmail 8.14.3 with dovecot LDA on linux (RHEL5 on x86_64). I have deliberately set a very low quota (4MB) on a test account, while the actual disk usage is 5MB at the moment, in order to test overquota behaviour.. When I send an email to this account, sendmail accepts the email and tries to deliver it. Deliver fails to save in INBOX and returns an

Hi Timo, little cosmetic bug report: using "verbose_proctitle = yes" shortens the proctitle of dsync to just "dsyn". Example: Note the whitespace instead of the 'c' in the proctitle: root at m-st-01:~# ps auwwwx | grep [d]syn virtmail 18141 13.0 0.1 49916 7952 pts/6 R+ 00:49 0:00 dsyn -v -u xxyyzz7 -R backup maildir:/staging/xxyyzz7/Maildir With

Happy Xmas, when using a post-login procedure the "verbose_proctitle = yes" has no effect. If it is feature then please explain else please fix the bug fi --Frank Elsner

> On Jul 10, 2018, at 7:19 PM, J Doe <general at nativemethods.com> wrote: > > Hello, > > I have a question relating to the detail that the verbose_proctitle parameter enables for ps. > > I have TLS configured for IMAP as follows: > > /etc/dovecot/dovecot.conf > ssl = required > ssl_cert = </path/to/cert.pem> > ssl_key =

Hi, We're using Dovecot to proxy incoming POP3 and IMAP connections to the right server. We'd like to be able to see what connections are currently open on the proxy servers, without having the parse the log file. For normal mail processes it's possible to use verbose_proctitle for this purpose, but this setting doesn't work for proxy/login processes. Is it possible to do

How is verbose_proctitle supposed to work? I set it in the config but I don't see anything particularly verbose while the mailbox is connected. This is while the connection is open, immediately after deleting a message, before closing the connection. Same for IMAP and POP tests. # `ps axu | grep dove` # root 20392 0.0 0.0 1888 540 ? Ss 12:45 0:00 /usr/sbin/dovecot #

On 07/13/2018 08:45 AM, J Doe wrote: > I?m aware that this is because the code does not state to specify ?TLS? for the dovecot/imap [user at example.com 1.2.3.4 IDLE] line of output, but I?m curious as to why that decision was made ? TLS is done by the imap-login process. This process does all the actual talking to the client. The imap process blindly trusts whoever invoked it (imap-login), it