search for: ex_tempfail

...g: lda_mode = mode b) command line: deliver --mode mode where mode is default or sendmail. When no mode is specified, it defaults to "default", which is the current behaviour. In sendmail mode, mail_send_rejection() simply prints the rejection reason to stdout, logs it and returns EX_TEMPFAIL. Ideally, the return value would be specific to the reason. I haven't poked into this deeply, but it doesn't look straight forward. Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBRkHNQS9SORjhbDpvAQIhdggAq79RHKa1gIUTFwAu7Gd2maIUkDTgbNu6...

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: /usr/local/libexec/dovecot/deliver must not be both world-executable and setuid-root. Thi...

...nd.c (working copy) @@ -42,7 +42,7 @@ i_info("msgid=%s: Return-Path missing, rejection reason: %s", orig_msgid == NULL ? "" : str_sanitize(orig_msgid, 80), str_sanitize(reason, 512)); - - return 0; + return EX_TEMPFAIL; } smtp_client = smtp_client_open(return_addr, NULL, &f); Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBRkGA0S9SORjhbDpvAQIh0Qf/RUkmWnK+LhB3/ZwY+AnyTAYGBPB7qTCp bVchn4F7zL+W2fIYZGz6YG1bKUtHE3qMQAY3gYijspNZBejS0Z8cTI983ZMwJFP+ y...

...ded 2. Sender should get a proper response. Regards -Azher Apr 14 11:31:41 wm sm-mta[22712]: l3EFVKQY022711: to=<azher at wm.niit.edu.pk>, delay=00:00:00, xdelay=00:00:00, mailer=local, pri=130864, dsn=4.0.0, stat=Deferred: local mailer (/usr/dovecot/libexec/dovecot/deliver) exited with EX_TEMPFAIL -------- wm:/etc/mail# mailq MSP Queue status... /var/spool/mqueue-client is empty Total requests: 0 MTA Queue status... /var/spool/mqueue (1 request) -----Q-ID----- --Size-- -----Q-Time----- ------------Sender/Recipient----------- l3EFVKQY022711 99722 Sat Apr 14...

...ly well, UNLESS a user exceeds his/her quota: In that particular case, deliver fails to deliver the mail and generates a bounce, all on it's own. It's exit status is 0 in that case, so my MTA (postfix) thinks that the mail has been delivered successfully. I'd prefer deliver to return EX_TEMPFAIL, which I can pass through maildrop back to postfix, which will then log a temporary error and will bounce the mail all by itself after 5 days time. But how? -- Ralf Hildebrandt (Ralf.Hildebrandt at charite.de) plonk at charite.de Postfix - Einrichtung, Betrieb und Wartung Tel....

...= Oct 17 14:25:19 mx-mstr-07 sendmail[17289]: m9HBPJ99017288: to=<stsimb at t157.forthnet.gr>, ctladdr=<root at mx-mstr-07.forthnet.prv> (0/0), delay=00:00:00, xdelay=00:00:00, mailer=local, pri=30603, dsn=4.0.0, stat=Deferred: local mailer (/usr/libexec/dovecot/deliver) exited with EX_TEMPFAIL ==> /var/log/dovecot.log <== deliver(stsimb.t157.forthnet.gr): Oct 17 14:25:19 Info: Loading modules from directory: /usr/lib64/dovecot/lda deliver(stsimb.t157.forthnet.gr): Oct 17 14:25:19 Info: Module loaded: /usr/lib64/dovecot/lda/lib10_quota_plugin.so dovecot: Oct 17 14:25:19 Info: aut...

...d bounce the message. Note that the question may somehow be re-phrased as: when invoked without the -e option, under which circumstances will deliver send a rejection message? 3. Doesn't failure_exit_callback() in deliver.c tend to merge many (possibly dissimilar) errors into the single EX_TEMPFAIL one? And BTW, is that function guaranteed to be always called with an EX_* value? Seems to be the case, but... ;-) TIA for your patience, Axel

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

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

...uot;nscd" bug. But that bug is nevertheless out there, in the wild, on such systems, potentially affecting dovecot's delivery of valid user email. We have had a source code hack since October (in "deliver.c", simply replacing a "return ret" occurence with "return EX_TEMPFAIL") and it has worked nicely (ported forward from rc8 towards rc22). Mail re-queues and a later delivery attempt then succeeds. So it would be both helpful, and good for resilience against such real OS/nscd bugs (and similar), if there were a configuration option in dovecot to allow a site adm...

