Why does some list software not honor the headers? (was ... Re: People want ...)
On Wed, Feb 20, 2013 at 07:44:37AM -0500, Patrick Shanahan wrote: > Then it *should* be upon you to adjust your mail-system to provide the > *special* provision that *you* desire rather than force an un-needed extra > copy upon the "rest of the world". The **ONLY** way to not get an extra copy is **NOT** to get CC'd in the first place (and vice versa; i.e you in To and list in CC). It is disgusting that the list software decides whether to honor the headers or not -- "If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing." --- Malcolm X
Forcing closure of an IMAP connection
I use mutt 1.5.20 to access my mail over IMAP held on several different servers. One of these servers was "upgraded" last year and now exhibits an issue whereby approximately 5 minutes after it was last accessed it hangs, but doesn't close, the connection to mutt. This hangs mutt for a couple of minutes then mutt closes the connection and we're all happy again. I don't get a lot of mail on this server and look at it probably once a day or less so this isn't a great problem but it would be great if there was some key combination I could use to do a force a close of the connection. Is there any way of manually closing an IMAP connection in mutt? Regards -- John Landamore Department of Computer Science University of Leicester University Road, LEICESTER, LE1 7RH j.landam...@mcs.le.ac.uk Phone: +44 (0)116 2523410 Fax: +44 (0)116 2523604
Record Sent Mesages to IMAP Folder when Using Mutt on Command Line
Dear all, I've succesfully configured mutt to receive messages via IMAP and send messages via SMTP from/to a mail server (Dovecot, Postfix) in the network. If I send mails using Mutt's user interface, sent mails are saved in the relevant IMAP folder "Sent". But if I use the command-line mode of mutt, e. g. >echo "This is a test message" | mutt -s "Test Message" testu...@mydomain.com or >mutt -s "Test Message" testu...@mydomain.com < /tmp/message_body.txt Mutt sends the e-mail, but does not store a copy of the sent e-mail in the "Sent" folder. What do I miss?
