Neil Romig | 20 Apr 14:03 2016

getaddr confusion

I am using getaddr in .mailfilter to extract addresses:

if( /^From:\s*(.*)/:h )

I have added log "$FRM" to the .mailfilter file to investigate, and it
fails to extract the address from lines like this:

From: "Someone - Mailbox" <someone <at>>

But it will work with:

From: "Some One" <someone <at>>

I guess the hyphen is causing trouble - is this a bug or am I failing
to understand?



Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!;130105516;z
(Continue reading)

Philip Rhoades | 4 Feb 09:14 2016

Getting xfilter AND delivery to working


I have this filter:

if( /^[TC][[co]:.*tst/ )
     xfilter "/home/phil/bin/ > /home/phil/t"
     to $DEFAULT/.tst/

and the xfilter is working but the delivery is not - if I reverse the 
lines, the delivery works but the xfilter does not - how can I get BOTH 
lines to work?



Philip Rhoades

PO Box 896
Cowra  NSW  2794
E-mail:  phil <at>

Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
(Continue reading)

Christian Ebert | 21 Dec 15:11 2015

courier-unicode fails to build on Mac OS 10.10.5


Version 1.4 of courier-unicode fails to build like so:

make[1]: Entering directory '/Users/chris/src/courier-unicode-1.4'
/bin/sh ./libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.     -I.. -I./.. -g -O2 -Wall
-fexceptions -MT unicode.lo -MD -MP -MF .deps/unicode.Tpo -c -o unicode.lo unicode.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I./.. -g -O2 -Wall -fexceptions -MT unicode.lo -MD -MP
-MF .deps/unicode.Tpo -c unicode.c  -fno-common -DPIC -o .libs/unicode.o
In file included from unicode.c:8:
./courier-unicode.h:44:43: error: unknown type name 'locale_t'
extern const char *unicode_locale_chset_l(locale_t l);
unicode.c:41:36: error: unknown type name 'locale_t'
const char *unicode_locale_chset_l(locale_t l)
unicode.c:43:21: warning: implicit declaration of function 'nl_langinfo_l' is invalid in C99
        return fix_charset(nl_langinfo_l(CODESET, l));
1 warning and 2 errors generated.
Makefile:748: recipe for target 'unicode.lo' failed
make[1]: *** [unicode.lo] Error 1
make[1]: Leaving directory '/Users/chris/src/courier-unicode-1.4'
Makefile:556: recipe for target 'all' failed
make: *** [all] Error 2

$ sw_vers
ProductName:	Mac OS X
ProductVersion:	10.10.5
(Continue reading)

Sam Varshavchik | 21 Dec 05:04 2015

(no subject)

I've packaged the 20151220 build of maildrop and courier packages.



• maildrop: fix parsing a message without a body, and without a blank line
that separates the message's headers from its body.

This did not affect Courier which always inserts a blank line after headers,
even if a received message didn't have one.

• maildrop: fix maildrop not searching the last line of a text message.

• maildrop: FLAGS variable sets message flags when delivering a message to a

Courier-maildrop mailing list
Courier-maildrop <at>
Dimitri Maziuk | 18 Dec 17:12 2015

Re: maildrop feature request

On 12/17/2015 06:36 PM, Philippe Cerfon wrote:
> ... basically every
> server that speaks maildir supprts it as described here

A quick ls of my cur shows very few messages with :2,S yet they're all
"seen" in the thunderbird. So yeah, basically every server. Except the
dovecot shipped with rh 6.


Dimitri Maziuk
BioMagResBank, UW-Madison --

Courier-maildrop mailing list
Courier-maildrop <at>
Sam Varshavchik | 17 Dec 13:05 2015

Re: maildrop feature request

Philippe Cerfon writes:

> Don't understand what you mean.
> E.g. (F)lagging a message may simply be desired, regardless of which folder.
> Denoting that an answer has already been written, as e.g. in the
> example above, cannot be done by moving mail to specific folder. It's
> simply what the A flag is for.
> And as for the last example, even when you move it to some folder, the
> mail would still show up as unseen in the user's MUA, which is just
> what's not desired in the above example.

If your maildrop recipe chooses to handle a particular message, in some  
way – say send an autoreply, or set it aside for some special handling –  
all that needs to happen is to deliver the message to the appropriate  
folder; say a folder called "Replied", or "To Do".

And now, instead of having one flat Inbox, that you have to search for, to  
find all of your flagged or replied messages, all of them are easily found  
in a separate folder. They'll certainly be seen as unread in their dedicated  
folder, but so what? If you want to find all of the autoreplied messages,  
you open the "Replied" folder, and there they are. If you want to find all  
of the flagged messages, you open the "To Do" folder. Mission accomplished.

> Cheers,
> Philippe
> On Tue, Dec 15, 2015 at 2:20 AM, Sam Varshavchik <mrsam <at>>  
> wrote:
(Continue reading)

Andreas Kinzler | 16 Dec 22:57 2015

Patch for bug in search function


maildrop 2.7.x and 2.8.x has a bug the causes that the last line of a 
text is not searched. While that alone is a bug, there are cases where a 
whole HTML body only consists of one huge (over 50 kb) line. In that 
case the whole body is not searched.

A simple patch fixes the bug.

Regards Andreas

--- a/libs/maildrop/search.C	2014-01-16 01:50:53.000000000 +0100
+++ b/libs/maildrop/search.C	2014-11-08 03:31:22.332009388 +0100
 <at>  <at>  -215,6 +215,8  <at>  <at> 
 				msg.rfc2045p, &decode_cb);
