On Tue 12/Jun/2012 14:37:43 +0200 Sam Varshavchik wrote:
> Alessandro Vesely writes:
>>
>> I apparently lost a message. I found it in the log:
>> [...]
>> But it wasn't in the folder it should have gone to. It isn't
>> anywhere.
>>
>> The Maildrop recipe consists of if (...) { ...; to "./..."; }
>> and terminates with to "./Maildir/".
>
> Well, you have an alternative delivery there, so that's maybe where it
> went.
The alternative deliveries use local mailboxes in the form
to "./Maildir/.Some.Folder";
> Otherwise, there are only two possibilities. It was delivered, but
> subsequently to that some other process deleted.
I might have inadvertently killed it, but not from the Trash folder.
> Or, there was a delivery error, but Courier thought that the
> message was accepted for delivery.
>
> Double-check how you have Courier invoke maildrop; using either
> DEFAULTDELIVERY or from a .courier file; that it's a simple
> invocation. If you have a whole shell mini-script in there, that
> invokes maildrop, depending on how it's done maildrop's exit code may
> get lost, and Courier has no indication that mail delivery failed.
Nope, I have DEFAULTDELIVERY=./Maildir and .courier is
| /usr/local/bin/maildrop
I hadn't altered the recipe for quite some time.
Another possibility is that the message had been considered empty, for
some reason. I asked the remote sender if they logged anything
unusual, but got no reply yet.
--
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
