similar to: deliver exit codes?

I'm testing deliver with sendmail and fs quotas. On an over quota condition, deliver accepts the mail, deletes it, then issues a MDN immediately. Is there a way to get deliver to soft fail like procmail does with a 400 error and queue the mail, then let sendmail handle the MDN, following it's "confTO_QUEUEWARN" and "confTO_QUEUERETURN" ? Thanks, Ken -- Ken

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, Dovecot v1.0.0 if there is no Return-Path in the message and Deliver cannot deliver the message, no DSN is sent _and_ the MTA is returned 0 (aka success) return code, which leads to mail loss. This is not the case, when the message actually finds a Return-Path, but fails to invoke the MTA. - --- src/deliver/mail-send.c (revision 47) +++

>From my log: Oct 6 00:10:36 postamt kernel: [2353838.557216] deliver[2799]: segfault at 48 ip b77dd649 sp bfcf3b48 error 6 in libdovecot-storage.so.0.0.0[b778e000+b8000] Oct 6 00:14:39 postamt kernel: [2354082.014722] deliver[6399]: segfault at 48 ip b7779649 sp bf9ca028 error 6 in libdovecot-storage.so.0.0.0[b772a000+b8000] Oct 6 00:28:12 postamt kernel: [2354894.551201] deliver[13972]:

Hello, I want to make final delivery for some of my mailboxes using dovecot-lda, since I'm interested in using sieve. My usual MDA which is called from postfix is and will be maildrop. First try was to call dovecot-lda from command line: /usr/lib/dovecot/dovecot-lda -d spam at xgm.de < testmail which gave return code 75 (EX_TEMPFAIL) and logged: dovecot: auth-worker(3533):

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I've put together an always tempfail & sendmail-like DSN report back patch. Because I don't know how to transform the rejection reason into sysexit.h codes, it always tempfails. The hooks are so that: a) config file setting: lda_mode = mode b) command line: deliver --mode mode where mode is default or sendmail. When no

Hi, I upgraded from Courier to dovecot, and now I try to rebuild some of the features I used to have. One was a monthly per user log of maildrop's work. I used this code in maildroprc: DATE=`date +%m` logfile "$MAILDIR/maildrop-$DATE.log" This created a monthly log in the each user's Maildir. I find it easier to have a log per user than having to filter the log entries

While investigating Dovecot's deliver with Postfix, I encountered some behaviors making me wonder whether I really understand the purpose of that binary. So, if you allow... This is from Postfix' main.cf: mailbox_command = /usr/local/dovecot/libexec/dovecot/deliver -e -n This is my quick setup for Dovecot: # 1.2.rc4: /usr/local/etc/dovecot.conf # OS: Darwin 9.7.0

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

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

Hello, I'm tinkering with Dovecot-LDA in order to achieve: + Better intergration into sendmail, and + tweaking its way to act on errors. Attached patch is a "brainstorming" like suggestion: a) when sendmail is dropping a message, it spawns the LDA, captures stderr/stdout and, if the LDA returns an exit code != 0, generates either a DSN or, when EX_TEMPFAIL, queues the mail.

Hi, I am using dovecot deliver as lda for sendmail. My problem is that when a user account is over quota, deliver program sends message in the logs, but the message is not bounced back to sender informing that their is disk quota problem at the recipient side. Further message remains in the mail queue. Details are below. Plz suggest how to figure out the problems: 1. Message should be

Hello-- I've noticed that with when using deliver, if there is a misconfiguration in my dovecot configuration file, a permissions problem on the maildir, etc., deliver will bounce the message. I'm using Postfix, and at some point used Maildrop, and I know that maildrop (and I believe also Postfix's virtual transport) instead defer the message if there is some kind of fixable

If pop3_lock_session = yes, how does Dovecot LDA handle the situation when the pop3 mbox is locked? Does it requeue mail for later delivery immediately (EX_TEMPFAIL), or wait until mbox_lock_timeout? Thanks, Ken A. Pacific.Net

SoI had a hell of a time converting my qmail install to dovecot 2.0.5, so I thought I'd pass on what I learned. 1. When using vpopmail, do not use " --disable-many-domains". If you do, you'll need to recompile vpopmail without that setting and use the script found at http://qmailrocks.thibs.com/downloads/scripts/migrate-vpopmail-many-domains to collapse the tables. 2.

Hi all. I've had a hard time trying to find out why deliver isn't working after I've updated dovecot from v1.11 to v1.2.8. It just gave me EX_TEMPFAIL without any info in the logs. My deliver was setuid-root. Once I've made a simple shell wrapper script for the deliver executable which saves deliver's stdout+stderr, I've found the reason:

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

How do I increase the journal size of a partition? -- Ralf Hildebrandt (Im Auftrag des Referat V A) Ralf.Hildebrandt@charite.de Charite Campus Virchow-Klinikum Tel. +49 (0)30-450 570-155 Referat V A - Kommunikationsnetze - Fax. +49 (0)30-450 570-916 The Imperial Vendor or Contractor probably told them that droid armies don't need redundant command centers, nor

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

On the whole we are pleased with our trials of dovecot to replace UW-IMAP. But (ah!) we have hit one particular problem, in which we think dovecot could probably benefit from a resilience improvement. We're running dovecot on Fedora Core 5 (FC5), with passwd map details supplied by NIS. We have found that "nscd" sometimes thinks that a username is invalid, even though it is valid.

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.