Constantine Kousouris writes:
This happens ONLY for me, all the other users (and they are a lot ...) do not have this problem ...
What's different for you, then? Do you have a custom maildrop recipe? Let's see it.
What exactly "deliver: Is a directory" mean ...???
"deliver" handles mail delivery. If it starts a child process that complains about something on standard error, it gets logged, and deliver gets blamed for it.
It is supposed to be a directory after all, since it is a maildir ...
It means that something is a directory, when it shouldn't be: [mrsam@octopus ~]$ mkdir ttt [mrsam@octopus ~]$ >ttt -bash: ttt: Is a directory
In addition messages are delivered alright in maildir subfolders using dot-courier (.courier-zzzzz) ...!!!
Ok, then let's look at your .courier files, too.
I assumed that there is something peculiar in my maildir that confuses mail delivery, so i created a brand new maildir. At first it worked fine and messages were deliverd for a while but soon the problem appeared again.
That suggests a mail delivery script with a race condition that occasionally gets triggered.
When I switch to the old Netapp system everything works fine ... Any ideas ...???
It could be that your old mail system was not triggering a race condition. Entirely plausible.
pgphECFripe4w.pgp
Description: PGP signature
------------------------------------------------------------------------------ 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
