-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 12 Nov 2002 20:21:51 -0500, Michael Fratoni wrote: > > > I've noticed that I had an incoming mail message go missing, and > > > am looking at possible ways to prevent it in the future. Pointers > > > to what I've missed much appreciated. > > > > > > I use fetchmail (in daemon mode) to pop mail from my mailserver as > > > well as a couple of external servers. The mail is filtered via > > > procmail and spam assassin, and delivered to > > > /var/spool/mail/mfratoni. I then view the mail with kmail. > > > > Most likely it was due to procmail not using the same file locking > > mechanism than kmail (or even no file locking at all like Mozilla > > Mail, IIRC). You can add "VERBOSE=yes" to your ~/.procmailrc and see > > what lock file procmail uses. Then find out what locks kmail uses. > > Yes, I've done that, and procmail seems to do the right thing: > procmail: Locking "/var/spool/mail/mfratoni.lock" > procmail: Assigning "LASTFOLDER=/var/spool/mail/mfratoni" > procmail: Opening "/var/spool/mail/mfratoni" > procmail: Acquiring kernel-lock > procmail: Unlocking "/var/spool/mail/mfratoni.lock" > procmail: Notified comsat: "mfratoni@55372:/var/spool/mail/mfratoni" > > > Until you've found a bullet-proof way, you could store all your > > incoming mails in a backup folder with a procmail rule at the top of > > your procmailrc: > > :0 c: > > > > backup > > Good idea, thanks. I'm also going to file a bug against kmail, and see > where that goes. I'm guessing kmail isn't honoring the file lock? Maybe this one is of help: http://docs.kde.org/3.0/kdenetwork/kmail/faq.html#id2836552 - -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) iD8DBQE90azq0iMVcrivHFQRAngkAJsHfUU2dUI7g8DWfkDsMfKBjl73GQCdGHqR /bO4VR7vaDp6pxroulLmTz4= =lNVe -----END PGP SIGNATURE----- -- Psyche-list mailing list Psyche-list@redhat.com https://listman.redhat.com/mailman/listinfo/psyche-list
