similar to: deliver vs lda

Hi, Since updating to 2.3.1 on my FreeBSD mailserver mail delivery using lda is broken if I have sieve enabled. (Before updating this was 2.2 and pigeonhole 0.4) FreeBSD 11.1-p8 amd64 Dovecot 2.3.1 Pigeonhole 0.5.1 Mailflow is OpenSMTPd as MTA, using mda delivery to rspamc which utlimately delivers using dovecot-lda. smtpd.conf deliver to mda "rspamc -h scan --mime -e

On RHEL5, dovecot 1.0.7, I have set up sendmail to use `deliver` for my local mda. It keeps giving me this error for the root user though: Jul 12 12:51:29 mail sendmail[4105]: o699225f001348: to=<root at localhost.localdomain>, ctladdr=<root at localhost.localdomain> (0/0), delay=3+08:49:26, xdelay=00:00:00, mailer=local, pri=7502879, dsn=4.0.0, stat=Deferred: local mailer

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

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 all. I've got a bit of a peculiar issue here. I'm running dovecot 1.2.9 on an Ubuntu 9.10 box using Sendmail 8.14.3. I've set up Sendmail similar to <http://wiki.dovecot.org/LDA/Sendmail> except that *) dovecot's deliver is configured as my default local mailer, so some of the flags for the Mailer definition had to be adjusted accordingly. *) The setuid users

On Fri Apr 02 00:37:03 +0200 2010, Trevor Harmon wrote: > On Mar 31, 2010, at 3:13 PM, Owen Anderson wrote: > > Others, like MemoryDependenceAnalysis, are "lazy." MDA > > specifically does NOT compute results in its runOnFunction(), > > instead computing results on-demand when a user queries it. Because > > MDA depends on AA, we must ensure that, as long as

Hi Stephan, Shared the message to you in person only via separate mail. With to Return-Path, I've not seen any difference in failures, all messages were consistently failing with the same error. Thank you! Bernard. 2018-04-10 2:54 GMT+02:00 Stephan Bosch <stephan at rename-it.nl>: > Op 4/8/2018 om 8:10 PM schreef Bernard Spil: >> Hi, >> >> Since updating to 2.3.1

Hi, First, please forgive me as I'm not subscribed to the list. I'm using Dovecot 2 (2.1.7) for serving my local maildir. This maildir is filled by an external process, fetching & merging mails from different sources that's outside this scope (but it's working). Dovecot is thus acting as a MTA, but more as a MDA. I've a web client running on the server, and it connects

hmm if message cannot be written to disk surely it remains on mda queue as not delviered and does not just disappear ? or am i reading this wrong ?! > Dag Nygren <mailto:dag at newtech.fi> > 16 August 2017 at 7:14 am > Thanks for all the advice on how to configure systemd > not to loose my emails after every update. Much appreciated. > > But there could be other reasons

Would it be sensible/"cost effective" to make dovecot-deliver generated X-Delivered-To header(s) based on command line parameter(s)? [after striping such existing headers, before consulting sieve] I need it to: a) *clearly* mark POP/IMAP account fetched by fetchmail [with fetchmail using directly dovecot-deliver in --mda option] b) cleanly implement "shared mailboxes" with

On Mar 31, 2010, at 3:13 PM, Owen Anderson wrote: > Some analyses, like Andersen's AA, do all their computation in their > runOnFunction(). Therefore, anything they depended on can be > destroyed after the runOnFunction() returns. What about AA itself? Would addRequired<AliasAnalysis> keep AliasAnalysis alive (but allow AliasAnalysis's dependencies to die)? >

Hi, i still try to sieve system. ok first our deliver command procmail. our user accounts stored in openldap, mail files are in Maildir folders in 15-lda.conf recommented protocol lda { # Space separated list of plugins to load (default is global mail_plugins). mail_plugins = $mail_plugins sieve log_path = info_log_path = } after that, in master.cf i added dovecot unix -

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

Hi there, I'm using Dovecot 2.0.9-1 under Arch Linux. Currently, I have Maildir configured, and I move all my emails into dovecot by using this sequence: 1) cron starts fetchmail periodically under user manfred to collect my mails from various email accounts. 2) In ~/.fetchmailrc I have configured /usr/bin/maildrop as MDA. 3) In ~/.mailfilter (used by maildrop) I have extensive filtering in

Hello, I currently have one machine running postfix SMTP server as MTA along with dovecot IMAP server for email. Although it only supports a handful of users, email service is important to us all; so I'm looking to make this a more fault-tolerant / highly-available system. To that end, I'm planning on configuring postfix to use deliver/dovecot-lda as my MDA (using procmail at the

Hello, guys, I'm going to using sieve and quota plugins, but I'm not sure where shall I enforce against properly? I see somebody uses them against 20-imap.conf, 15-lda.conf, or 20-lmtp.conf I use LMTP as MDA, so where is the correct location to call these plugins and why? Thanks, -------------- next part -------------- An HTML attachment was scrubbed... URL:

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

On Mar 31, 2010, at 2:53 PM, Trevor Harmon wrote: > I'm a bit confused about the distinction between addRequired and > addRequiredTransitive in AnalysisUsage. From PassAnalysisSupport.h: > > "REQUIRES (must be available when the pass runs), REQUIRES TRANSITIVE > (must be available throughout the lifetime of the pass)." > > The part that's confusing me

Hi, I have an OpenSMTPD / Dovecot installation on an OpenBSD server. I recently came across an issue where Dovecot LMTP would reject a message sent to a local user from an address which contains a single apostrophe (e.g. firstname.o'lastname at example.com). Apparently apostrophe, as well as a number of other special characters, are valid characters in the local part of the email address

Our asterisk server has been up and running for over a year and it works great. I have emails going to my account as an attachment and I can listen to them on the desktop and it works fine. I just got a T-Mobile MDA that runs Windows Pocket (or whatever they call it) and it can check email. If I have it download the email, it gets the attachment, but it can't seem to play it (it CAN