Re: Mail from me doesn't appear i subscribed (mailing lists) folders
Patrick Shanahan schrieb am 14.06.2012 um 15:50 (-0400): * Michael Ludwig mil...@gmx.de [06-14-12 04:40]: My workaround for this helpful gmail feature is to (a) not use gmail or (b) have mutt save a copy of the message I send to the list in the list folder/mbox (using POP3, not IMAP): fcc-hook vim_use@googlegroups\.com =2-Vim But then you don't know it made it to the list ??? Correct, but consider: * The mail system is reliable enough for me, so I'm happy with just SMTP confirmation when sending. * Should I have doubts there'd be an easy way of checking via Google Groups web archives. * It's just mail going to a list. For messages going to an individual (which might be more important) instead of going to a list you don't get a more reliable confirmation either, and you can't check the recipient's inbox like the mailing list web archive. Michael
Re: Mail from me doesn't appear i subscribed (mailing lists) folders
Patrick Shanahan schrieb am 08.06.2012 um 09:29 (-0400): If you are using gmail smtp, gmail has you *original* copy in the Sent folder/virtual-folder/label(???) and the return copy from the list appears to them to be a copy so it does not show. My workaround for this helpful gmail feature is to (a) not use gmail or (b) have mutt save a copy of the message I send to the list in the list folder/mbox (using POP3, not IMAP): fcc-hook vim_use@googlegroups\.com =2-Vim Michael
Re: mutt, html and chrome
Luis Mochan schrieb am 15.05.2012 um 15:22 (-0500): If I insist enough times, the message eventually is successfully displayed in my browser. My guess is that there is some kind of race condition which becomes apparent only when my computer is busy, as if the browser tries to read the temporal file before mutt finishes writing and closing it. IIRC there was an issue where the file would get deleted before the browser would get its hands on it. There's a set of Python scripts that fixes this problem: https://bitbucket.org/blacktrash/muttils Relevant Mutt configuration: # call viewhtmlmsg from macro macro index,pager F7 \ enter-command set my_wait_key=\$wait_key wait_key=noenter\ pipe-messageviewhtmlmsg -k0enter\ enter-command set wait_key=\$my_wait_key my_wait_keyenter\ view HTML in browser macro index,pager F8 \ enter-command set my_wait_key=\$wait_key wait_key=noenter\ pipe-messageviewhtmlmsg -k0 -senter\ enter-command set wait_key=\$my_wait_key my_wait_keyenter\ view HTML (safe) in browser Michael
Re: Hide [bracketed topic indicators] such as prepended by mailing lists
Tom Furie schrieb am 11.04.2012 um 14:47 (+0100): On Wed, Apr 11, 2012 at 01:01:00PM +, Grant Edwards wrote: But, IMO, gmane+slrn is far superior (if gmane carries the list in question). That's because newsgroups are a much better way of handling the type of discussion groups that mailing lists are commonly used for, and indeed is what newsgroups were developed for. Unfortunately they never really caught on in this way. If gmane doesn't carry the list you're interested in you could always set up your own mail-news gateway and keep your slrn interface to the rogue group. But, this is all way off topic for the list, so I'll shut up now. :) While GMANE is somewhat off-topic, it is a very interesting alternative. I tried slrn but found it too emacsy. Tin feels more like vim and mutt so suits me better; there was just one nasty configuration issue, fortunately solved now: Posting not allowed / Posten nicht erlaubt http://comments.gmane.org/gmane.network.tin.user/437 Thanks for pointing to GMANE and the NNTP alternative! Michael
Re: Hide [bracketed topic indicators] such as prepended by mailing lists
David Champion schrieb am 13.04.2012 um 11:37 (-0500): […] this config: subjectrx '^(re: *)?\[[^]:]*\] *' '%1%R' should perform the replacement for *any* list tag that appears at the beginning or after a re: prefix. Great - I find this setting more convenient than having to specify a dozen separate tags. Thank you! Michael
Re: Hide [bracketed topic indicators] such as prepended by mailing lists
David Champion schrieb am 10.04.2012 um 19:10 (-0500): * On 10 Apr 2012, Michael Ludwig wrote: 28.06.11 14:08+0200 Alexander Muyla 21 [Firebird-net-provider] Consol 29.06.11 01:56-0700 ven ~ 6 [Firebird-net-provider] fbdata 30.06.11 19:40+ Nataniel (JIRA) 98 [Firebird-net-provider] [FB-Tr Does anyone know of a why to hide those tags short of editing the source? It now looks like this: 28.06.11 14:08+0200 Alexander Muyla 21 Console app for failing events 29.06.11 01:56-0700 ven ~ 6 fbdataadapter update 'dataType 30.06.11 19:40+ Nataniel (JIRA) 98 (DNET-386) Timeout exceeded or I've since edited the source, and I find this a much more compete solution. There are two patches and some muttrc configuration: https://bitbucket.org/dgc/mutt-dgc/raw/tip/replacelist https://bitbucket.org/dgc/mutt-dgc/raw/tip/subjectrx Applied against current trunk from Mercurial, together with trash folder patch; some fuzz, but no conflicts. Works as advertised, see above. The configuration is straightforward if you know regular expressions: subjectrx '\[Firebird-net-provider\] *' '%L%R' subjectrx '\[FB-Tracker\] Created: *' '%L%R' Thanks, David! Michael
Re: allow_ansi set, but I only get the first character highlighted
lilydjwg schrieb am 11.04.2012 um 19:40 (+0800): I'm using elinks to view those HTML emails. ~/.mailcap contains: text/html; muttHtml; copiousoutput Not answering your questions, but as you appear to like Python: https://bitbucket.org/blacktrash/muttils This allows you to have FF or IE or display your mail. -- Michael Ludwig
Hide [bracketed topic indicators] such as prepended by mailing lists
Some mailing list software prepends a [tag] to every subject line of every message. I realize people may find this practical; see this thread for an example: 07.03.12 16:31+0100 Marco Paolone 35 Mailing list and subject prefix 07.03.12 15:40+ Chris Green 12 ├─ 07.03.12 09:21-0800 Gary Johnson 13 ├─ 08.03.12 09:27+0100 Remco Rijnders49 ├─ 11.03.12 14:07+0100 Marco Paolone 20 └─ On the other hand, you may also find it impractical with an index view such as above when on an 80 column terminal when the tag is a bit longer, like here: 28.06.11 14:08+0200 Alexander Muyla 21 [Firebird-net-provider] Consol 29.06.11 01:56-0700 ven ~ 6 [Firebird-net-provider] fbdata 30.06.11 19:40+ Nataniel (JIRA) 98 [Firebird-net-provider] [FB-Tr Does anyone know of a why to hide those tags short of editing the source? -- Michael Ludwig
Re: Hide [bracketed topic indicators] such as prepended by mailing lists
Michael Ludwig schrieb am 11.04.2012 um 00:16 (+0200): Some mailing list software prepends a [tag] to every subject line of every message. I realize people may find this practical; see this thread for an example: 07.03.12 16:31+0100 Marco Paolone 35 Mailing list and subject prefix 07.03.12 15:40+ Chris Green 12 ├─ I meant to include this doc pointer, just for reference: http://durak.org/sean/pubs/software/mutt/reference.html#index-format %ssubject of the message -- Michael Ludwig
Re: regexp and pattern limit
steve schrieb am 02.04.2012 um 22:01 (+0200): I'm trying to write a regexp in order to capture some words to put them in color. I have a line like this in my .muttrc: color body red default \etch\|((L|l)enny)|((S|s)queeze)|((S|s)arge)|((P|p)otato) I want to catch only etch, but not fetch nor fetchera (or whatever combination). So I tried the \word\ syntax without success. I also tried the Perl way \bword\b which fails too. So you want word boundaries. I found out double backslashes work fine: color body red default \\etch While hacking away at the regex in the conf file and testing in mutt reloading the conf, it's easy to get fooled by the cumulative effect of all regexes tried along the road … so it's important to make tabula rasa for your combination by doing: :uncolor body red default * Michael
Define colors like with variable?
Using the color command, you can tell mutt how to dress. Let's say you have quite a lot of those color commands in your configuration, preferably in a separate ~/.mutt/colors file. Is there a way to tell mutt in the configuration that the color default is to appear as black? Note that default is bound, at least by default, to the background color of your terminal. I changed that terminal background color, but now my mutt colors aren't to my liking any more, which prompted me to think about the best way to configure colors. It would be convenient if I could have a layer of indirection and define default to be black in the mutt configuration. If not, in order to be flexible and switch color schemes without global search and replace, I could make the color file a template containing placeholders like [% default %] or [% hilite %] or [% error %], thus obtaining a layer of indirection, and process it using my color definitions du jour to achieve the desired result. Michael
IMAP/fetchmail setup: preserving READ/NEW status?
I read my mail via IMAP. From various computers. Every so often I run fetchmail on one computer to download all mail and remove it from the remote servers. I then don't have the full story on the server, but that's perfectly fine. There's one annyoing bit about this setup. Mail that I've read via IMAP is flagged as new when downloaded to my computer. I would prefer to have only new mail flagged as new. In practice, my workaround is to make sure I've read all mail before on the server before running fetchmail; and then mark everything as read when downloaded. But an annoying inner voice tells me that this is not a satisfactory solution. Who's to blame? Mutt for not properly flagging mail as read via IMAP? Me for not configuring it to do so? Fetchmail for not honoring the IMAP status bits (whatever they are) when downloading mail? Me, again, for not configuring it to do so? Or simply the Internet gods for not having made the behaviour I want attainable? Or, again, me for desiring the impossible? Michael
Re: Local alternative to Re:
Ave Salve! Salve Håkedal schrieb am 01.12.2011 um 22:59 (+0100): /usr/share/doc/mutt/manual.txt.gz (Debian): 3.210. reply_regexp Type: regular expression Default: “^(re([\[0-9\]+])*|aw):[ \t]*” A regular expression used to recognize reply messages when threading and replying. The default value corresponds to the English Re: and the German Aw:. So it seems German is accepted by some people! Close to 100 million :) -- Michael Ludwig
Re: Can't figure out how to set locale/charset stuff
Grant Edwards schrieb am 17.05.2011 um 16:40 (+): On 2011-05-17, Grant Edwards grant.b.edwa...@gmail.com wrote: It's been years since mutt displayed more than a small fraction of my incoming mail correctly. I've tried setting LC_CTYPE and LANG according to http://wiki.mutt.org/?MuttFaq/Charset, but no matter what I choose, there's always a large percentage of mails that won't display properly. Here are my settings: # set locale= de_DE@euro# aus Umgebung set charset = utf-8 set send_charset= us-ascii:iso-8859-1:utf-8 charset-hook us-ascii iso-8859-1 charset-hook ^unknown-8bit$ windows-1252 charset-hook ^x-user-defined$ windows-1252 charset-hook ^iso-8859-1$ windows-1252 charset-hook ^us-ascii$ windows-1252 The locale doesn't appear to work on Cygwin, but never mind. http://wiki.mutt.org/?MuttFaq/Charset delimiter (e.g. =8C.=B9) I see this: delimiter (e.g. \214.¹) I'm using urxvt as my terminal, and the touch/ls test with a non-ascii filename suggested by http://wiki.mutt.org/?MuttFaq/Charset works fine. I'm using MinTTY, which is just great. And my Mutt is linked against ncursesw, Although mutt -v will claim mutt is compiled with just ncurses (which might be true, after all), ldd reveals the true linkage occurring: cygncursesw-10.dll = /usr/bin/cygncursesw-10.dll (0x6ed1) Read this thread: http://cygwin.com/ml/cygwin/2010-06/msg00173.html Andy Koppe, the MinTTY developer, said this: […] vim works fine with UTF-8 already. […] Mutt and also nano do need rebuilding with ncursesw though. -- Michael Ludwig
Re: Viewing HTML mails with images
Christian Ebert schrieb am 02.04.2011 um 14:11 (+0100): * Leonardo M. Ramé on Friday, April 01, 2011 at 17:40:08 -0300 Hi, when I receive HTML mails, I can see all its files in the attachments view, that is, the html itself, and all of its images. When I select the main html file, the default web browser is opened and I can see the html file alone, the images are not loaded. How can I let Mutt force showing the images? If you're not afraid of Python you can try out viewhtmlmsg from my muttils package: https://bitbucket.org/blacktrash/muttils/ What would I have to do to get this to work on Windows/Cygwin? By which I mean launching Windows FF, IE or chrome from Mutt in Cygwin? -- Michael Ludwig
Re: Viewing HTML mails with images
Michael Ludwig schrieb am 10.04.2011 um 22:46 (+0200): Christian Ebert schrieb am 02.04.2011 um 14:11 (+0100): * Leonardo M. Ramé on Friday, April 01, 2011 at 17:40:08 -0300 How can I let Mutt force showing the images? If you're not afraid of Python you can try out viewhtmlmsg from my muttils package: https://bitbucket.org/blacktrash/muttils/ What would I have to do to get this to work on Windows/Cygwin? By which I mean launching Windows FF, IE or chrome from Mutt in Cygwin? Okay, I've set the BROWSER environment variable correctly, that is one step in the right direction. export BROWSER=/cygdrive/c/Programme/Mozilla Firefox/firefox.exe Now the script launches the message into a new tab in FF when it is running. Alas, the message arrives completely empty. The URL in the URL bar is something like: file:///cygdrive/c/DOKUME~1/michael/LOKALE~1/Temp/viewhtmlmsg.NZxhlF/index.html That is the tempdir configured in Cygwin: TEMP=/cygdrive/c/DOKUME~1/michael/LOKALE~1/Temp TMP=/cygdrive/c/DOKUME~1/michael/LOKALE~1/Temp That Cygwin path is wrong for a Windows app. And if you look into %UserProfile\lokale~1\temp, there are no files created by your script. I can change TMP and TEMP to /tmp and files aren't showing up there either. Ah, using -k0 the temp files aren't deleted. Now the path remains to be fixed. It should be something like: file:///T:/Cygwin/tmp/viewhtmlmsg.94tExP/index.html Looks like I'd have to modify viewhtmlmsg (which runs in Cygwin, just like Mutt) to use the Cygwin path notation to pass the path in Windows notation to Windows apps. -- Michael Ludwig
Re: Viewing HTML mails with images
Michael Ludwig schrieb am 10.04.2011 um 23:07 (+0200): Looks like I'd have to modify viewhtmlmsg (which runs in Cygwin, just like Mutt) to use the Cygwin path notation to pass the path in Windows notation to Windows apps. Had a look at the source: /usr/lib/python2.6/site-packages/muttils/viewhtmlmsg.py /usr/lib/python2.6/site-packages/muttils/viewhtmlmsgcommand.py But I can't figure this out. 66 fp = open(htmlfile, 'wb') 67 fp.write(html) 68 fp.close() 69 self.items = [htmlfile] 70 self.urlvisit() 71 if self.keep: 72 time.sleep(self.keep) Looks like self.urlvisit() launches the browser? Probably involving the pybrowser module? Enough research for tonight ... -- Michael Ludwig
Re: Improve sorting rule?
Yue Wu schrieb am 16.11.2010 um 15:06 (+0800): Do you use vim? vim's widemode option is in the form that I've described just above. I can't find any Vim option by that name in either my Vim online manual - VIM 7.3 (2010 Aug 15, compiled Aug 19 2010 13:06:02) - nor in Google. Maybe you misspelt the option name? -- Michael Ludwig
Re: Up to date version of trash patch?
Zeerak Mustafa Waseem schrieb am 16.09.2010 um 07:11 (+0200): On Wed, Sep 15, 2010 at 11:29:56PM +, seanh wrote: Is there an up-to-date version of the trash folder patch, one that is known to work with mutt 1.5.20/21? There was another thread mentioning it a month or so back. Have a look at it. Sorry I can't be of more help as I don't remember the subject. Probably the thread starting here: Deleting messages trash-can-style - Michael Ludwig - 22.08.10 18:51+0200 http://www.mail-archive.com/mutt-users@mutt.org/msg41666.html -- Michael Ludwig
Re: Deleting messages trash-can-style
On Sunday, 22 August 2010, 18:51:31 +0200, Michael Ludwig mil...@gmx.de wrote: Can I configure Mutt to save deleted messages to another folder or mbox (as GUI mail clients do) instead of simply deleting it? What about the trash variable? Type: path Default: “” If set, this variable specifies the path of the trash folder where the mails marked for deletion will be moved, instead of being irremediably purged. NOTE: When you delete a message in the trash folder, it is really deleted, so that you have a way to clean the trash. Thanks. This variable is mentioned here: http://manpages.ubuntu.com/manpages/karmic/man5/muttrc.5.html But not here: http://www.mutt.org/doc/devel/manual.html#variables And my Mutt [version 1.5.20 (2009-12-10)] doesn't like this variable: trash: Unbekannte Variable. = unknown variable -- Michael Ludwig
Re: Deleting messages trash-can-style
Hi Ed, ed schrieb am 22.08.2010 um 18:10 (+0100): On Sun, Aug 22, 2010 at 06:51:31PM +0200, Michael Ludwig wrote: Can I configure Mutt to save deleted messages to another folder or mbox (as GUI mail clients do) instead of simply deleting it? I thought that was the default behaviour? I did not have a macro for d; I think the key is by default mapped to delete-message, which implements its mission the not-kidding way. If not, you might want to look at doing this: macro index d save-message=.Trash\n macro pager d save-message=.Trash\n That should work, but you'll want to change .Trash to something else, That works great, thanks! I think what save-message does is a combo of copy-message and delete-message. Exactly what I want. I'm using Maildir style (which I found more efficient with header caching). I'm sure it is. Good old mbox still good enough for me, although sometimes I have to wait more than five seconds for large mboxes. -- Michael Ludwig
Re: mutt 1.5.20 problem changing mailboxes
Gregor Zattler schrieb am 06.07.2010 um 10:22 (+0200): c^a^k\t\t does it (change-folder, beginning-of-line, kill-to-end-of-line, tab, tab). You save one keystroke by doing ^u (kill to beginning of line) instead of ^a^k. -- Michael Ludwig
Re: Can't set alternates
Nicolas Sebrecht schrieb am 02.07.2010 um 09:26 (+0200): I've added this line in my muttrc file set alternates=...@email.address but got alternates : unknown variable (translated message) with mutt v1.5.18. Moving from set alternates = ^(...|...|...)$ to a series of alternates ... commands is one of two things I had to change when upgrading Mutt/Cygwin from 1.4.2 (2006) to 1.5.20 (2009). The other one was set check_mbox_size = yes. -- Michael Ludwig
Re: What-key Example
rog...@sdf.org schrieb am 28.06.2010 um 08:19 (-0800): quit which ^g Probably quit with ^g. I would presume this is the (secret) escape key for the what-key loop? I didn't know the what-key command either, but ^g also aborts e.g. Bash or Vim or Mutt command line editing, knowing which you'd presume it would work here, too. -- Michael Ludwig
Re: Add header automatically
Eric Smith schrieb am 26.06.2010 um 21:09 (+0200): Michael Ludwig said: Eric Smith schrieb am 25.06.2010 um 08:11 (+0200): Is it possible to configure mutt to place an extra header in the edit buffer each time you go into edit mode? I want the line `attach:' Yes, it is possible: add the header with a non-empty value and it'll be present in the edit buffer, no need to unignore it: my_hdr Attach: ~/empty.txt set edit_headers = yes Thanks Michael, yes that works. But effect is to send that null file each time that you do not actually want to attach a file, in which case you would edit that header and remove the placeholder filename. Or hit D to delete the attachment from the attachment list after having finished editing the message. But IIRC, an empty attachment will be stripped anyway. -- Michael Ludwig
Re: Add header automatically
Eric Smith schrieb am 25.06.2010 um 08:11 (+0200): Is it possible to configure mutt to place an extra header in the edit buffer each time you go into edit mode? I want the line `attach:' Yes, it is possible: add the header with a non-empty value and it'll be present in the edit buffer, no need to unignore it: my_hdr Attach: ~/empty.txt set edit_headers = yes Then it is easier to paste in filenames or if you paste nothing it is ignored. (When I use vim, I have a nice binding for this but not with nano - which for some reason I am using more and more). Can only be minimalism ;-) -- Michael Ludwig
Re: folder-hook doesn't work anymore with gmail
Marco Giusti schrieb am 25.06.2010 um 08:50 (+0200): i'm using debian testing's package[1] and before debian stable, maybe in the upgrade something changed. There is a slight version change: http://packages.debian.org/lenny/mutt - stable - mutt (1.5.18-6) http://packages.debian.org/squeeze/mutt - testing - mutt (1.5.20-9) -- Michael Ludwig
Re: Two alternative proposed fixes [Was: Re: A wish for the mailboxes command]
Erik Christiansen schrieb am 25.06.2010 um 20:48 (+1000): While that would be a lot of fun, mutt itself does seem able to be cured of its current fibbing behaviour. (Try copying this message to this mail folder. Mutt says New mail in this mailbox. What hokum.) Confirmed :-) Mutt needs to check the size and/or atime of the destination folder _before_ it writes, rather than cookily doing it _after_. Then the erroneous and misleading immediate message would go away. To fix the problem of mutt adding the transfer recipient folder to its list of New folders on its next scan, another small bugfix is also required. Once the recipient file has been written, mutt needs to update its current values for file size and atime, so that the Newness reference will be correct. Would that not put an end to its fibbing ways? Sounds like it would! One more example, I have the following setting to store mail conversations as threads: set spoolfile = +Neu # c! set record = +Neu # c So when I send a message that is not going to a list, it goes to +Neu, and I'm notified of a new message in +Neu, which is technically correct, but as I put it there myself I don't need to be told about it. Checking for new mail before a user-triggered write operation, as you suggested, would, I think, fix the issue. -- Michael Ludwig
Re: Message save causes erroneous New mail detection.
Erik Christiansen schrieb am 24.06.2010 um 19:18 (+1000): Since upgrading to ubuntu 10.04, and therefore Mutt 1.5.20, saving a read mail to another mailbox immediately causes that mailbox to be flagged as containing new mail. Since I'm using the same .muttrc, something has changed between mutt versions, to cause the erroneous behaviour. (Prior mutt version was from 3 years ago, or so.) Does anyone know of a fix for this problem? You could give the following line a try, which has helped me with a similar (if not actually the same) problem: set check_mbox_size=yes -- Michael Ludwig
Re: Detecting new mail and read mail in 1.4 and 1.5
Michael Ludwig schrieb am 23.06.2010 um 14:23 (+0200): Christian Ebert schrieb am 22.06.2010 um 23:16 (+0200): * Michael Ludwig on Tuesday, June 22, 2010 at 22:27:06 +0200 How can new mail detection be repaired for 1.5? I'm using Maildir, but set check_mbox_size=yes I presume the underlying issue is that atime (access time) is turned off or otherwise unavailable on some filesystems, so Mutt cannot use it to detect new mail in a box. Is that correct? Yes, appears to be correct: http://wiki.mutt.org/?MuttFaq/Folder Why are new flags of mbox folders wrong in folder-list view? Bottom line: * $check_mbox_size option for mutt 1.5.15 or later * --enable-buffy-size option to configure for mutt 1.5.15 -- Michael Ludwig
Re: Detecting new mail and read mail in 1.4 and 1.5
Chris G schrieb am 23.06.2010 um 13:11 (+0100): On Wed, Jun 23, 2010 at 11:22:53AM +0200, Christian Ebert wrote: Maildir vs. mbox: I found that Maildir with header_cache is way faster than mbox in opening large mailboxes, even though I'm on a Mac where HFS+ is supposedly not good at handling a lot of small files. YMMV. Why is mbox slow at reading large mailboxes though, it doesn't make much sense as it's only got to open one file as opposed to maildir opening at least one file per message. To display the index with maildir, Mutt has to read the header_cache; to do so with mbox, Mutt has to read the whole file. That's why. , thinks, I *believe* my problem with mutt not seeing new incoming mail is because of my delivery mechanism. I use a custom python script to deliver my mail to multiple mailboxes (split basically by mailing lists) and it's that which doesn't play nicely with mutt for some reason. I use procmail, and Mutt doesn't care which procedure is used. What Mutt cares is about is the atime or size of the mbox. Try applying the setting Christian suggested, it works perfectly for me. -- Michael Ludwig
Re: Detecting new mail and read mail in 1.4 and 1.5
Christian Ebert schrieb am 22.06.2010 um 23:16 (+0200): * Michael Ludwig on Tuesday, June 22, 2010 at 22:27:06 +0200 How can new mail detection be repaired for 1.5? I'm using Maildir, but set check_mbox_size=yes I presume the underlying issue is that atime (access time) is turned off or otherwise unavailable on some filesystems, so Mutt cannot use it to detect new mail in a box. Is that correct? -- Michael Ludwig
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: Pick sendmail command based on sender address
Michael Tatge schrieb am 22.06.2010 um 23:19 (+0200): * On Mon, Jun 21, 2010 04:27PM +0200 Michael Ludwig (mil...@gmx.de) muttered: I send mail using ssmtp (a simple standalone SMTP library) and one of the SMTP servers for the different freemail addresses I have. I'd recommend switching to esmtp. You don't have to mess with send-hooks because it supports using the correct server based on the envelope (identities) See http://wiki.mutt.org/?LightSMTPagents/Esmtp where I described the config in detail. Thanks. I've switched to msmtp, which can also parse the envelope to figure out the SMTP server to use. But it's not even needed now as Mutt passes the sender address to msmtp and so has it select the correct account. -- Michael Ludwig
Re: Detecting new mail and read mail in 1.4 and 1.5
Christian Ebert schrieb am 22.06.2010 um 23:16 (+0200): * Michael Ludwig on Tuesday, June 22, 2010 at 22:27:06 +0200 Is that also the cause of the now dysfunctional new mail detection in 1.5, broken at least in my configuration and on Cygwin? How can new mail detection be repaired for 1.5? I'm using Maildir, but set check_mbox_size=yes looks like a good candidate. Indeed. It is unknown as of 1.4,2, but solves the issue in 1.5.20. -- Michael Ludwig
Pick sendmail command based on sender address
I send mail using ssmtp (a simple standalone SMTP library) and one of the SMTP servers for the different freemail addresses I have. When receiving an email to ad...@gmx.de, I'd like to reply using that as the From line, and also the corresponding SMTP account, of course. Same thing for ad...@gmx.de, ad...@googlemail.com and so on. set from = ad...@gmx.de # main address set alternates = ^(ad...@gmx.de|ad...@gmx.de|ad...@googlemail.com)$ set use_from = yes # generate From: header set reverse_name = yes # use alternates when replying This seems to set my sender address as desired. But in order for the mail to get accepted by the SMTP server, I have to select matching SMTP server settings (addr1 account for addr1 etc), and I can't seem to figure out how to change the sendmail command based on the sender address. A send-hook, for instance, is for Chang[ing] settings based upon message recipients, which is fine, but not what I beed in this case. Is the best option to write a shell or Perl script to parse the mail, determine the appropriate SMTP server from the From line (first line of the mail), and then to exec ssmtp with the appropriate arguments or configuration file? -- Michael Ludwig
Re: Pick sendmail command based on sender address
Alek Rollyson schrieb am 21.06.2010 um 10:47 (-0400): I'm not sure exactly what version it was introduced, but I use reply-hook to source different profiles to do what you're describing. The earliest version I have used is 1.5.18, but it appears you are on 1.4.2 so I cannot say for sure whether that will work or not for you. I am, and doesn't seem to work as I get errors in my config indicated on startup after adding the following lines: reply-hook . 'unmy_hdr from' reply-hook '~t ad...@gmx.de' 'my_hdr From: No 2 ad...@gmx.de' reply-hook '~t ad...@gmx.de' 'set sendmail = /usr/sbin/ssmtp -v -C /home/michael/.ssmtp/addr2.gmx.de.conf' So it seems to be a 1.5 feature. Has anyone managed to compile Mutt 1.5 on Cygwin 1.7? -- Michael Ludwig
Re: Pick sendmail command based on sender address
Christian Ebert schrieb am 21.06.2010 um 16:50 (+0200): * Michael Ludwig on Monday, June 21, 2010 at 16:27:52 +0200 When receiving an email to ad...@gmx.de, I'd like to reply using that as the From line, and also the corresponding SMTP account, of course. Same thing for ad...@gmx.de, ad...@googlemail.com and so on. Use a message-hook? Sounds like this is to be used to execute arbitrary configuration commands before viewing or formatting a message. http://www.mutt.org/doc/manual/manual-3.html#message-hook Is the best option to write a shell or Perl script to parse the mail, determine the appropriate SMTP server from the From line (first line of the mail), and then to exec ssmtp with the appropriate arguments or configuration file? Might be easier to switch to msmtp which provides this functionality - Thanks - looking into it. or postfix in case it already supports relaymaps. I don't want a full mail server. -- Michael Ludwig
Re: Pick sendmail command based on sender address
Michael Ludwig schrieb am 21.06.2010 um 17:27 (+0200): Christian Ebert schrieb am 21.06.2010 um 16:50 (+0200): * Michael Ludwig on Monday, June 21, 2010 at 16:27:52 +0200 Is the best option to write a shell or Perl script to parse the mail, determine the appropriate SMTP server from the From line (first line of the mail), and then to exec ssmtp with the appropriate arguments or configuration file? Might be easier to switch to msmtp which provides this functionality Thanks - looking into it. The msmtp utility appears to do what I want in combination with Mutt 1.4 and the following configuration: set from= ad...@gmx.de# main address set reverse_name= yes # use alternates set use_from= yes # generate From: header set envelope_from = yes # don't know if relevant here Thanks for pointing me at msmtp, very useful! -- Michael Ludwig
Re: Pick sendmail command based on sender address
Michael Ludwig schrieb am 21.06.2010 um 17:20 (+0200): So it seems to be a 1.5 feature. Has anyone managed to compile Mutt 1.5 on Cygwin 1.7? Mutt 1.5 (mutt-20100621.tar.gz) builds and starts without problems on Cygwin 1.7, at least using the following configuration: ./configure --prefix=/usr/local/mutt15 --with-regex But what happened to --enable-buffy-size ? This is needed in 1.4 (so it seems, at least) to make mutt remember having read new mail in a box so it isn't flagged as new any more. And the same seems to hold true for 1.5, but the flag is no longer available. -- Michael Ludwig
Re: Colors, mutt, termcap/terminfo
[Re: Colors, mutt, termcap/terminfo] rog...@sdf.org schrieb am 09.06.2010 um 00:01 (-0800): On Tue, Jun 08, 2010 at 05:17:06PM -0700, Chip Camden wrote: I finally got 256 colors working with mutt and zsh on FreeBSD. Even though both of Look for the 256colors2.pl perl color test script. It will help you verify 256 colors is *really* working. http://code.google.com/p/joeldotfiles/source/browse/trunk/256colors2.pl Fantastic! Works great on rxvt and MinTTY on Cygwin. I didn't know the terminal could be so colorful, used to think it was limited to 256 colors. -- Michael Ludwig
Re: Wrapping on internal pager
Camaleón schrieb am 11.04.2010 um 13:22:52 (+): On Sun, 11 Apr 2010 09:11:21 -0400, Patrick Shanahan wrote: in ~/.muttrc unset markers note that proper syntax may be: set markers=no That just removes the + (plus) mark, but the text wrapping is still badly formatted (it breaks before reaching the end of the line) :-( What does the following command display? :set ?wrapmargin A setting of wrapmargin=2 tells the pager to leave two spaces before the end of the terminal. -- Michael Ludwig
Re: Wrapping on internal pager
Camaleón schrieb am 11.04.2010 um 14:14:34 (+): I tested with: *** set smart_wrap set wrapmargin = 2 *** And also: *** set wrapmargin = 2 *** But still get broken lines at the middle of the text. Then the text has line breaks in the middle. Mutt can't know that you want that text to be reflowed. It could be program text or something else that should be kept as it is. If you use Vim as your editor, the gq command is handy to reformat text to your likings (as per the textwidth and other settings). -- Michael Ludwig
Re: Wrapping on internal pager
Camaleón schrieb am 11.04.2010 um 14:53:51 (+): On Sun, 11 Apr 2010 16:38:02 +0200, Michael Ludwig wrote: Then the text has line breaks in the middle. The funny thing is that not. I also thought that something in the code could be the culprit of this mess but reviewing the code of the e-mail I see nothing strange on it. Then I don't know. If you use Vim as your editor, the gq command is handy to reformat text to your likings (as per the textwidth and other settings). I'm not familiar with vim, have to carefully try with that option. It's a programmer's editor, it's very powerful, but it takes some getting used to. But, how the viewer can mix/interact with the pager? Is that possible? I thought they were two separate settings (one for editing new messages and one for displaying messages) :-? Correct, they're two things: pager (ov viewer, same thing), and editor. I imagined all you might want to achieve is reformatting the text of the message your replying to, which is what you can do using the gq command in Vim. Sorry for the distraction. Or you mean I can setup the pager to use Vim as internal source? No. Maybe you can, but I wouldn't do that. Mutt's pager is just fine. -- Michael Ludwig
Re: Wrapping on internal pager
Camaleón schrieb am 11.04.2010 um 18:17:24 (+): Nothing! The e-mail is clean. Just a bunch of text words, nothing in between, no rare characters. So all is well. - Image sample of failing e-mail (it will be auto-deleted in 7 days): http://picpaste.com/20100411_mutt_pager_wrapping.png - Raw code sample of failing e-mail (it will be auto-deleted in 1 day): http://pastebin.com/4t4kPSrh Can't see any problem here. -- Michael Ludwig
Quote headers of incoming message when replying?
Mutt allows you to edit the headers of the mail you're composing through setting edit_headers = yes. Is there a way to have Mutt copy the headers of the incoming message (ideally, just a selection) along with the body to your editor so you can quote them in your reply, like in the following example? http://markmail.org/message/vkqs2bvt7ovzhnnt -- Michael Ludwig
Re: Quote headers of incoming message when replying?
Andreas Kneib schrieb am 07.04.2010 um 21:41:20 (+0200) [Re: Quote headers of incoming message when replying?]: * Michael Ludwig schrieb am Mittwoch, den 07. April 2010: Is there a way to have Mutt copy the headers of the incoming message (ideally, just a selection) along with the body to your editor so you can quote them in your reply, like in the following example? http://markmail.org/message/vkqs2bvt7ovzhnnt Like Outlook-Express? ;-) Maybe a bit ;-) set attribution=- Original Message -\n\From: %n %a\n\%t\n\Sent: %d\n\Subject: %s Thanks - I already had %n and %d, but didn't know about the other ones. -- Michael Ludwig
Re: Quote headers of incoming message when replying?
Gary Johnson schrieb am 07.04.2010 um 15:33:28 (-0700) Date: Wed, 7 Apr 2010 15:33:28 -0700 From: Gary Johnson gar...@spocom.com To: Mutt Users mutt-users@mutt.org Subject: Re: Quote headers of incoming message when replying? On 2010-04-07, Michael Ludwig mil...@gmx.de wrote: Mutt allows you to edit the headers of the mail you're composing through setting edit_headers = yes. Is there a way to have Mutt copy the headers of the incoming message (ideally, just a selection) along with the body to your editor so you can quote them in your reply, like in the following example? http://markmail.org/message/vkqs2bvt7ovzhnnt You can include the weeded headers by executing :set header Great - as you can see, it works! before replying to the message. If you want all headers to be included, also execute :unset weed Perfect, thanks! -- Michael Ludwig
