On Sun, Aug 13, 2006 at 06:30:02PM +0200, Josip Rodin wrote:
> Compared to the current maildrop 2.x package (in experimental), the
> dependencies [of maildrop and courier-maildrop packages] only differ in
> the fact that the courier-maildrop package depends on courier-base, while
> maildrop has a plugin for courier-authlib.
Upon switching to maildrop 2.x on a production system with a more complex
setup than the one where I usually tested the package, I noticed several
problems:
* the switch to PCRE introduced the normal regular expression syntax which
is a worthy goal, but unfortunately that also means that:
* it voided the old pattern->variable syntax, where /first!second!third/
would create variables $MATCH1=first, $MATCH2=second and $MATCH3=third.
This one's easy to fix, you just have to replace all your !s with
parenthesis marks in the right places, and re-count your matches
(since there is no more implicit matching of the part up to the first !)
* the checking of character classes became more rigorous, so it will die
when encountering a standalone named class [:something:] outside of a
character class - easily fixed by adding another set of []s around it.
* the switch to courier-authlib made the -d option imply a connection to the
Courier authdaemon, whereas for normal users such a connection is not
attempted. This causes problems in MTA-to-MDA interaction if for example
you had your Exim transport run maildrop -d $local_part and at the same
time used its own user/group-setting mechanism. This appears to have been
a pointless setup even before when it didn't crap out - but now the
solution is simple - just drop the -d $local_part bit.
Of course, all of the above errors cause a temporary error and make the
messages remain in queue. But they still all require a manual intervention,
and that sounds like it will prompt a lot of bug reports :(
--
2. That which causes joy or happiness.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
