In regard to: Re: [Imap-uw] tweaking env_unix.c for different spool...:
On Tue, 5 Dec 2006, John Kelly wrote:
>Note that once you have an INBOX file in a user's home directory, any
>mail that gets delivered to /var/spool/mail/username is effectively
>invisible, so you want to make sure nothing ever gets delivered to
>/var/spool/mail/username
Not a problem. uw-imap "snarfs" any spool mail over to INBOX on the
next client connect, disk quotas permitting.
Exactly. This is also why you don't want to maul sysinbox(). As long as
sysinbox() points at the traditional UNIX mail spool, the snarfing will take
care of any messages which get misdirected to the spool.
At one time we were modifying sysinbox(); perhaps that's how we picked
up the bit of "wisdom" about /var/spool/mail/username. I do know that
we had messages end up "lost" in /var/spool/mail/username for weeks or
months, even though the user was checking their mail via imapd regularly.
Based on Mark's recommendation last year, after explaining why modifying
sysinbox() wasn't needed when using mbxproto, we quit "mauling"
sysinbox(). It seems likely that the problem we had, with messages there
being invisible to imapd, went away at the same time and we didn't know
it.
Thanks for the additional education -- it's good to know that getting
rid of the change to sysinbox() also fixed the problem with mail delivered
to /var/spool/mail/username.
Tim
--
Tim Mooney [EMAIL PROTECTED]
Information Technology Services (701) 231-1076 (Voice)
Room 242-J6, IACC Building (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164
_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
