similar to: Adding a parameter to dovecot's deliver to get a meaningful return value

Hello everybody! I am a Linux admin trying to move my mail system based on qmail to the software which is more spam-protected: exim4 + dovecot-1.0rc15 + pgsql . I've downloaded and rebuild dovecot from src.rpm (for fc4). During the testing stage I've discovered two troubles: 1) the problem with deliver (...I'm not sure it's a really bug). Here is relevant part of my

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

deliver is the binary name. but it's configured inside protocol lda {} section. This is getting annoying, any thoughts on what would be a good unifying name? a) deliver binary, protocol deliver {} b) lda binary, protocol lda {} c) dovecot-lda binary, protocol lda {} d) mda binary, protocol mda {} e) dovecot-mda binary, protocol mda {} f) something else? In any case protocol lda {} would

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

Hello Dovecot users, Relatively many bugs and problems were reported recently in a short period of time. Apparently, now that Dovecot v1.2 is finally stable, the new Sieve plugin is also starting to get used much more. No known bugs remain. Let's hope I didn't spawn any new ones. Apart from the bugfixes I made the deprecated notify plugin implementation compatible with CMUSieve. You

Hello Dovecot users, Relatively many bugs and problems were reported recently in a short period of time. Apparently, now that Dovecot v1.2 is finally stable, the new Sieve plugin is also starting to get used much more. No known bugs remain. Let's hope I didn't spawn any new ones. Apart from the bugfixes I made the deprecated notify plugin implementation compatible with CMUSieve. You

Hi all... How can deliver messages to a subfolder using the LDA? For example, I want a message to joe+spam at abc.com to be placed inside the 'spam' subfolder. Any hint is appreciated. Thanks ;)

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

Hello, I am the new maintainer of dovecot for Fedora and Red Hat and so I am trying to cleanup some old reported bugs. One of them is a problem when "deliver" writes of temporary files into /tmp are blocked by SELinux policy (https://bugzilla.redhat.com/show_bug.cgi?id=424091). From the SELinux's point of view it is bad when system services try to write into /tmp (for detail see

Hi, is there a sieve option that can reject a mail directly without creating a new mail and sending that out? I know about reject "Reject message goes here"; but I am looking for a mechanism that can reject Mail. Postfix can use reject_unverified_recipient to connect to LMTP and ask if a mail would successfully be enqueued and will return the status gotten from the LMTP server if not.

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

Currently pigeonhole supports reject which would generate a NDR for each message. (If I understand the current documentation) Using Dovecot LMTP it would be more optimal to kick a 5xx back to the primary MTA to reject the delivery rather than generating more back scatter NDRs. Anyone know if this is possible now (to forgo the NDR)'s or do we need to wait for ereject ? If so, how much work

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 -

On Jan 13, 2015, at 8:30 PM, Reindl Harald <h.reindl at thelounge.net> wrote: > > so what you want in your OP is just DISCARD in a sieve script and there is no point in "Using Dovecot LMTP it would be more optimal to kick a 5xx back" when the desired result is DISCARD > > why do you want the burden of keep the SMTP session with the client open until the mail is

Hello, I'm using dovecot-1.0.5 with postfix. There is no document about how to using deliver parameters (-d). I can not set mail quota with mysql db if I haven't set this parameter. How can I describe user (-d) parameter to procmail. Procmail set, :0 | /usr/local/dovecot/libexec/dovecot/deliver -f blabla -d blabla regards,

Per the wiki page: http://wiki.dovecot.org/LDA Doing the following should create a Maildir directory structure in an arbitrary directory, deposit a message and create/update any dovecot indexes: mkdir /common/foo export HOME=/common/foo export PATH=/usr/libexec/dovecot:$PATH cat 1180102308.88215.4145.davidfavor.com:2,RS | deliver -f doda at foobar.com This gives an error

dear all, quickie - is possible(if yes - how, params, directives, etc) to use any alternative to sendmail_path = /usr/lib/sendmail is is configurable at all? like having postfix or anything else? regards

Hi, I'm trying to execute a script when a mail arrives in a given user's mailbox. Something like .dovecot.sieve. The reason I'm not using sieve itself is that I need to do stuff on mail arrival, which is beyond sieve's features. So is there a way to tell dovecot to run a script when a mail arrives in a certain mailbox? Optionally a solution to forward the whole mail to a

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I have a small Sieve script that tries to use vacation that segfaults. The script is the one from http://wiki.dovecot.org/LDA/Sieve. When I change the email address (I changed the local part into "skai"), hence, vacation is skipped, the mail is delivered without any problem. ==== script start require ["fileinto",

Hi all I'm considering moving over my POP3 service from qmail-pop3d to Dovecot for the following reasons: - Support for Maildir++ which I have yet to implement - Already using Dovecot for IMAP, so makes sense i.t.o Maildir++ - Support for SQL based user authentication My primary concerns are performance and security. Before I go down that route of migrating away from qmail-pop3d, I'd