+	if (current_line.Length() >= 1)
+		search_cb("\n", 1);
 	return 0;

(Continue reading)

Sam Varshavchik | 15 Dec 02:20 2015

Re: maildrop feature request

Philippe Cerfon writes:

> On Mon, Dec 14, 2015 at 1:00 PM, Sam Varshavchik <mrsam <at>>  
> wrote:
> >> Have there been any news over the years on this front? I.e. the
> >> problem on how to flag mail's as (S)een, (A)nswered, (D)eleted, etc. ?
> >> That seems to pop up every now and then again here, there are probably
> >> countless of blog entries where people complain about that issue :-(
> > Haven't seen that topic come up in a number of years, actually. I still
> > think that this is a solution in search of a problem.
> There's for example, "[maildropl] Marking a message read when
> delivering to a Maildir" right here on the list, from e.g. 2014
> And as I've said, countless of blog posts, etc. which deal with that issue.
> Also I don't know how you come to idea that this should be the search
> of a problem.
> Setting these flags seem to be one of the most basic featurs,
> supported by sieve, or any MUA's internal filtersystem.
> And it makes perfectly countless of use cases:
> - e.g. automatically (f)lagging messages, based on e.g. From
> - when maildrop is e.g. used to automatically reply to certain mails
> (via passing them on to some scripts or so), may be desired to have
> them marked (A)nswered
> - when having high volume mailing lists subscribed, one may want to
> mark most messages (S)een since one isn't interested in them, except
> those which are e.g. directly To:ed to one self, or which include
> certain keywords, etc. pp

Why would delivering messages to the appopriate folder, instead, be a  
(Continue reading)

Philippe Cerfon | 14 Dec 05:13 2015

Re: maildrop feature request

Hey Sam, et all.

Have there been any news over the years on this front? I.e. the
problem on how to flag mail's as (S)een, (A)nswered, (D)eleted, etc. ?
That seems to pop up every now and then again here, there are probably
countless of blog entries where people complain about that issue :-(

It seems there has even been a patch proposed
Any reason not to merge that or solving that somehow else?

That, plus the issue of the dovecot-authlib patches not having been
merged here and subsequently been dropped from many distros, makes
using maildrop quite difficult. And it seems to me without any
necessity :-/


On Mon, Oct 18, 2010 at 11:51 PM, Sam Varshavchik <mrsam <at>> wrote:
> Philippe Cerfon writes:
>> Dear maildrop maintainer.
>> I and my customers make heavy use of (standalone) maildrop for filtering.
>> On missing feature though, which we get manually by some ugly hack at
>> the moment is the ability to deliver mail (via to) and in addition set
>> a status on it immediately.
>> Most important would be to mark the mail read, but also replied (e.g.
>> in case there are automatic replies programmed)
(Continue reading)

Kamil Jońca | 2 Sep 20:30 2015

Re: pattern match body?

kjonca <at> (Kamil Jońca) writes:

> I have patern:
> KJ_NO_RCVDS=(/^Received:\s/:h,1) 
> log "Number of received ${KJ_NO_RCVDS} "
> and with attached message I got ... 1
Sorry, file was missing
Attachment (77.eml): application/octet-stream, 3651 bytes


When I saw a sign on the freeway that said, "Los Angeles 445 miles," I said
to myself, "I've got to get out of this lane."
		-- Franklyn Ajaye
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
Courier-maildrop mailing list
Courier-maildrop <at>
(Continue reading)

rlharris | 10 Aug 22:10 2015

error 75, error 164

I am receiving the following error message:

Delivery error (command maildrop 18470 error (75, .mailfilter(164):
  Syntax error after ))) msg 4/1300 (24935 bytes) from
  < <at>>, delivery error
  (command maildrop 18470 error (75, .mailfilter(164): Syntax error
  after )))

but I have not yet spotted a syntax error in ".mailfilter".

I do not know where to look for the definitions of errors number 75 and
164; searching with Google has not provided an answer.

And I am confused by the mismatch in the number of parentheses in the
error message; there are only three opening parentheses but four closing


   after )))

Am I misreading the error message?


(Continue reading)