Re: How to identify unread (new/old) mail -- another bit of info
Hello Dan, On Monday, January 28, 2008 at 14:48:17 +0100, Daniel Haude wrote: mutt still refuses to identify mail that hasn't been read. Even if new mail comes in during a session while the inbox is open. Is the number of the just delivered mail included on the unseen: line of .mh_sequences? Otherwise it's to be considered already read. Bye!Alain.
Re: How to identify unread (new/old) mail -- another bit of info
On Thu, Jan 31, 2008 at 01:28:23AM +0100, Alain Bench wrote: Is the number of the just delivered mail included on the unseen: line of .mh_sequences? Otherwise it's to be considered already read. I've found the source of the problem. It's because procmail doesn't update the .mh_sequences file. Currently I'm experimenting with procmail and nmh, without much success so far. I don't like Maildir because that's not working well with Claws. --D. signature.asc Description: Digital signature
Re: How to identify unread (new/old) mail -- another bit of info
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday, January 31 at 03:18 PM, quoth Dan H.: On Thu, Jan 31, 2008 at 01:28:23AM +0100, Alain Bench wrote: Is the number of the just delivered mail included on the unseen: line of .mh_sequences? Otherwise it's to be considered already read. I've found the source of the problem. It's because procmail doesn't update the .mh_sequences file. Currently I'm experimenting with procmail and nmh, without much success so far. I don't like Maildir because that's not working well with Claws. Ahh, well, according to Google, the way to use procmail to deliver to MH folders properly is to tell procmail to pipe the message to a program called rcvstore (part of the nmh package). ~Kyle - -- To sin by silence when they should protest makes cowards of men. -- Abraham Lincoln -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFHoeeJBkIOoMqOI14RAmGGAJ9K+A8AZJIkXHrekhFLlhDCxzjNqgCfUvfq /sAonhi7RleB7dnJd2E8EA8= =dlST -END PGP SIGNATURE-
Refused by Server
When sending mail from mutt I have begun getting the following message in /var/log/mail.log: Jan 31 07:02:37 bill-2 postfix/smtp[868]: E0F13CD105: to=[EMAIL PROTECTED], relay=mx1.comcast.net[76.96.62.116]:25, delay=0.73, delays=0.29/0.1/0.33/0, dsn=4.0.0, status=deferred (host mx1.comcast.net[76.96.62.116] refused to talk to me: 554 IMTA11.westchester.pa.mail.comcast.net comcast 76.27.219.66 Comcast BL001 Blocked. Can anyone shed some light on how to fix this? Thanks
Re: Refused by Server
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday, January 31 at 03:40 PM, quoth [EMAIL PROTECTED]: When sending mail from mutt I have begun getting the following message in /var/log/mail.log: Jan 31 07:02:37 bill-2 postfix/smtp[868]: E0F13CD105: to=[EMAIL PROTECTED], relay=mx1.comcast.net[76.96.62.116]:25, delay=0.73, delays=0.29/0.1/0.33/0, dsn=4.0.0, status=deferred (host mx1.comcast.net[76.96.62.116] refused to talk to me: 554 IMTA11.westchester.pa.mail.comcast.net comcast 76.27.219.66 Comcast BL001 Blocked. Can anyone shed some light on how to fix this? Looks like Comcast is blocking you. I suggest either changing your postfix config to use authenticated SMTP to your ISP (presumably, Comcast), or configuring mutt to use its own smtp-auth support (you may need to recompile mutt). ~Kyle - -- Only the fool hopes to repeat an experience; the wise man knows that every experience is to be viewed as a blessing. -- Henry Miller -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFHoe83BkIOoMqOI14RAvafAKCfX1EZroem/bSDig8aBDeSGmlNBQCfcFpA mjplJ2P2cYkV6UwNiMpw31o= =waP0 -END PGP SIGNATURE-
mutt crashes with imap
So I have a user that is having a very hard time with mutt and connecting to a IMAP mailbox. Once or twice a day his mutt will lock up for 5-10mins when fetching a message and then finally disconnects from the server. Here is the snippet if you strace mutt, read(3, 0x8954f00, 5) = -1 ETIMEDOUT (Connection timed out) write(3, \25\3\1\0 \2549\246\302\347\217 \213\264\212\332\337E#..., 37) = -1 EPIPE (Broken pipe) --- SIGPIPE (Broken pipe) @ 0 (0) --- close(3)= 0 close(5)= 0 munmap(0xb7d68000, 4096)= 0 We are running Cyrus IMAP 2.2.x from RHEL4 and both mutt on RHEL4 and a hand built 1.5.17. Any thoughts? Anyone seen this or and idea if i can build mutt with more debugging? Thanks, derek - Derek Yarnell UNIX Admin Unversity of Maryland Institute for Advanced Computer Studies
Re: mutt crashes with imap
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday, January 31 at 03:40 PM, quoth Derek Yarnell: So I have a user that is having a very hard time with mutt and connecting to a IMAP mailbox. Once or twice a day his mutt will lock up for 5-10mins when fetching a message and then finally disconnects from the server. Here is the snippet if you strace mutt, read(3, 0x8954f00, 5) = -1 ETIMEDOUT (Connection timed out) So, his connection is timing out. One way to prevent that is to set the mail_check and imap_keepalive to lower values. The default for the latter is 900 seconds (15 minutes), which is well-under the 30-minute timeout specified in the IMAP spec. But if Cyrus has changed the timeout to something lower, you may want to try lower values too. ~Kyle - -- Habits of thought persist through the centuries; and while a healthy brain may reject the doctrine it no longer believes, it will continue to feel the same sentiments formerly associated with that doctrine. -- Charlotte Perkins Gilman -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFHok0pBkIOoMqOI14RAhggAJwJCvto59hiPwxiJyzGPsYMNGIE1wCgmSGY ZFh0WZ77PuMheFJun/+Zui4= =sSNc -END PGP SIGNATURE-
Re: Refused by Server
For the use of any others who use Leopard Migration Assistant and find they have hammered their previous postfix settings. The previous /etc/postfix/main.cf configuration file does NOT get moved to the new location by Migration Assistant, and must be placed there manually. When I replaced /etc/postfix/main.cf with my previous configuration file, and restarted postfix, everything came back up as it should be. SMTP is now working. Thanks for everyone's assistance. bj -- Original message -- From: Kyle Wheeler [EMAIL PROTECTED] -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday, January 31 at 03:40 PM, quoth [EMAIL PROTECTED]: When sending mail from mutt I have begun getting the following message in /var/log/mail.log: Jan 31 07:02:37 bill-2 postfix/smtp[868]: E0F13CD105: to=[EMAIL PROTECTED], relay=mx1.comcast.net[76.96.62.116]:25, delay=0.73, delays=0.29/0.1/0.33/0, dsn=4.0.0, status=deferred (host mx1.comcast.net[76.96.62.116] refused to talk to me: 554 IMTA11.westchester.pa.mail.comcast.net comcast 76.27.219.66 Comcast BL001 Blocked. Can anyone shed some light on how to fix this? Looks like Comcast is blocking you. I suggest either changing your postfix config to use authenticated SMTP to your ISP (presumably, Comcast), or configuring mutt to use its own smtp-auth support (you may need to recompile mutt). ~Kyle - -- Only the fool hopes to repeat an experience; the wise man knows that every experience is to be viewed as a blessing. -- Henry Miller -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFHoe83BkIOoMqOI14RAvafAKCfX1EZroem/bSDig8aBDeSGmlNBQCfcFpA mjplJ2P2cYkV6UwNiMpw31o= =waP0 -END PGP SIGNATURE-
