similar to: deliver w/quotas - MDN after accept mail?

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

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

It appears that there is some version of the Dovecot LDA that is sending an RFC 3798 MDN rather than an RFC 3464 DSN to report non-delivery to a user who is over quota. See <https://bugs.launchpad.net/mailman/+bug/693134> for a discussion of this and <https://bugs.launchpad.net/mailman/+bug/693134/+attachment/1773018/+files/Automatically%20rejected%20mail.msg> for the actual MDN

I'm using dovecot-1.2-sieve-0.1.15 with dovecot-1.2.11. I have a reject test filter that looks like this: require "reject"; if header :contains "subject" "reject" { reject "bye"; } Is there any way to get a "reject" filter to send back a 550 reject as detailed in http://ietfreport.isoc.org/idref/rfc5429/#section-2.5 rather than a MDN? The

Before switching to dovecot deliver for all local deliveries, I'm calling deliver from maildrop (yes, don't laugh). Snippet from my global /etc/maildroprc: # Store maillist & junk messages directly /^Precedence: ?list/ if ( $MATCH ) { exception { log "Bulk message: $MATCH" #to "$DEFAULT" to "|$DELIVER" } } I replaced to

Hello, I can get the median for each factor, but I'd like another column to go with each factor. The nm column is a long name for the lvls column. So unique work except for the order can get messed up. Example: x =

2. update ZFS in libfsimage from illumos for pygrub diff -r 7c12aaa128e3 -r c2e11847cac0 tools/libfsimage/Rules.mk --- a/tools/libfsimage/Rules.mk Thu Oct 24 22:46:20 2013 +0100 +++ b/tools/libfsimage/Rules.mk Sat Oct 26 20:03:06 2013 +0400 @@ -2,11 +2,19 @@ include $(XEN_ROOT)/tools/Rules.mk CFLAGS += -Wno-unknown-pragmas -I$(XEN_ROOT)/tools/libfsimage/common/

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

I think someone else mentioned this problem earlier on the list, and I've recently started seeing the following error show up: file index-transaction.c: line 54 (index_transaction_finish_rollback): assertion failed: (t->mail_ref_count == 0) Raw backtrace: /usr/lib/dovecot/deliver(i_syslog_fatal_handler+0x2b) [0x80bff0b] -> /usr/lib/dovecot/deliver [0x80bfd1a] ->

Hi, while testing out dovecot 1.1, I found that when you set quota_full_tempfail = yes in dovecot.conf and use the deliver -e command line flag, no deferral reason is printed, thus breaking my fancy quota_exceeded_message. This appears to be because of the if() block in lines 1003-1009 in src/deliver/deliver.c, and should be easily fixable (if it is indeed a bug, and not intended behavior).

Currently the typical rejection message is: --------- Your message was automatically rejected by Dovecot Mail Delivery Agent. The following reason was given: Quota exceeded. --------- Then there is MDN + message headers in other MIME parts. But of course there sucky clients that can't display MDNs and users get confused. Any suggestions how to improve this message? I'm not sure if the

Hi all, I have Dovecot 1.2.13 installed. My clients ask why Disposition-Notification is requested every time the mail is moved on a new IMAP folder... I take a look into dovecot-keywords file and I see that: 1) I have only one row 0 NonJunk 2) dovecot-keywords file is not present inside every directory. How I can restore normal status? Where is probably the problem? Thanks Mauro D.

Hello everyone, I'm doing a standard build on Solaris 10 with Dovecot 2.2.15 without anything fancy: ./configure make make check make install Configure output looks like this: *** Install prefix . : /usr/local File offsets ... : 64bit I/O polling .... : poll I/O notifys .... : none SSL ............ : yes (OpenSSL) GSSAPI ......... : no passdbs ........ : static passwd passwd-file shadow

Hi, after having moved a big mail archive to IMAP, I've now got the following problem: The MUA asks to send an MDN on all those old messages that contain the 'Disposition-Notification-To' header when opened. I'd like to set the $MDNSent flag on those (>10000 in a deeply nested directory structure) mails. After having read http://wiki.dovecot.org/MailboxFormat/Maildir I wrote a

This was actually the first thing that ChatGPT debugged for me. The issue was that I was able to click on the link when I displayed the raw SVG in the browser (you can use that to test whether the syntax is even correct), but not when the svg displays inside a html page with the <img ...> tag. ChatGPT correctly identified the issue and suggested a solution using <object ...> tags

Hi, a few days ago, we switched our site from pop3 to imap. We are running about 20 users with Netscape 7.0 on a FreeBSD-4.8 Server . I installed dovecot 0.9.99.1 via the freebsd-ports collection, which was as easy as make install and start dovecot. Our users mailboxes are still standart mbox format in /var/mail/(user), as it is default in Freebsd. Now we suffer from a realy ugly problem,

http://dovecot.org/tmp/dovecot-1.0.1rc3.tar.gz Looks like I managed to do a lot of changes today. So I'll wait a few more days before v1.0.1 release. The important changes since rc2: + deliver: Added -e parameter to write rejection error to stderr and exit with EX_NOPERM instead of sending the rejection by executing sendmail. + dovecot --log-error logs now a warning, an error and a

About 9 months ago, I made a policy decision to adopt RAID 1 on all systems I admin. (about 20 systems, all told) It's been a long, slow process. One of the systems is being upgraded from CentOS3 to CentOS4. It's been rock-solid stable for over a year. It's a "frankenserver" with parts from all over the place, maintained over years of active service. Currently,

BAADCAAHDwEHEAEKFwESKwIXNQIaOwIcQQIgSQIpXwM4gAQ8igU/kAVAkwVB lAVClwVCmAVFngVJpgZKqQZLrQZPtQZQtgZRuQYAAAAAAQB1lW3cAAAAAXRS TlMAQObYZgAAAAFiS0dEAIgFHUgAAAAJcEhZcwAALiMAAC4jAXilP3YAAAAH dElNRQfXAxgNAiAQYlKOAAAAHXRFWHRDb21tZW50AENyZWF0ZWQgd2l0aCBU aGUgR0lNUO9kJW4AAADMSURBVEjHzZbJEsMwCEPpvjfdW9T//89OkktqVxgy PpSjzLPHQeCIZKGDkGJoFsF0E1EW0XyCaFVA/fl3RvzaTfW6nPTaaQqWP1TP

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