Trying mutt out again with mbox and atime set
I have now got my new server running and I'm testing out mutt with mbox mail storage and with atime set. This message is really just a test message to myself, sorry for the noise. I will however report if it all works or not. -- Chris Green
Re: Trying mutt out again with mbox and atime set
On Wed, Jun 23, 2010 at 09:21:39PM +0100, Chris G wrote: I have now got my new server running and I'm testing out mutt with mbox mail storage and with atime set. This message is really just a test message to myself, sorry for the noise. I will however report if it all works or not. ..., and it *doesn't* work. :-( I now have two nearly identical Ubuntu 10.04 servers running. I'm delivering mail by SMTP to both of them by using the forwarding at my hosting site so both of my servers receive identical mail by SMTP. Both servers run postfix and that delivers mail to 'me' (user chris), there is a .forward file that passes the mail on to a python script that delivers the mail to the appropriate mailbox - maildir on one system and mbox on the other. My previous mail to the list has been delivered back to both systems and has arrived in the mailbox ~/Mail/Li/mutt in both cases. On the maildir system mutt sees the new mail and I can 'c' to the mailbox and see the mail. On the mbox system mutt doesn't see the mail as new and I can't use 'c' to get to it. However if I navigate to the mutt mailbox on the mbox system the message is marked as new with an 'N' by it. I have the following in muttrc:- mailboxes /var/mail/chris ~/Mail/In/inbox `echo ~/Mail/Li/*` `echo ~/Mail/In/*` So I need to reread my muttrc file to see new mailboxes in Li or In but I have done that and mutt *still* doesn't see new mail on the mbox system. I'm confused, what is going on, surely mutt should recognise a *new* file as one that has new mail in it. -- Chris Green
Re: Trying mutt out again with mbox and atime set
Chris G schrieb am 23.06.2010 um 21:40 (+0100): I'm confused, what is going on, surely mutt should recognise a *new* file as one that has new mail in it. Why don't you simply use the option Christian suggested yesterday and call it a day? set check_mbox_size = yes I agree the parameter name is not intuitive - but it works. -- Michael Ludwig
Re: Trying mutt out again with mbox and atime set
On Wed, Jun 23, 2010 at 09:40:42PM +0100, Chris G wrote: I'm confused, what is going on, surely mutt should recognise a *new* file as one that has new mail in it. ... but maybe it doesn't. In fact how would it recognise a newly created file as one having new mail in it, it typically looks like:- Times for file mutt 2010-06-23 21:41:40.00 Modifed 2010-06-23 21:41:40.00 Accessed 2010-06-23 22:20:35.07 Status changed So the access time is the same as the modified time and mutt doesn't see it as having new mail. Since I rarely leave any mail in these mbox files (I save mail I want to keep elsewhere) and I have save_empty=no much of my new mail is in fact a completely new mailbox. Maybe this is the problem I have seen in the past. Since I have control of the writing process (my python filtering script) I can set the modified time for the mbox file a few seconds in the future, can anyone see any problem with doing this. I have modified the script to do it and it *seems* to be working but I may have overlooked something. -- Chris Green
