Re: Mailing list Subject: line
--> grarpamp [2013-02-08 22:17:26 -0500]: > If at all possible I'd like to see the Subject: line for this list > updated from... > Subject: ...thread... > ...to... > Subject: [mutt-users] ...thread... I got this far in your email and had to reply no - please don't do that. Sorry but it's not to everyones taste i'd imagine. I haven't even read other replies yet but i'm pretty sure they will say a similar thing.
Re: Mailing list Subject: line
On 08.02.13 22:29, Will Yardley wrote: > On Fri, Feb 08, 2013 at 10:17:26PM -0500, grarpamp wrote: > > > If at all possible I'd like to see the Subject: line for this list > > updated from... > > Subject: ...thread... > > ...to... > > Subject: [mutt-users] ...thread... > > > I'm aware mail filters are readily available to some. I'm suggesting > > it because the prefixed subject line model is very prevalent these > > days, particularly with mailman, and would further hazard the > > suggestion that as such it should be considered a reasonable standard > > worth implementing. No, it is not considered reasonable here, I think you'll find. Though present on a number of lists, I have encountered the subject line pollution on only one other list. It was soon removed, after community objection. (AFAICT. I implemented a procmail filter to remove the pollution from mails received here, but have read on the list that it is no longer sent.) > Given the number of threads on here about getting *rid* of those things, > I doubt there will be a lot of enthusiasm for this suggestion on this > mailing list. +1 > That said, you should check out '$index_format' in the muttrc man page > -- if the list is defined properly, you should already see (with the > default index format) the mailing list name in your index already, so > even if you're not filtering, it should be pretty obvious what mailing > list the message was sent to. Beatifully parried, Will. With recipients disinclined to sort their mail able to have their cake and eat it too, there is no longer any pretext on which the one can reasonably impose on the community to make up for personal lack of effort. Erik (Who has 20 incoming mailboxes, and 1138 mailboxes for sorting after reading.) -- One man's constant is another man's variable. - A.J. Perlis
Re: build problems on Solaris 8
On Fri, Feb 08, 2013 at 04:46:28PM -0800, Will Yardley wrote: > On Fri, Feb 08, 2013 at 05:30:03PM -0700, s. keeling wrote: > > Incoming from Michael Elkins: > > > > FYI, there are nightly snapshots here http://dev.mutt.org/nightlies/ > > > which avoid the need to have the developer toolchain installed. > > > > Michael, kind of off topic, I know, but why would you want to > > discourage people from learning the developer toolchain? > > I think the point is that minimizing the build dependencies for people > who aren't developers should reduce build problems quite a bit. There's another issue and as a Solaris user I'm painfully aware of it ;-) As you get further and further away from Linux as in Linux -> BSD UNIX -> Solaris -> other UNIX etc. the typical app written for Linux is less and less likely to build without pain either because of compiler, library, prereqs or other problems. Many apps don't even seem to get tested anywhere but Linux. Building apps isn't the best use of most peoples' time. If you have a trustworthy place to get the apps you want that's a good way to go. -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04
Re: rendering color in html emails inside mutt
Am Fri, Feb 08, 2013 at 05:23:23PM +0100, Eric Smith wrote: > I have never managed to render color in html email, how is this > possible? Yes, this is a question, which would interest me too. I also have sometimes this problem. -- :: Igor Sosa Mayor :: joseleopoldo1...@gmail.com :: :: GnuPG: 0x1C1E2890 :: http://www.gnupg.org/ :: :: jabberid: rogorido :::: pgpxtTXUxz0Qn.pgp Description: PGP signature
Re: Mailing list Subject: line
Derek Martin wrote: > But this philosophy favors the casual list member over the people who > read the list regularly. The community should cater to its regular > members, not people whose interest and participation are fleeting... > So this approach is wrong. The Mutt community, by and large, chooses > Mutt because it is a superior tool for many mail processing needs; > they also tend to use other powerful tools to further improve and > streamline their mail processing needs. This question, and others > like it arise on the list from time to time, and on the whole the > community rejects the notion of "dumbing down" list policies (like > this one, or like setting reply-to to the list address) for the > benefit of those who are ignorant of, or can't be bothered to use > better tools. I've been here for nearly 15 years, and the arguments > have been pretty consistent for the entirety of that time. +1! Insightfully written. > s. keeling wrote: > > I'm a sysadmin. My job is to make users' wishes happen, as long as > > they don't hurt others or the overall system. > > I was a sysadmin for a very long time, and I daresay I was a pretty > darn good one... I disagree that your job is to make users' wishes > happen. Your job is to help your users to best leverage the > technology you manage for them to achieve their goals. Sometimes, > part of that job is recognizing that what the user thinks he wants IS > WRONG, and pointing out that there are better alternatives. And > sometimes, your job IS to get in their way, when getting their way > hurts the greater user community. +1 again. I try to only very rarely post me-too types of posts. But I was compelled to say something positive about these very well thought out comments. It is as important to prevent us from moving backward as it is to try to keep moving us forward. Bob signature.asc Description: Digital signature
Re: rendering color in html emails inside mutt
On 2013-02-08, Eric Smith wrote: > Hi. > > (For those deeply offended by manifestations of html in emails, > please look away now). > > I mainly receive email from non-technical people. Recently, > while in the chaos ahead of a deadline I missed some > important email where answers to my questions where inserted > inline in a red color. > > I have never managed to render color in html email, how is this > possible? This is a function of the external program used to render HTML as text. The two that seem to be the most popular, lynx and w3m, don't seem to do this, but elinks does. So, all you should have to do is set your mailcap file to use elinks for text/html and configure elinks to use 256 colors. While running elinks, type to see the menu bar, then go to "Setup menu" -> "Terminal options" and select under "Color mode"->"256 color". I've often wondered if this was possible, but never investigated it very deeply. Your question piqued my curiosity, so I searched a little and just discovered that elinks could do this. I've verified its behavior on a few web sites, but not from within mutt. Let us know if this works for you. Regards, Gary
Re: rendering color in html emails inside mutt
On Saturday, 09 February 2013 at 13:15, Gary Johnson wrote: > On 2013-02-08, Eric Smith wrote: > > Hi. > > > > (For those deeply offended by manifestations of html in emails, > > please look away now). > > > > I mainly receive email from non-technical people. Recently, > > while in the chaos ahead of a deadline I missed some > > important email where answers to my questions where inserted > > inline in a red color. > > > > I have never managed to render color in html email, how is this > > possible? > > This is a function of the external program used to render HTML as > text. The two that seem to be the most popular, lynx and w3m, don't > seem to do this, but elinks does. > > So, all you should have to do is set your mailcap file to use elinks > for text/html and configure elinks to use 256 colors. While running > elinks, type to see the menu bar, then go to "Setup menu" -> > "Terminal options" and select under "Color mode"->"256 color". > > I've often wondered if this was possible, but never investigated it > very deeply. Your question piqued my curiosity, so I searched a > little and just discovered that elinks could do this. I've verified > its behavior on a few web sites, but not from within mutt. Let us > know if this works for you. Elinks does work fine to view attachments in color. You can't get color when autoviewing though -- in this case, the elinks output is recolorized by the pager using color body rules, which mangle the underlying color.
Re: rendering color in html emails inside mutt
On 2013-02-09, Brendan Cully wrote: > Elinks does work fine to view attachments in color. You can't get > color when autoviewing though -- in this case, the elinks output is > recolorized by the pager using color body rules, which mangle the > underlying color. Even if allow_ansi is set? Regards, Gary
Re: rendering color in html emails inside mutt
On Saturday, 09 February 2013 at 13:27, Gary Johnson wrote: > On 2013-02-09, Brendan Cully wrote: > > > Elinks does work fine to view attachments in color. You can't get > > color when autoviewing though -- in this case, the elinks output is > > recolorized by the pager using color body rules, which mangle the > > underlying color. > > Even if allow_ansi is set? Yes, on my system at least, the first character of the line is colored but the rest are clobbered, in autoview mode. When I switch to view-attachment mode, everything looks fine. With allow_ansi unset, not even the first character is colored.
Re: rendering color in html emails inside mutt
* Brendan Cully [2013-02-09 22:38]: On Saturday, 09 February 2013 at 13:27, Gary Johnson wrote: On 2013-02-09, Brendan Cully wrote: Elinks does work fine to view attachments in color. You can't get color when autoviewing though -- in this case, the elinks output is recolorized by the pager using color body rules, which mangle the underlying color. Even if allow_ansi is set? Yes, on my system at least, the first character of the line is colored but the rest are clobbered, in autoview mode. When I switch to view-attachment mode, everything looks fine. With allow_ansi unset, not even the first character is colored. You could give '-dump-color-mode 3' a try - it works quite good but you'll be in trouble if you try to print those HTML-messages ... ;-) HTH Stefan pgpnV9NXJwDBs.pgp Description: PGP signature
People that CC mailing lists
I've a few mailing lists where people don't send to the mailing list instead they CC it. In which case when I reply to the list mutt doesn't recognise it as a list and I have to do a normal reply and manually put in the mailing list address in the send field. Is there a way of getting mutt to recognise a list from the CC address? I guess the other way is to nag people into using a proper email client :) -- When all you have is a Swiss Army Knife, every problem looks like email. -- Peter da Silva
Re: People that CC mailing lists
* David Woodfall [02-09-13 19:44]: > I've a few mailing lists where people don't send to the mailing list > instead they CC it. In which case when I reply to the list mutt > doesn't recognise it as a list and I have to do a normal reply and > manually put in the mailing list address in the send field. > > Is there a way of getting mutt to recognise a list from the CC > address? procmail, remove dups # remove duplicates ## from man procmailex examples ## # 12-13-2002 ### adjust cache size to suit personale pref # --- LOCKFILE = msgid.cache.lock :0 Whc: msgid.lock | $FORMAIL -D 16384 msgid.cache LOCKFILE ### save duplicates in case of error :0 a: $MAILDIR/duplicates # --- -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535@ http://linuxcounter.net
Re: People that CC mailing lists
On (09/02/13 20:08), Patrick Shanahan put forth the proposition: * David Woodfall [02-09-13 19:44]: I've a few mailing lists where people don't send to the mailing list instead they CC it. In which case when I reply to the list mutt doesn't recognise it as a list and I have to do a normal reply and manually put in the mailing list address in the send field. Is there a way of getting mutt to recognise a list from the CC address? procmail, remove dups # remove duplicates ## from man procmailex examples ## # 12-13-2002 ### adjust cache size to suit personale pref # --- LOCKFILE = msgid.cache.lock :0 Whc: msgid.lock | $FORMAIL -D 16384 msgid.cache LOCKFILE ### save duplicates in case of error :0 a: $MAILDIR/duplicates # --- Thanks, I'll give that a shot
Re: People that CC mailing lists
On (10/02/13 02:08), David Woodfall put forth the proposition: On (09/02/13 20:08), Patrick Shanahan put forth the proposition: * David Woodfall [02-09-13 19:44]: I've a few mailing lists where people don't send to the mailing list instead they CC it. In which case when I reply to the list mutt doesn't recognise it as a list and I have to do a normal reply and manually put in the mailing list address in the send field. Is there a way of getting mutt to recognise a list from the CC address? procmail, remove dups # remove duplicates ## from man procmailex examples ## # 12-13-2002 ### adjust cache size to suit personale pref # --- LOCKFILE = msgid.cache.lock :0 Whc: msgid.lock | $FORMAIL -D 16384 msgid.cache LOCKFILE ### save duplicates in case of error :0 a: $MAILDIR/duplicates # --- Thanks, I'll give that a shot Of course that won't work when someone else is in the To: field. Might be time to put together some sort of formail/shell script maybe.
Re: [POSSIBLE SPAM] People that CC mailing lists
* David Woodfall [130210 00:45]: > I've a few mailing lists where people don't send to the mailing list > instead they CC it. In which case when I reply to the list mutt > doesn't recognise it as a list and I have to do a normal reply and > manually put in the mailing list address in the send field. ... > I guess the other way is to nag people into using a proper email > client :) Please tell me if I am using the wrong command when attempting to reply to a mail list regarding a message on the list. I am running Mutt on Debian Squeeze. In order to reply to your message, I press "g" (for "group reply"), and Mutt generates the following header pair: To: David Woodfall Cc: mutt-users@mutt.org Is there a command other than "g" which is appropriate when replying to a group? RH
Re: People that CC mailing lists
--> David Woodfall [2013-02-10 00:42:27 +]: > I've a few mailing lists where people don't send to the mailing list > instead they CC it. In which case when I reply to the list mutt > doesn't recognise it as a list and I have to do a normal reply and > manually put in the mailing list address in the send field. > > Is there a way of getting mutt to recognise a list from the CC > address? > > I guess the other way is to nag people into using a proper email > client :) Although I also use the procmail trick to remove duplicate mail, if you have used the subscribe and/or lists command you should just be able to use the key L to reply to the list and only the list. I'm pretty sure this works when there are mulitple recipients in a message, inlcuding CC. Jamie -- Primary Key: 4096R/1D31DC38 2011-12-03 Key Fingerprint: A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
