I have a problem in maildrop where a failed "cc" rule will
also cause a subsequent "to" rule to fail.
I'm running the full courier suite, including
courier-imap and sqwebmail.
In $sysconfdir/courierd, I have
DEFAULTDELIVERY="| $prefix/bin/maildrop"
(where $sysconfdir and $prefix have the usual autoconf meanings)
I have a couple of users who would like a copy of their email
delivered to their work address.
So I had them create a filter rule via sqwebmail, forwarding
all messages of non-zero size to their work address, with the
"and continue filtering" block checked. This produces the
following maildrop text (names changed to protect the guilty):
##Op:islargerthan
##Header:
##Value:0
##Folder:[EMAIL PROTECTED]
##From:
##PlainString
##Continue
##Name:forward-to-work
if (($SIZE > 0))
{
cc "| $SENDMAIL -t -f '$FROM' [EMAIL PROTECTED]"
}
to "./Maildir/."
My problem is that the ship.navy.mil server is often down for days at
a time, and as a result, the messages are not getting delivered to the
local inbox. Apparently, from reading the control files, the
$SENDMAIL process is exiting with an error, and the message is
deferred before the "to" line gets processed.
I think that I once tried writing the filter the other way, so that
the "cc" goes to the local mailbox while the "to" goes to the remote
one, but the effect is even worse. For every failure in remote
delivery, the local mailbox gets an extra copy of the message.
Can anybody suggest an easy way for my users to instruct courier to
always deliver to the local inbox, and attempt to deliver a copy to
the remote mailbox, as well?
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