..., Apr 19 20:52:13 host1 sendmail[22311]: q3JHqDAR022309: to=<jamal at example.com>, ctladdr=<root at host1.bigmama.com> (0/0), delay=00:00:00, xdelay=00:00:00, mailer=dovecot, pri=120292, relay=dovecot, dsn=4.0.0, stat=Deferred: dovecot mailer (/usr/libexec/dovecot/deliver) exited with EX_TEMPFAIL Dovecot LDA can?t deliver the mail to the user!!!

...hough: 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 (/usr/libexec/dovecot/deliver) exited with EX_TEMPFAIL I've tried to `chmod +s /usr/libexec/dovecot/deliver`, which I read might fix some of those issues, but it didn't. Anyways, here are the important changes I made in my config files for using `deliver`: == sendmail.mc == ... dnl ## Should I modify this?? define(`PROCMAIL_MAILER_PATH',...

..., 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. (EX_TEMPFAIL) > > The mta keep the mail and retry delivery later, which is what I need. Ah, my mistake. But ... > I don't want to deliver email on dspam error, I prefer TEMPFAIL and > future retries, so I have a chance to fix the issue later without > loosing or deliver unprocessed mails...

...ot working and in the maillog, it shows: sendmail[31949]: sAEM4GTt031742: to=<user at localhost>, ctladdr=<test at localhost> (1000/1000), delay=00:08:31, xdelay=00:00:00, mailer=local, pri=210942, dsn=4.0.0, stat=Deferred: local mailer (/usr/libexec/dovecot/dovecot-lda) exited with EX_TEMPFAIL I verified that SELinux is not interfering in this case. I see talk of having sendmail run /usr/libexec/dovecot/dovecot-lda as other users, but I see that the file on my system is uid/gid as: root/root. Is there a way to get this working? Thanks much! -- Chris

...y 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): mysql(localhost): Connected to database system dovecot: imap-login: Login: user=<spam at xgm.de>, method=PLAIN, rip=::1, lip=::1, mpid=3535, secured, session=<jwXWP3HrwgAAAAAAAAAAAAAAAAAAAAAB> dovecot: imap(spam at xgm.de): Disconnected: Logge...

...r e.g. aliases.) + Maildir: uidlist file can now override message's GUID, making it possible for multiple messages in a mailbox to have the same GUID. This also fixes dsync's message conflict resolution. - dovecot-lda: If destination user isn't found, exit with EX_NOUSER, not EX_TEMPFAIL. - dsync: Fixed handling \Noselect mailboxes - Fixed an infinite loop introduced by v2.0.2's message parser changes. - Fixed a crash introduced by v2.0.2's istream-crlf changes.

...r e.g. aliases.) + Maildir: uidlist file can now override message's GUID, making it possible for multiple messages in a mailbox to have the same GUID. This also fixes dsync's message conflict resolution. - dovecot-lda: If destination user isn't found, exit with EX_NOUSER, not EX_TEMPFAIL. - dsync: Fixed handling \Noselect mailboxes - Fixed an infinite loop introduced by v2.0.2's message parser changes. - Fixed a crash introduced by v2.0.2's istream-crlf changes.

...However, when sendmail tries to use deliver I just get this message: Feb 13 15:37:23 gate sendmail[1399]: p1DEWtc2021995: to=<user at example.org>, delay=00:04:28, xdelay=00:00:00, mailer=local, pri=121665, dsn=4.0.0, stat=Deferred: local mailer (/usr/libexec/dovecot/deliver) exited with EX_TEMPFAIL I've tried to get better logging by putting the following in 15-lda.conf in /etc/dovecot/conf.d: protocol lda { postmaster_address = postmaster at example.org auth_socket_path = /var/run/dovecot/auth-master mail_plugins = sieve mail_location = maildir:~/.maildir log_path = /va...

...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. Hence, it is not necessary to have mail_send_rejection() to spawn another sendmail instance. The attached patch suggest to introduce an "operation_mode", in which Dovecot-LDA behaves differently for different environments. b) Some errors, like when spooling the messa...

...illog : Mar 19 15:17:28 hosting sendmail[3617]: m2J1EtMP003319: to=<root at localhost.localdomain>, ctladdr=<root at localhost.localdomain> (0/0), delay=06:02:32, xdelay=00:00:00, mailer=local, pri=665894, dsn=4.0.0, stat=Deferred: local mailer (/usr/libexec/dovecot/deliver) exited with EX_TEMPFAIL i am new in this. anyone can help??? appreciate ur reply....