On 06/12/2012 05:15 AM, Alessandro Vesely wrote:
> But it wasn't in the folder it should have gone to. It isn't
> anywhere. I only have seven (other) messages from that guy,
> so I run a
> find ./Maildir -type f | xargs grep -li xxxx@yyyy
> search, but it only found the same seven messages as the MUA.
You're looking for the wrong information. The 'from' address listed in
the mail log may not be anywhere in the message file.
The only thing that matters is the "id". First, search the log again.
You appear to be missing the courierd "started" line that reflects which
user/directory received the message. Starting at that directory, search
for files containing the message "id".
find . -type f -exec fgrep -l \
00000000005DC03F.000000004FD63F99.00003F1E {}+
> It is the second time this happens to me, in all these years,
> but the previous time I hadn't been able to locate the log
> entries so I gave up. How can this be at all possible?
>
> The Maildrop recipe consists of if (...) { ...; to "./..."; }
> and terminates with to "./Maildir/". A disk error should have
> been reported prominently, shouldn't it? (I run a Debian
> squeeze.)
An IO error would have resulted in a delivery failure, yes. Filesystem
corruption that happened afterward would not, so it depends on what you
mean by "disk error".
Sam has previously given the advice that all of your "to" and "cc"
entries which refer to a Maildir should end in "/." like "./Maildir/."
as this universally and unambiguously refers to a directory and cannot
result in a message being delivered to an mbox file. Even if your
platform is not ambiguous about this, make a habit of using that format.
------------------------------------------------------------------------------
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
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
