[no subject]
This message wraps the original message. The sending domain has a DMARC p=reject policy, which unfortunately can cause bounces. See http://www.mutt.org/mail-lists.html#dmarc To remove this message, please change the domain policy to p=none or p=quarantine.--- Begin Message --- Thanks, this works for me! Thanks also to Remco. On Saturday, October 24, 2020, 12:24:15 PM CDT, Felix Finch wrote: On 20201024, Globe Trotter via Mutt-users wrote: > >An irritating thing right now is that if I hit q in error after composing a >message, I get: Postpone message (yes/no) and if I say no, then the message >appears lost. Is is possible to have an an option on this which should be to >cancel the postpone question: perhaps a prompt that is [yes/no/cancel] Try ^G. I just tried it on this message and it does cancel the quit. You do have to type "e" to get back to editing. Or go ahead and postpone, then type "m" to send a new message. This notices the draft and asks if you want to work on that. -- ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._. Felix Finch: scarecrow repairman & wood chipper / fe...@crowfix.com GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933 I've found a solution to Fermat's Last Theorem but I see I've run out of room o --- End Message ---
[no subject]
This message wraps the original message. The sending domain has a DMARC p=reject policy, which unfortunately can cause bounces. See http://www.mutt.org/mail-lists.html#dmarc To remove this message, please change the domain policy to p=none or p=quarantine.--- Begin Message --- > On Saturday, October 24, 2020, 11:33:57 AM CDT, Remco Rijnders wrote: > I got that mixed up indeed, apologies! The manual does mention it, but > perhaps not in the easiest searchable way: > 3.347. sort_aux > (...)> You can also specify the “last-” prefix in addition to the “reverse-” > prefix, but “last-” must come after “reverse-”. The “last-” prefix causes > messages to be sorted against its siblings by which has the last descendant, > using the rest of $sort_aux as an ordering. Oh, thanks very much for this additional information. This is very helpful!! --- End Message ---
[no subject]
This message wraps the original message. The sending domain has a DMARC p=reject policy, which unfortunately can cause bounces. See http://www.mutt.org/mail-lists.html#dmarc To remove this message, please change the domain policy to p=none or p=quarantine.--- Begin Message --- Hi, An irritating thing right now is that if I hit q in error after composing a message, I get: Postpone message (yes/no) and if I say no, then the message appears lost. Is is possible to have an an option on this which should be to cancel the postpone question: perhaps a prompt that is [yes/no/cancel] Thanks! --- End Message ---
[no subject]
This message wraps the original message. The sending domain has a DMARC p=reject policy, which unfortunately can cause bounces. See http://www.mutt.org/mail-lists.html#dmarc To remove this message, please change the domain policy to p=none or p=quarantine.--- Begin Message --- On Saturday, October 24, 2020, 11:07:41 AM CDT, Remco Rijnders wrote: On Sat, Oct 24, 2020 at 03:09:06PM +, Globe wrote in : > >Looking at: http://www.mutt.org/doc/manual/manual.html#sort, it seems to me >that I should simply > >set sort=threads >set sort_aux=reverse-date-received > >However, what I get is the threads, correctly, but the ones with most recent >messages do not come up first. I want the threads with most recent activity >coming up first. Can this be done in mutt? (I do not want reverse_threads.) > Try changing the sort_aux to: > set sort_aux=last-reverse-date-received > Does that what you want? Without "last" it looks at the date of the first > message in the thread, with it, it uses the last one of all the messages. Thanks! For me, and also from the manual, I don't find this method: Error in /home/gt/.muttrc, line 187: reverse-date-received: unknown sorting method Perhaps, you meant: set sort_aux=reverse-last-date-received which I tried as a guess, even though it does not seem to be in the manual but does not give an error and seems to work. Thanks!! --- End Message ---
[no subject]
This message wraps the original message. The sending domain has a DMARC p=reject policy, which unfortunately can cause bounces. See http://www.mutt.org/mail-lists.html#dmarc To remove this message, please change the domain policy to p=none or p=quarantine.--- Begin Message --- Hi, Looking at: http://www.mutt.org/doc/manual/manual.html#sort, it seems to me that I should simply set sort=threads set sort_aux=reverse-date-received However, what I get is the threads, correctly, but the ones with most recent messages do not come up first. I want the threads with most recent activity coming up first. Can this be done in mutt? (I do not want reverse_threads.) Sorry if my question is unclear. Thanks, GT --- End Message ---
[no subject]
This message wraps the original message. The sending domain has a DMARC p=reject policy, which unfortunately can cause bounces. See http://www.mutt.org/mail-lists.html#dmarc To remove this message, please change the domain policy to p=none or p=quarantine.--- Begin Message --- On Friday, October 23, 2020, 10:38:00 AM CDT, Remco Rijnders wrote: >> I want to set bcc to my address for every e-mail I send from an account. How >> do I do that? Do I define a hook? > You could use a hook for it, but it might be simpler to use the record > functionality. See http://www.mutt.org/doc/manual/#record for how to > automatically save a copy of every outgoing message to a folder of your > choice. Thank you for this.I also set Bcc because it gives me an indication that the message actually went out/through. How do I specify this hook? Thank you again! GT --- End Message ---
[no subject]
This message wraps the original message. The sending domain has a DMARC p=reject policy, which unfortunately can cause bounces. See http://www.mutt.org/mail-lists.html#dmarc To remove this message, please change the domain policy to p=none or p=quarantine.--- Begin Message --- On Friday, October 23, 2020, 9:33:13 AM CDT, Remco Rijnders wrote: > Hi Globe, > Please see http://www.mutt.org/doc/manual/#sidebar-sort-method for a list of > options for sorting your sidebar. It probably is a good idea to refer to this > official mutt manual in general for supported options as some of the "how > to"'s and tricks you can find on the internet might be outdated. I hope this > helps! > Kind regards, Remco, Thanks very much! This is very helpful. Best regards, GT --- End Message ---
[no subject]
This message wraps the original message. The sending domain has a DMARC p=reject policy, which unfortunately can cause bounces. See http://www.mutt.org/mail-lists.html#dmarc To remove this message, please change the domain policy to p=none or p=quarantine.--- Begin Message --- Hi, I want to set bcc to my address for every e-mail I send from an account. How do I do that? Do I define a hook? Thanks! --- End Message ---
[no subject]
This message wraps the original message. The sending domain has a DMARC p=reject policy, which unfortunately can cause bounces. See http://www.mutt.org/mail-lists.html#dmarc To remove this message, please change the domain policy to p=none or p=quarantine.--- Begin Message --- Hi, New to mutt but I put the following in my .muttrc file, as per examples online: set sort_sidebar = desc However, when I start mutt, I get: Error in /home/gt/.muttrc, line 217: sort_sidebar: unknown variable source: errors in /home/gt/.muttrc Press any key to continue... Is sort_sidebar deprecated in mutt? Thanks, GT --- End Message ---
[no subject]
This message wraps the original message. The sending domain has a DMARC p=reject policy, which unfortunately can cause bounces. See http://www.mutt.org/mail-lists.html#dmarc To remove this message, please change the domain policy to p=none or p=quarantine.--- Begin Message --- Hi, New to mutt but I put the following in my .muttrc file: set sort_sidebar = desc However, when I start mutt, I get: Error in /home/gt/.muttrc, line 217: sort_sidebar: unknown variable source: errors in /home/gt/.muttrc Press any key to continue... Is sort_sidebar deprecated in mutt? Thanks, GT --- End Message ---
[no subject]
This message wraps the original message. The sending domain has a DMARC p=reject policy, which unfortunately can cause bounces. See http://www.mutt.org/mail-lists.html#dmarc To remove this message, please change the domain policy to p=none or p=quarantine.--- Begin Message --- My aoologies for the earlier attempts at sending e-mail. But I am new to mutt (as of today) and do not have my mailer set up and trying to get started. I hope this goes through in plain-text format. My set up is as follows: I use fetchmail and procmail to get my mail delivered to Maildir mailboxes. So,my mail is inside folders in ~/Maildir in the following manner: ~/Maildir/inbox ~/Maildir/sent ~/Maildir/drafts ~/Maildir/work/ ~/Maildir/work/user1 ~/Maildir/work/user2 ~/Maildir/bills ~/Maildir/family etc. I want to show this tree on a side-pane. So, my initial attempt at .muttrc has the following: modified from mutt & Maildir Mini-HOWTO set mbox_type=Maildir set folder="~/Maildir" mailboxes `echo -n "+ "; find ~/Maildir -type d -name "*" -printf "+'%f' "` However, when I launch mutt, I get nothing and after a lot of blank stares on-screen, I get: Mutt:/var/spool/mail/itsme [Msgs: 0 Inc: 20](date/date)(all)-- I was wondering if I could get some advice and help on how to do this. I plan on sending mail through postfix (localhost:25). My apologies for my questions and thank you for your help! GT --- End Message ---
[no subject]
This message wraps the original message. The sending domain has a DMARC p=reject policy, which unfortunately can cause bounces. See http://www.mutt.org/mail-lists.html#dmarc To remove this message, please change the domain policy to p=none or p=quarantine.--- Begin Message --- Hi, Sorry I am very new (as of today) to mutt and I am trying to get started. My set up is as follows: I use fetchmail and procmail to get my mail delivered to Maildir mailboxes. So,my mail is inside folders in ~/Maildir in the following manner: ~/Maildir/inbox~/Maildir/sent~/Maildir/drafts ~/Maildir/work/~/Maildir/work/user1~/Maildir/work/user2~/Maildir/bills~/Maildir/family etc. I want to show this tree on a side-pane. So, my initial attempt at .muttrc has the following: modified from mutt & Maildir Mini-HOWTO set mbox_type=Maildir set folder="~/Maildir" mailboxes `echo -n "+ "; find ~/Maildir -type d -name "*" -printf "+'%f' "` However, when I launch mutt, I get nothing and after a lot of blank stares on-screen, I get: Mutt:/var/spool/mail/itsme [Msgs: 0 Inc: 20](date/date)(all)-- I was wondering if I could get some help. My apologies for my questions and thank you for your help! GT --- End Message ---
[no subject]
This message wraps the original message. The sending domain has a DMARC p=reject policy, which unfortunately can cause bounces. See http://www.mutt.org/mail-lists.html#dmarc To remove this message, please change the domain policy to p=none or p=quarantine.--- Begin Message --- Hi, Sorry I am very new (as of today) to mutt and I am trying to get started. My set up is as follows: I use fetchmail and procmail to get my mail delivered to Maildir mailboxes. So,my mail is inside folders in ~/Maildir in the following manner: ~/Maildir/inbox~/Maildir/sent~/Maildir/drafts ~/Maildir/work/~/Maildir/work/user1~/Maildir/work/user2~/Maildir/bills~/Maildir/family etc. I want to show this tree on a side-pane. So, my initial attempt at .muttrc has the following: modified from mutt & Maildir Mini-HOWTO | | | | mutt & Maildir Mini-HOWTO | | | set mbox_type=Maildir set folder="~/Maildir" mailboxes `echo -n "+ "; find ~/Maildir -type d -name "*" -printf "+'%f' "` However, when I launch mutt, I get nothing and after a lot of blank stares on-screen, I get: Mutt:/var/spool/mail/itsme [Msgs: 0 Inc: 20](date/date)(all)-- I was wondering if I could get some help. My apologies for my questions and thank you for your help! GT --- End Message ---
[no subject]
This message wraps the original message. The sending domain has a DMARC p=reject policy, which unfortunately can cause bounces. See http://www.mutt.org/mail-lists.html#dmarc To remove this message, please change the domain policy to p=none or p=quarantine.--- Begin Message --- AOL and Yahoo have been warning me that there will be new security procedures in a couple days. I access AOL and Yahoo with IMAP/SMTP. How will this affect my (infrequent) use of these services with Mutt? URLs: https://uk.help.yahoo.com/kb/new-mail-for-desktop/SLN27791.html?impressions=true#others https://help.aol.com/articles/allow-apps-that-use-less-secure-sign-in#others Thanks, gil --- End Message ---
[no subject]
This message wraps the original message. The sending domain has a DMARC p=reject policy, which unfortunately can cause bounces. See http://www.mutt.org/mail-lists.html#dmarc To remove this message, please change the domain policy to p=none or p=quarantine.--- Begin Message --- On 2020-09-01, at 10:49:22, Jon LaBadie wrote: > > On Mon, Aug 31, 2020 at 01:06:48PM -0400, Mark H. Wood wrote: >> >> >> It's easy to edit documents in a revisable format until they are >> satisfactory, and then render the finished content in a final format >> (or multiple final formats) for publication. > > Good point Mark. And certainly my need is distribution of a finalized > document. I've kinda decided to create the 2 columns of seating > assignments using a text editor and shell tools. This will be the > main part of the email msg body. That will also be pasted into an > "odt" document, some formatting and boiler plate added, then exported > as a "pdf" for attachment to the email. > If you have LibreOffice, consider editing to a .csv; importing to LibreOffice as a spreadsheed, and exporting as .pdf (or .html). A shell tool might automate converting plain text to .csv. -- gil --- End Message ---
[no subject]
This message wraps the original message. The sending domain has a DMARC p=reject policy, which unfortunately can cause bounces. See http://www.mutt.org/mail-lists.html#dmarc To remove this message, please change the domain policy to p=none or p=quarantine.--- Begin Message --- (Plus one Bcc:) On 2020-08-26, at 23:40:08, Jon LaBadie wrote: > > For so long I've used mutt and composed my emails in ASCII, > now I guess Unicode, that I'm ignorant of potential approaches > to a bit of formatted text. > The needed symbols seem to exist in Unicode: https://en.wikipedia.org/wiki/Playing_cards_in_Unicode > Both a friend and I organize weekly online bridge games for > 20-30 players. My seating notices go out as simple text. He > creates a 2 column Word document and includes it as an attachment. > Players who wish to see his seatings must use an external office > suite to view the attachment. > One thing I think of is a spreadsheet, packaged as a .csv. It's marginally legible as text or either Windows Excel or MacOS Numbers should render it. An alternative is the attractively priced LibreOffice. > Is there anything I could use to create such "formated text", then > distribute it in the body of a mutt message having some hope that > the recipients see it correctly? > Is there an example to try? If it exists as .xlsx it could be exported as .csv -- gil --- End Message ---
Using Maildir format, changing mailbox
I used to use Mutt way back in the day and, well, I haven't found anything better, so am returning to the fold. Kennel. Whatever. I was never very happy with mbox format so thought I would try Maildir instead. I've got it working, more or less, but my Mutt experience seems quite "raw" in that the format I'm using bleeds through into the user interface. To explain: I have a number of different email accounts on a number of different servers, and I do that for a number of reasons, one being that my email is then effectively pre-filtered. Work email goes to, say, some...@example.com, non-work email to someb...@example.org, and so on. I want that to be the case with my local email experience as well, so I've set up procmail to deliver into different directories depending on where the email comes from/to: # work :0: * ^(From|Cc|To).*some...@example.com Work/ # play :0: * ^(From|Cc|To).*someb...@example.org Play/ # rest :0 Mail/ When I open Mutt it starts in the Mail mailbox. Okay, fair enough, it has to start somewhere. But then I press 'c' to change mailbox and, if I can't remember what mailboxes I have (seriously, I have a *lot*), can press '?' to find them. Except there's the "leakage", I see the cur, new, and tmp directories listed inside the Maildir directory. Then, yes, I can go up a level and choose the mailbox I want. All of this is a long-winded way of asking: is there a better way of changing mailbox, please, given what I'm to do overall? Maybe I am just missing a config setting? (he says, hopefully) What I'd like is that when I press '?' I get a list of *mailboxes* rather than directories, because, as a user, I'm really not interested in directories, I only want to know about mailboxes.
Re: Going GUI...er
No! The ultimate goal should be do accept calendar invitations from your calendar! Your mail client is reserved for reading email. MIME attached ics files to coordinate meeting attendance is an atrocity. On Sun, Apr 05, 2020 at 08:48:35PM +0100, Sam Kuper wrote: > On Sun, Apr 05, 2020 at 08:05:29AM -0700, m...@amrx.net wrote: > > Truly, sending the human an E-Mail, to read, is a great response, but > > could trigger a frustrating conversation about auto populating > > calendar items, be prepared to defend your mutt way of life. > > Been there, done that. Several times. Still standing, > > If/when it becomes possible to RSVP, in a machine-readable fashion > directly from Mutt, to calendar-invites-sent-via-email, I'll switch to > that. > > At least, as long as the feature is sensibly implemented. Based on > Mutt's track reccord, it probably will be. > > -- > A: When it messes up the order in which people normally read text. > Q: When is top-posting a bad thing? > > () ASCII ribbon campaign. Please avoid HTML emails & proprietary > /\ file formats. (Why? See e.g. https://v.gd/jrmGbS ). Thank you.
Re: Going GUI...er
Propagating the notion that E-Mail and Calendar are separate things is probably the best thing to do, to undo their evil marriage. The calendar related RFC's that I have looked at indicate that the protocols were designed work and communicate completely independent of E-Mail, yet the majority of people believe these things are designed or must to go together. Truly, sending the human an E-Mail, to read, is a great response, but could trigger a frustrating conversation about auto populating calendar items, be prepared to defend your mutt way of life. On Sun, Apr 05, 2020 at 11:44:16AM +0100, Sam Kuper wrote: > On Sat, Apr 04, 2020 at 09:06:13AM -0700, Felix Finch wrote: > > On 20200404, Sam Kuper wrote: > >>This ~/.mailcap works tolerably under Gnome [...] > > > > I've been using something similar for several years, and one thing > > missing from this is a way to respond to invites. Perhaps it's an > > Outlook-only thing, but I invariable get followup emails asking me to > > click "Accept", and I never see any such links. Looking at it in the > > Outlook webmail, there is an RSVP section with buttons for Accept > > Yes/No. > > AFAICT, this is just another Micro$oft lock-in attempt. > > > > Looking at the actual mime part, each invitee has an RSVP section. > > > >ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Joe > > Blow :mailto:jb...@megacorp.com > > > > [...] Do any calendar filters replicate this RSVP business? [...] > > I, too, would be grateful to know this. Not because I support lock-in, > but because simplifying calendar invites/RSVPs should not be beyond the > means of free (as in freedom) software. (Compatibility with proprietary > implementations should be a secondary concern.) The key difficulty is > likely to be broken time zone implementations (see below). > > > In the meantime, you can just reply to the message (which, after all, > was sent as an email): "Thanks, I accept your invitation to the meeting > at 5pm PDT on 5th May 2020." > > N.B. I strongly suggest including the time, zone and date in your reply, > as above, because sometimes automated invites: > > - use the wrong time zone for the event, AND > - do not specify the time zone that they are assuming! > > > > The only "http" links are for zoom. > > Don't be shy about alerting those senders that they are sending you > links to malware. Seriously. See: https://gu.com/p/dtx4g > > N.B. Even MS Outlook should not be sending Zoom links by default (not > because Micro$oft cares about giving you malware, but because Zoom is > non-Micro$oft). So, those senders presumably installed or configured > something at their end that causes those links to be inserted. > > -- > A: When it messes up the order in which people normally read text. > Q: When is top-posting a bad thing? > > () ASCII ribbon campaign. Please avoid HTML emails & proprietary > /\ file formats. (Why? See e.g. https://v.gd/jrmGbS ). Thank you.
Re: mutt and clear-signing
Derek Martin wrote: > On Tue, Jul 02, 2019 at 02:48:21PM +0100, tech-lists wrote: > > Hi, > > > > I'm using mutt v.1.12.0 on freebsd-current with gpgme. In my config, mutt > > will > > verify clearsigned gpg sigs if the public key is on the gpg keyring. > > > > But if the key is unknown, mutt will say the key is unknown, and this is > > normal and expected. > > > > What I want to happen is, if the key is unknown i'd like mutt to prompt > > something like "get key y/n" or even automatically fetch the key and add > > it to the keyring if the public key is valid. > > You can do this by configuring gnupg itself to do it. You need to > tell gnupg what key server to use (you probably already did that), and > then you need to add the option auto-key-retrieve in gnupg.conf. > > -- > Derek D. Martinhttp://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 > -=-=-=-=- > This message is posted from an invalid address. Replying to it will result in > undeliverable mail due to spam prevention. Sorry for the inconvenience. be warned though that the SKS network (where you might get keys from) has recently been attacked by the poisoning of some high profile keys that, if fetched and imported, will break your gnupg installation. see the following for more information and advice: https://gist.github.com/rjhansen/67ab921ffb4084c865b3618d6955275f
Re: order of sending mail and saving to fcc
Derek Martin wrote: > On Tue, Jun 11, 2019 at 01:45:18PM -0700, Kevin J. McCarthy wrote: > > On Tue, Jun 11, 2019 at 06:43:25AM -0700, Kevin J. McCarthy wrote: > > I've pushed a branch up to gitlab, kevin/fcc-before-send. It adds > > $fcc_before_send, default unset. > > Obviously you don't need to listen to me, but I do want to state for > the record that I'm opposed to this change going in. I'm sure a lot > of people will say, "Oh, it's just a config variable." Those > who've been paying attention will realize I've consistently argued > against new config variables by default, over the last 20+ years, and > I'll restate my unwavering reasoning for that here: > > Mutt already has tons of config vars, and Mutt is already a beast to > learn how to configure--I think it takes years for people to even > realize all the features Mutt has that are configurable, nevermind > getting a config that does all they want. As such, (I believe) adding > a new config variable is inherently bad, and should only be done when > the good of having the alternative behaviors outweighs that bad. Such > cases clearly exist, and in those cases I don't argue against them. > > This is not such a case. I believe I have demonstrated in my last > post in this thread, using sound logic, that the alternative behavior > is not only never an improvement for any of the stated concerns, but > inarguably worse for some of the relevant concerns, and as such clearly > does not outweigh the bad of making Mutt that much more unweildy to > understand and configre. Therefore, the change should not be > committed. > > -- > Derek D. Martinhttp://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 I could be wrong (and I haven't read the patch so apologies if I'm being silly) but I think that this patch might be too simple. If all it does is perform the fcc before sending rather than after sending, then the message that it saves isn't the message that is subsequently sent (as explained earlier). While I personally think that the copy in the /tmp directory suffices in times of trouble (so far anyway), clearly not everyone agrees. However, I would expect such people to still want the actual message that is saved to be a true record of the message that was sent (taking into account the other fcc-related config options). At least, once it is successfully sent. So, if something like this config option were to go ahead, it should probably save the pre-sending version before sending and, when the sending succeeds, replace the pre-sending version of the message with the final version that was actually sent. Otherwise, the saved message is only appropriate for re-sending but not appropriate as a permanent record of what was sent. At least, that's the impression I get from reading this thread. But that sounds like messy behaviour if the pre-sending copy and the post-sending copy are in the same file. If the patch is as I imagine, the documentation should make it clear that turning the new config option on means that the messages that are saved are not identical to the messages as they were sent. Having the pre-sending copy in a separate file would help keep the code change simple but of course that will bring about yet another config option to supply the name of the additional file (like postponed). Another advantage of a separate file for messages-that-are-in-the-process-of-being-sent is that the presence of the file on disk is an indication of a failure to send since the file would be deleted or emptied when the post-sending copy is saved. Note that I'm not recommending these changes, just pointing out that using the new fcc_before_send shouldn't necessarily mean that the sent box is no longer a true record of what was sent. Again, apologies for wasting time if I've misunderstood things. I've used mutt for decades but I'm no expert on its internals. cheers, raf
NeoMutt 20170113 (1.7.2) (debian9) segfaults on readonly mbox
Hi, This might not be the right place to report this but I've just discovered that the mutt package on debian9 stable (or rather NeoMutt 20170113 (1.7.2)) segfaults if you ask it to write to a readonly mbox file. It happened several times yesterday before I realised what was wrong (and yes, I did have a reason for wanting some mbox files to be temporarily read-only). touch readonly chmod 400 readonly mutt Save any message to the readonly mbox and... /home/raf/mail/readonly: Permission denied (errno = 13)[1] 25270 segmentation fault mutt Happens every time (for me). So don't do that. I know it's an old version and it might have been fixed (but I couldn't see that it has from the changelogs). But if you use debian9 stable, this is the version you'd get. If I can get past neomutt's configure script, I'll see if it's still a problem. It seems that it can't find libncursesw no matter how many ways I tell it where it is. cheers, raf
Re: re-sort and save?
Cameron Simpson wrote:
> On 23May2019 09:08, m...@raf.org wrote:
> > is it possible to get mutt to
> > reorder an mbox file by date ("od")
> > and then save it in that order?
> >
> > if not, i can use some other program
> > but i'd trust mutt more.
>
> I haven't tried it, but what if you sort on date and then save or copy to a
> separate new mbox file? Might do what you need.
>
> Cheers,
> Cameron Simpson
Hi Cameron,
Perfect, thanks. I owe you a beverage of your choice. :-)
After sorting "od", I tagged all messages "T."
then saved tagged messages ";s=newfilename"
and they were written in the desired order.
cheers,
raf
re-sort and save?
hi,
is it possible to get mutt to
reorder an mbox file by date ("od")
and then save it in that order?
if not, i can use some other program
but i'd trust mutt more.
cheers,
raf
Re: Attachment weirdness
Cameron Simpson wrote: > On 14May2019 09:58, jeremy bentham wrote: > > (Whatever the e-mail abbreviation for "sound of hand slapping > > forehead" is...) > > What is the sound of one hand slapping? > > Cheers, > Cameron Simpson that sound would be: "doh!"
Re: majordomo [Was: Send to a Listing]
Derek Martin wrote: > On Wed, Apr 17, 2019 at 09:53:58AM +1000, m...@raf.org wrote: > > if you want majordomo, i can send a copy but it's available at: > > > > ftp://ftp.icm.edu.pl/packages/majordomo/Welcome.html > > > > note that it's at least 18 years old and unsupported (but still works). > > it might be a better idea to use mailman. > > The whole point of suggesting majordomo is that (IIRC) it keeps the > recipients in a plain-text file, one address per line, making it > trivial to replace them by dropping in a file that had them in that > format in place of the existing file. You can't do that with mailman > because it stores them in a db file. So in that case you'd be better > off using a script to generate a mutt aliases file, or some other > thing. Fair enough. I hadn't read the entire thread. > -- > Derek D. Martinhttp://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 > -=-=-=-=- > This message is posted from an invalid address. Replying to it will result in > undeliverable mail due to spam prevention. Sorry for the inconvenience. >
Re: majordomo [Was: Send to a Listing]
Ian Zimmerman wrote: > On 2019-04-12 14:20, Derek Martin wrote: > > > I imagine google would turn up some source, but on my desktop, I get > > it by typing > > > > apt install majordomo > > > > Hmm, what distribution? Search on packages.debian.org doesn't find it, > even when I set the "Distribution" select widget to "Any". on debian and ubuntu, apt-cache search majordomo only shows mailman. if you want majordomo, i can send a copy but it's available at: ftp://ftp.icm.edu.pl/packages/majordomo/Welcome.html note that it's at least 18 years old and unsupported (but still works). it might be a better idea to use mailman. cheers, raf
Re: Copying text from Mutt viewer also copies trailing space
Felix Finch wrote: > On 20190101, Vegard Svanberg wrote: > > Hi, > > > > Happy New Year! > > > > I have a problem that's been bugging me for years: > > > > Let's say the terminal window is appr. 120 characters wide. The email > > I'm reading is ~80 chars wide. In other words, columns 80-120 are blank. > > > > When I copy text from Mutt into whatever else (vim, text editor, browser > > textarea... doesn't matter), the paste includes the (trailing) spaces > > (\s) from column 80-120, so I have to manually remove them. > > > > This seems to only happen when I run Mutt inside screen or tmux. > > However, I use screen/tmux extensively and I only observe this > > phenomenon inside the Mutt viewer. > > > > If I, say, edit the email so it opens in vim (like esc-e or hitting > > reply), this does not occur. > > > > How can I find out what causes this and (more importantly) fix it? > > I just used X select to select two lines from your message, running > inside tmux, and paste them into emacs. It pasted in the two lines > with no extraneous spaces on either line. The selection highlighted > the full width of both lines, 210 columns. I don't know what I am > doing differently, but there are no extraneous spaces for me. for me it happens when mutt is in tmux or screen in xterm, pasting into gvim. according to this, there isn't a solution: https://stackoverflow.com/questions/28749919/text-copied-from-vim-inside-a-tmux-session-is-padded-with-spaces-to-the-right according to this: https://unix.stackexchange.com/questions/218248/trailing-spaces-when-copying-from-console there's an xterm resource that will fix it: https://invisible-island.net/xterm/manpage/xterm.html#VT100-Widget-Resources:trimSelection i just tested it and it fixes it in both screen and tmux. yay! that's been bothering be a bit lately too. thanks for asking about it. so, put this in a file like ~/.xresources.screen: XTerm*VT100.trimSelection: True and cause this to be executed when you log into X11: xrdb -merge ~/.xresources.screen cheers, raf
Re: throw away signature in reply
Michael Wagner wrote: > Hello folks, > > I edit my mails here in mutt with vim. When I reply to a message I don't > want to delete the signature from the original poster by myself. Can this > be done in mutt or must it be done in vim. > > TIA Michael hi, you could define your muttrc editor variable to be a program that locates and removes signatures before invoking vim on the result. you just have to write the program. i used to have procmail filter emails through a program that deleted signatures and legal notices upon arrival. i had to add new signatures to be recognised whenever new ones turned up. so it can be automated but it requires some effort. cheers, raf
Re: How to send with charset=iso-8859-1 instead of unknown-8bit?
Ian Zimmerman wrote: > On 2018-06-20 12:16, m...@raf.org wrote: > > > I have some software that invokes mutt (non-interactively) to > > send email with iso-8859-1 body text. > > My guess is that mutt looks at the locale environment (LANG and LC_*) to > set the encoding of the source data, and tries to recode it into one > of the encodings in send_charset. > > If you _know_ your data is iso-8859-1 but your LANG etc. is something > else, try changing LANG locally in your driver script/program. Thanks. I'll try that. Mutt probably detects that it isn't valid utf-8, and so doesn't match the system locale, and so can't be converted. That would make sense. I wonder if setting charset to iso-8859-1 would also fix it. That's for the terminal so it's probably not wise to change that. Maybe assumed_charset? (maybe that's only for incoming messages). I ran some tests and setting LANG=en_AU.iso88591 fixes it. So does setting charset=iso-8859-1 in .muttrc. But setting assumed_charset or send_charset doesn't fix it. Strangely, when I perform these tests, when it gets it "wrong", it's using utf-8 as the character set rather than unknown-8bit. I don't understand that but it's OK. It is as a different user. That might have something to do with it. The user producing the unknown-8bit emails did have send_charset=us-ascii:iso-8859-1 in their .muttrc (I'd forgotten) but the user performing these tests didn't). The main thing is that I now have two ways to fix the problem. I think setting LANG when sending the mail as you suggest is the best method (and leaving charset as it is so that it matches the terminal for when reading mail later). Thanks again. > BTW, running mutt non-interactively has always seemed strange to me. > Why not use something simpler like mailx, or even /usr/sbin/sendmail? Because they don't know about ~/.muttrc or mutt's -e option :-) Mainly, I want mutt to keep a record of outgoing mail in an mbox that I might need to examine later, and I'll be using mutt when I do. If I ever need to send encrypted mail programmatically, I'd probably want to do that via mutt as well. cheers, raf
How to send with charset=iso-8859-1 instead of unknown-8bit?
Hi, I have some software that invokes mutt (non-interactively) to send email with iso-8859-1 body text. I've noticed that emails with accented characters are being sent with charset=unknown-utf8 instead of charset=iso-8859-1. The muttrc manpage says that the default value for send_charset is "us-ascii:iso-8859-1:utf-8" and that, "In case the text cannot be converted into one of these exactly, mutt uses $charset as a fallback". The default charset value is utf-8 (but the body text is not being entered via the terminal). There is no mention of unknown-8bit. I don't understand what conversion is referred to here. I would have thought (incorrectly, no doubt) that mutt would use the first character set in send_charset that could be the character set of the body (i.e. just detection, not conversion). But if that were the case, the default send_charset would almost always result in us-ascii or iso-8859-1 being used since most 8 bit characters are valid iso-8859-1. If my understanding were right, it would make more sense for the default send_charset to be "us-ascii:utf-8:iso-8859-1" (or "us-ascii:utf-8:unknown-8bit"). So I'm clearly not understanding how it works. But I'm only thinking this way because that's how vim works with its fileencodings variable. What am I not understanding? And how do I make mutt set the charset of outgoing mail to iso-8859-1 when it detects accented (iso-8859-1) characters? Thanks, raf
Re: support of two factor authentication?
Tom Fowle wrote: > On Tue, Jun 12, 2018 at 08:49:09AM -0400, Jos? Mar?a Mateos wrote: > > On Mon, Jun 11, 2018 at 08:26:42PM -0700, Tom Fowle wrote: > > > As more isps and email providers require two factor authentication, I > > > hope mutt will support this security system! > > > > Doesn't mutt already "support" this? I use Fastmail with 2FA enabled. > > What I do then is to generate an app-specific password which is the one > > I use in the mutt configuration. There's not much to support, it's just > > a different password, unless there's something I'm not getting right. > > > > Cheers, > > > > -- > > José María (Chema) Mateos > > https://rinzewind.org/blog-es || https://rinzewind.org/blog-en > > Jose, > In what little I've read, I'd thought one needed to authenticate with two > passwords, but I'm probably wrong. > > Thanks, I'll try it if it becomes necessary. > Tom Fowle tl;dr - 2FA/MFA = what you know + what you have + what you are. 2 passwords = 2 * what you know = 1FA. 2FA/MFA is mostly for websites, not pop/imap. however, pop/imap + tls + client certificate = 2FA/MFA (?). however, can't really see that happening. off-topic nonsense about credential stuffing, 2FA/MFA, password managers. long version 2FA/MFA isn't two passwords. It's something you know (like usernames and passwords) and something you have (like access to an email account or mobile/cell/handy phone), and/or something you are (like fingerprints or iris patterns or voice pstterns). Two passwords is just two of something you know so it's still a single factor. However, it should be pointed out that 2FA/MFA is mostly for websites. The IMAP/POP protocols have no support for it. It's unlikely that the POP/IMAP protocols will be changed to incorporate 2FA/MFA. And until that happens, I doubt there's much that mutt (or POP/IMAP servers) can do about it. Actually, I'm probably completely wrong about that. It's probably quite possible for a POP/IMAP server to require the use of TLS and to require that you have a client certificate that it recognises as well as your username and password. That would be 2FA/MFA and mutt might not even need to know about it. The underlying TLS library would take care of it. But the email service provider would have to have some way of issuing you with a client certificate and instructions on how to install it. If the client certificate is encrypted then mutt might need to know about it to support gathering the passphrase needed to decrypt the client certificate. I don't know. But I can't see too many email service providers requiring all of their users to install (and possibly encrypt) client certificates on all of their devices where they read email. But it could be an opt-in thing where if you ask for a client certificate, then you always need to use it. The biggest threat that is mitigated by 2FA/MFA is credential stuffing where someone hacks one website, steals the usernames (usually email addresses) and passwords, cracks the passwords, then re-uses them on all the other websites to see if they work. Last I heard, 40% of website logins attempts worldwide are automated using stolen credentials. The attempts that succeed are worth more in criminal markets than untested stolen credentials. Where there's a business model, there's a way. Credential stuffing is here to stay. The best defense against this is for all websites to store passwords in a way that can't be cracked or at least can't be cracked without spending vast sums of money on hardware (e.g. scrypt+hmac). But of course website users have no control over that. Just having unique strong passwords for every website is enough to mitigate against credential stuffing. Real 2FA/MFA is more for protecting against attacks that target you specifically. But even then, some 2FA/MFA systems send an email with a code to an email account that you might only have 2FA/MFA access to, but most send a text message and, at least in Australia, it's very easy to steal someone's mobile/cell/handy phone number (not the handset, just the number), so 2FA/MFA doesn't really protect against targeted attacks either. So it only really protects against credential stuffing. But it does make targeted attacks harder to perform so it is worthwhile for that too. Anyway, if you're just concerned about credential stuffing, use a password manager and use it (or at least unique strong passwords) for any POP/IMAP accounts you have as well as for any website accounts. I think the reason that some websites require 2FA/MFA is because they can't force you to use strong unique passwords for every website. But if you choose to use strong unique passwords for everything, then you don't really need 2FA/MFA (unless you also want to defend yourself against targeted attacks by people who aren't willing to put too much effort into the ta
Re: choices on reading HTML emails
Jude DaShiell wrote: > I wonder, can mutt be used to strip all images and toss them in the > trash and strip all image attachments and toss them in the trash then > make remaining text viewable in mutt? Some of us with this kind of > capability could save lots of disk space. I had the same thought in a job where people kept sending me large documents I didn't want. Or at least, I wanted text-only versions of their content. So I wrote http://raf.org/textmail/ which lets you selectively replace non-text attachments with text-only versions or just delete attachments. It can dramatically reduce your mailbox size, either as email arrives (with procmail) or it can be applied to an existing mbox file. It can probably be used via mutt as a filter but I've always run it via procmail. I also had procmail filters that removed all the email signatures and legal notices that end up accounting for 95% of most work-related email conversations but that's something that needs to be constantly tweaked according to the signatures you encounter. Here's the usage message for textmail. I haven't used it in a while and it depends on lots of external programs to do the translations. I hope they all still work. :-) These days, I save the attachments I need and then manually delete attachments from the message in the view attachments menu. cheers, raf usage: textmail [options] options: -h - Print the help message then exit -m - Print the manpage then exit -w - Print the manpage in html format then exit -r - Print the manpage in nroff format then exit -M - Output in mailbox format (mboxrd) -T - Output in raw mail format (for smtp) -W - Don't replace MS Word attachments with text -E - Don't replace MS Excel attachments with csv -H - Don't replace HTML attachments with text -R - Don't replace RTF attachments with text -P - Don't replace PDF attachments with text -U - Don't translate winmail.dat attachments -L - Don't reduce appledouble attachments -I - Don't delete image attachments -A - Don't delete audio attachments -V - Don't delete video attachments -X - Don't delete MS Windows executable attachments -B - Don't recode text that was base64-encoded -S - Don't replace spaces in filenames with underscores -Z - Do translate signed content (discards signatures) -O - Delete all application/octet-stream attachments -! - Delete all application/* attachments -D hdrs - Delete headers (list of header prefixes and filenames) -K types - Keep attachments (list of mimetypes and filenames) -f - On translation error, keep translation, not original -? - Print paths of helper applications then exit
Re: Wide Glyph Problems
On Mon, Apr 09, 2018 at 05:04:15PM +0100, David Woodfall wrote: > I'm having problems with some messages that use wide glyphs, > especially mail from Ebay (even though I have chosen plain text > mail). I think that I am experiencing something similar, but in my case rendering errors generate what appears to be an unexpected linebreak or similar. This will throw the whole screen off until I do a manual redraw. Using mutt in gnu screen in urxvt. Not sure if it's related, but it happens with the same character sets you describe.
Re: leaking timezone
Cameron Simpson wrote: > On 23Mar2016 13:56, John Long <codeb...@inbox.lv> wrote: > >On Tue, Mar 22, 2016 at 08:40:21AM +1100, Cameron Simpson wrote: > >>On the othe hand, I do not think mutt makes the header. I'm in > >>compose mode right now with headers and the Date: header is not > >>there. > > > >Aside from the Received: header that was already mentioned upthread, Mutt > >can add headers when it sends meil that you don't see in compose mode. I > >don't think it's a proof of anything that you don't see it. > > How irritating. but it makes sense for the Date: header not to be present when composing the email. it hasn't been sent yet. it might get postpone, or it might take a lot of time to write, etc. it makes sense for it to be added when it is sent and not before. perhaps if you put your own Date: header in while composing, mutt would not replace it. cheers, raf
Re: leaking timezone
hy...@lactose.homelinux.net wrote: > I don't think mutt puts the Date: header on outgong email. It puts the Date: header in mail that it saves to the 'set record' mbox so it probably does.
Re: How to save messages by To: field?
Alright, I made a solution for this: Gist: https://gist.github.com/rmaddox/f1fcf6b4a32f04df5949 # macro index,pager S ':set wait_key=nosave-hook.pl:source /home/data1/protected/tmp/save-hook.tmp' - the macro S envokes the script at Gist. - script saves in the file the save-hook - macro sources it - and envokes save-message command This way, I can convert old Sent folders to Maildir/n...@example.com folders for easier searching. On Wed, Feb 17, 2016 at 10:44:04AM +0100, mutt-us...@rcdrun.com wrote: > Hello, > > I would like to know how to save-message to the To: field. > > By default it saves to "From:" field email address, like: > > =f...@example.com > > but I would like to change it temporarily to save in =t...@example.com by > the recipient. > > Thank you, > Rosario
How to save messages by To: field?
Hello, I would like to know how to save-message to the To: field. By default it saves to "From:" field email address, like: =f...@example.com but I would like to change it temporarily to save in =t...@example.com by the recipient. Thank you, Rosario
Re: Conditional configuration
Hello David, On Fri, Jan 29, 2016 at 05:51:46PM -0800, David Champion wrote: > * On 29 Jan 2016, martin f krafft wrote: > > > > It's a shame to hear that Karel doesn't do his work within the > > community. mutt-kz is a nice piece of work and why not provide an > > officially experimental mutt? > > I wonder, too, why he works entirely separately. I wish he were feeding > back to the community but he seems more interested in maintaining a > separate fork, and letting us worry about following/backporting his > work. It is not a shame. It is a feaute. Mutt is published and distributed by the GNU GENERAL PUBLIC LICENSE, which means there can be 100 forks, not just one, for any purpose, by anyone and that shall not be invalidated anyhow. Software produced under this license is freely available and any source code could be merged and used in the original Mutt. So, whoever is producing the fork, DOES work with the community within the scope of the GNU GPL. Rosario
Re: Conditional configuration
Hello, I don't understand why be jealous on something that has been clearly worked out in the licence itself. I don't know who is that man, but speak to him. Don't blame people for doing something that was intended to do in the first place. It was intention that everyone can make a fork and do what they want. So don't stamp on the freedom of software and GNU GPL, as there is just nothing written about the "Community" in the licence. Not even the word "community" is there. On Fri, Jan 29, 2016 at 11:13:52PM -0800, David Champion wrote: > * On 29 Jan 2016, mutt-us...@rcdrun.com wrote: > > > > So, whoever is producing the fork, DOES work with the community within > > the scope of the GNU GPL. > > Working within a development community and keeping the terms of a > license are disjoint. Doing one gains you no ground on the other. > mutt-kz keeps the license. It does not work with the greater mutt > community. > > -- > David Champion • d...@bikeshed.us
Re: Conditional configuration
Dear David, The efforts to bring back some sources to the original mutt are to be made by those developers of the original mutt. That is the point of the GNU GPL licence. I have looked up in my dictionary the word "envious": _painfully desirous of another's advantages_ You see the disadvantage. I see the benefit. Someone is developing on his own mutt software, and that may be patched in the original mutt. If you think this is too much work, why not speak to the person who has made the forked mutt? Why bash such person, who is contributing, on the public list that is going to stay here for ages. Rosario On Fri, Jan 29, 2016 at 11:58:47PM -0800, David Champion wrote: > * On 29 Jan 2016, mutt-us...@rcdrun.com wrote: > > Hello, > > > > I don't understand why be jealous on something that has been clearly > > worked out in the licence itself. > > > > I don't know who is that man, but speak to him. Don't blame people for > > doing something that was intended to do in the first place. > > > > It was intention that everyone can make a fork and do what they want. So > > don't stamp on the freedom of software and GNU GPL, as there is just > > nothing written about the "Community" in the licence. > > > > Not even the word "community" is there. > > I don't follow why you're bringing up the GPL. It has nothing to do > with my concerns. I don't know who this guy is either, but as far as I > know he's completely within his licensed rights and I have nothing to > say about that. > > What bothers me is the approach. It follows the very loose flavor of > a thousand "fork me on github" users. This model is OK. It's open > source, it's great for downstream. But if only benefits upstream if > someone makes the effort to patch upstream. The usual model is either > that when you fork, you take responsibility for guiding changes back > upstream, or that people at both ends become cooperative partners in > exchanging ideas between forks. There are discussion and pull requests. > Karel Zak doesn't do this (he's never posted to mutt-users or mutt-dev) > and I don't recall that anyone else has ever made that effort either. > > So his project is de facto a divergent fork. It has its own > distributions and adherents, and nobody is bringing any efforts in > mutt-kz back to mutt. It divides the mutt user community. And his > decision to convert all his development to git means that even if > someone makes the missing effort, it's more work to cherrypick anything > back to mutt.
Re: Conditional configuration
I am sorry to bring you any negative feelings.
mutt, to use as default handler in chromium
Hello, my mailto: handler was mutt.desktop, and it worked just perfect. Until today. Today I had a bug filed in chromium browser, as it was an extension with unwanted redirection. I have removed the extension. And used bleachbit to remove some cache and so on. Now, mailto: handler is not working at all. I get error from chromium: 946:9946:0118/223203:VERBOSE1:navigator_impl.cc(168)] Failed Provisional Load: mailto:some...@example.com, error_code: -3, error_description: Unknown error., showing_repost_interstitial: 0, frame_id: 1 Somebody knows how to "enable mutt" to become default URL handler for browsers? I am in IceWm, and my xdg-settings get default-url-scheme-handler mailto gives: mutt.desktop as result. Thanks
How to refresh mailboxes view (y)
Hello, I am mutt user since many many years. And I discover always some new features. Recently I was started using key (y) to view some mailboxes. And I get the view. Something like this: 1 5 imaps://mail.example.com:993/INBOX 2 0 imaps://mail.example.com:993/INBOX.Archive 3 0 imaps://mail.example.com:993/INBOX.Drafts 4 0 imaps://mail.example.com:993/INBOX.folder1 5 0 imaps://mail.example.com:993/INBOX.folder2.com 6 5 imaps://mail.example.com:993/INBOX.folder4 Now, some of those folders are not accurate any more. But I cannot delete them from the list or refresh the list. I get the error: mailbox does not exist, or must be subscribed to. And it does not exist, but it is still on the list. I am using headercache. Those are IMAP folders. I would like to refresh the list to get it accurate. Imagine, I have many folders there I need to manage. The keycode is (y). I have tried searching for option, but could not find. Thank you much. Rosario
Re: How to refresh mailboxes view (y)
I guess, I did not try the option (u), to simply the unsubscribe the folder, and after (y) (y) I could see the new fresh list of accurate folders. On Wed, Jan 13, 2016 at 10:37:02PM +0100, Tomas Nordin wrote: > > features. Recently I was started using key (y) to view some mailboxes. > > And I get the view. > > Thanks, great new discovery now for me too. > > > Something like this: > > > > 1 5 imaps://mail.example.com:993/INBOX > > 2 0 imaps://mail.example.com:993/INBOX.Archive > > 3 0 imaps://mail.example.com:993/INBOX.Drafts > > 4 0 imaps://mail.example.com:993/INBOX.folder1 > > 5 0 imaps://mail.example.com:993/INBOX.folder2.com > > 6 5 imaps://mail.example.com:993/INBOX.folder4
Re: sending mails readable on small screens
Derek Martin wrote: > On Mon, Nov 30, 2015 at 09:48:48PM +0100, Matthias Apitz wrote: > > > > Can you put it soemwhere where only HTTP is onvolved. SSL claims the > > > > page as insecure. > > > > > > It only claims that the certificate the server is using is > > > self-signed, meaning that it can't be validated as belonging to anyone > > > in particular by the big certificate trusts. If you're willing to > > > look at it without SSL entirely, then who cares if the cert doesn't > > > validate? This is just not interesting. > > > > Maybe for you (Derek Martin) it is not, but for me. > > OK, fair enough, but then can you please explain what the issue is? > Can you explain how a site serving SSL with a self-signed certificate > is the slightest bit less secure than the same one not using SSL at > all? > > > It is already an issue if a posted URL of http://... is redirected > > to some SSL URL of untrusted certifications. > > As for the redirect, it's to the same hostname, using a more secure > version of the same protocol, albeit with an unverifiable > certificate--but you couldn't verify the server's identity before > either so there's no difference whatsoever in that regard. How is > UPGRADING the security a problem? it's not just self-signed. that would be fine. it's also for a different hostname (git.rmz.io, not rmz.io) and it's expired (22/3/2015). hopefully, they are the reasons that the browser labelled it as insecure. but i agree that it's unimportant for the purposes of this discussion. it's not like that jpg is asking for a password for anything. it's just a jpg. cheers, raf
Re: Open postponed menu on startup
Xu Wang wrote: > I would like to have mutt open postponed when I first start mutt. Is > there a way to do this from the .muttrc? I suppose I could do that > "push R" trick, but I would prefer a .muttrc solution. > > Kind regards, > > Xu if a shell solution would do, then: alias muttp='mutt -p' or similar.
Re: Danger, real or imagined. [Was: Some desired features, do they exist?]
Ian Zimmerman wrote: On 2015-08-13 20:24 +1000, Erik Christiansen wrote: A line buffer of length $LINEBUF is used when processing the rcfile, any expansions that don't fit within this limit will be truncated and PROCMAIL_OVERFLOW will be set. If the overflowing line is a condition or an action line, then it will be considered failed and procmail will continue processing. If it is a variable assignment or recipe start line then procmail will abort the entire rcfile. You might like to read both recipe and manpage again. When processing the rcfile, the line with $SUBJECT does not expand. The SUBJECT= line is a variable assignment, not a macro definition. And this (the assignment line) is what I'm worried about, not the later line where $SUBJECT is used. According to the above paragraph, if _the expansion_ doesn't fit in $LINEBUF, the panic mode is triggered. I think substituting a shell command output counts as expansion. Do you not agree? if you are just worried about procmail rules not fitting in $LINEBUF, just make it huge. i have very large automatically-generated procmail rules so i use: LINEBUF=131072
Re: Forcing viewing HTML for certain senders
Cameron Simpson wrote: On 16Jul2015 13:02, Chris Down ch...@chrisdown.name wrote: I eventually worked this out[0]. I had previously tried using a message-hook to set alternative_order, but that didn't work because I didn't realise that alternative_order *appends*, it doesn't overwrite the existing alternative_order. So, the basic solution is to call unalternative_order every time before the message-hook is executed. 0: https://github.com/cdown/dotfiles/commit/c5927d Yep. Just FYI, this is mine: message-hook . 'unalternative_order *; alternative_order text/plain text/html' message-hook '~h X-Mailer: Apple Mail ~X 1-' 'unalternative_order *; alternative_order text/html multipart/mixed text/plain' message-hook '%f htmlers | ~f @no-re...@cc.yahoo-inc.com | ~f @outlook.com | ~f live.com | ~f @facebookmail.com' 'unalternative_order *; alternative_order text/html text/plain' In particular, I maintain a mutt group htmlers to track specific senders which send useless plain text components. Keeps the condition readable. Cheers, Cameron Simpson c...@zip.com.au The optimist proclaims that we live in the best of all possible worlds; the pessimist fears this is true. - Branch Cabell, The Silver Stallion another approach is to automatically run emails through a filter that replaces multipart/alternative + text/plain + text/html attachments with just the text/html attachment if the text/plain attachment is empty or contains the phrase: Your email client does not support HTML email the attached perl script can be used with procmail to achieve this without the need to know in advance who uses email clients that don't understand the meaning of the word alternative. but it is drastic in that it modifies the emails before you see them. you might see that as overkill and you'd probably be right. :-) cheers, raf textmail-htmlonly.gz Description: Binary data
Re: header_cache for mbox
Derek Martin wrote: On Tue, Jul 14, 2015 at 08:23:25PM +0200, Heinz Diehl wrote: On 14.07.2015, Kevin J. McCarthy wrote: With mbox, I guess the designers thought there wouldn't be that much of a speed improvement because it's just a sequential read of a single file. That sounds reasonable. Except, as far as I can tell, it isn't. I see no reason hcache could not significantly speed up scanning mbox folders as well, at least on any system that supports lseek() or similar (which I imagine is any system that Mutt runs on currently). The amount of benefit you'd get from this would greatly depend on the nature of the messages stored in the folder, though... Folders of moderate size or larger, with mostly large messages (or attachments) should see the most benefit, and those with many small messages, or with very few messages, would see the least (but still some). for lseek() to be useful, you need to know where to lseek to which you wouldn't in this case (if you want reliable parsing). and anyway, i'd like to think mutt uses mmap() for mbox files. cheers, raf
Re: autoviewing html gone wrong
Karsten Brand wrote:
raf m...@raf.org wrote on Thu, Jun 26 13:55:
for some reason i can't remember, i changed it to:
text/html; w3m -I %{charset} -T text/html -dump; copiousoutput;
which does the formatting but doesn't give a list of referenced urls
at the bottom so it's less useful.
Maybe you can try this.
text/html; /usr/bin/w3m -dump -I %{charset} -T text/html '%s' -o
display_link_number=1;
copiousoutput;
description=HTML Text;
nametemplate=%s.html
Regards,
Karsten Brand
hi karsten,
thanks. that works too.
cheers,
raf
Re: autoviewing html gone wrong
m...@raf.org wrote:
Karsten Brand wrote:
raf m...@raf.org wrote on Thu, Jun 26 13:55:
for some reason i can't remember, i changed it to:
text/html; w3m -I %{charset} -T text/html -dump; copiousoutput;
which does the formatting but doesn't give a list of referenced urls
at the bottom so it's less useful.
Maybe you can try this.
text/html; /usr/bin/w3m -dump -I %{charset} -T text/html '%s' -o
display_link_number=1;
copiousoutput;
description=HTML Text;
nametemplate=%s.html
Regards,
Karsten Brand
hi karsten,
thanks. that works too.
cheers,
raf
note: the '%s' should really be just %s because mutt puts single
quotes around the filename anyway so in cases where it matters
(i.e. spaces in the file name which doesn't happen anyway), the
extra quotes would defeat the purpose of putting them there.
but it's probably harmless if mutt always determines the file name.
cheers,
raf
Re: autoviewing html gone wrong
Christian Ebert wrote: * m...@raf.org on Friday, June 27, 2014 at 12:26:37 +1000 adding -force_html to the command did fix the problem. yay! Adding nametemplate=%s.html; to your mailcap entry would probably also help/not hurt. that sounds like a good idea. so either -force_html (lynx option) or nametemplate=%s.html (mailcap thing) is enough to fix my problem. cheers, raf
Re: autoviewing html gone wrong
Cameron Simpson wrote:
On 26Jun2014 13:55, raf m...@raf.org wrote:
i used to have this in my mutt mailcap file:
text/html; lynx -dump %s; copiousoutput
and it was good. it formatted the html and gave me a list of
referenced urls at the bottom.
for some reason i can't remember, i changed it to:
text/html; w3m -I %{charset} -T text/html -dump; copiousoutput;
which does the formatting but doesn't give a list of referenced urls
at the bottom so it's less useful.
if i change it back to using the lynx -dump command then i see the
raw html instead of the formatted html (as though i'd used lynx -source
rather than lynx -dump).
i suspect that must be why i changed it to use w3m in the past.
anyway, if i save the html attachment and run lynx -dump on it
then it shows me the formatting page with the list of referenced
urls like it used to but that isn't what happens when mutt invokes
the same command when autoviewing the attachment.
does anyone have any idea why this might be the case or what i can
do to make lynx work again for autoviewing html in mutt?
I would do two things:
First: inspect the message. Is the HTML attachment actually marked
as text/html as its content-type? If not, the wrong filter (if
any) will be chosen from your mailcap file. For example, if the
contenttype header for the attachment is text/plain, mutt will
(correctly) transcribe the HTML unformatted.
mutt is invoking the text/html autoview command. it says this at the top:
[-- Autoview using lynx -dump '/tmp/muttRpvZEI' --]
Second: if the message has the HTML marked as text/html, check that
the correct line is being selected from your mailcap file. I would be
inclined to make a shell script (mine is called unhtml) and put the
lynx (or w3m) incantation inside it. Then hack the script:
#!/bin/sh
exec 2$HOME/unhtml.err
set -vx
lynx -dump ${1+$@}
Then tail -F the unhtml.err file to check that your script is being fired.
i did that and it showed no unexpected output.
Cheers,
Cameron Simpson c...@zip.com.au
adding -force_html to the command did fix the problem. yay!
thanks everyone.
cheers,
raf
Re: REMOVE ME FROM THIS LIST
On Thu, Feb 20, 2014 at 06:31:28PM -0800, ga...@garryricketsonartworks.org wrote: At first I asked nicely, but this BS is getting on my nerves. REMOVE ME FROM THIS LIST! visit: http://www.mutt.org/mail-lists.html click: the Mutt Users link in the Unsubscribe section send: the resulting email afterwards, you might receive an email to confirm the unsubscription. if so, reply to it (if it instructs you to do so).
Re: auto reply to html-mails
Rejo Zenger wrote: ++ 20/01/14 21:40 +0100 - Jan-Herbert Damm: i would like to send an automatic answer to html-mails sent to me (because i'm tired of writing back that i prefer plain-text). I am aware that this is hardly an issue of mutt, but rather procmail or scripting. But i am curious how this could be approached. Procmail would suffice and definately for a rudimentary filter: :0 * ^Content-type: text/html * ! ^X-Loop: autoreply_because_html | (formail -rt \ -APrecedence: junk \ -AX-Loop: autoreply_because_html ; \ cat $HOME/body_of_autoreply.txt) | $SENDMAIL -t Or something along those lines. Untested. Procmail has lots of example in the procmailex manpage as well as on the internet. -- Rejo Zenger . r...@zenger.nl . 0x21DBEFD4 . https://rejo.zenger.nl GPG encrypted e-mail preferred . +31.6.39642738 . @rejozenger this recipe will also fire on emails that contain a multipart/alternative part containing plain text and html alternatives and so would not be ideal as mutt will hapily display the text alternative. i expect that distinguishing such emails from ones that only contain html would take more effort in procmail-land. better ask a procmail expert. an alternative is to use procmail and textmail to automatically convert html emails into plain text on their way into your inbox. the following procmail recipe just translates html emails into plain text. :0 fw | textmail -WERPULIAVXBS it's probably wiser for the recipe to put a copy of the original email somewhere first. textmail is available from http://raf.org/textmail/ and it'll need perl and mktemp and lynx to be installed (and other things if you use its other features). cheers, raf
Re: Embedding a photograph within an email message (not attaching)
Jeffery Small wrote: m...@raf.org writes: Jeffery Small wrote: Is there any convenient way to craft an email message using mutt that embeds a jpeg image within the body of the message for those reading with an HTML mail program, while still attaching it for others who use a text-based reader like mutt? raf wrote: you don't need to resort to html parts. you just need to make sure that the content disposition of the image attachment is inline rather than attachment. to do this, after attaching the image file, while viewing the list of parts before sending the message, use the arrow keys if necessary to navigate to the image attachment and press Ctrl-D which toggles the disposition between inline and attachment. each time you press Ctrl-D, the first character on the left hand side toggle between A and I to indicate the disposition. cheers, raf raf: Thanks for the great reply. I did not realize that this could be done in mutt! However, I tried this out and it did not work. I composed a message and then attached a jpeg file which was listed in the compose menu as: -- Attachments - I 1 /tmp/mutt-cjsa2-102-11172-13795190124143 [text/plain, 7bit, 0.1K] A 2 Image.jpg[image/jpeg, base64, 367K] I toggled the jpeg to inline: -- Attachments - I 1 /tmp/mutt-cjsa2-102-11172-13795190124143 [text/plain, 7bit, 0.1K] I 2 Image.jpg[image/jpeg, base64, 367K] And then sent the message to someone using Outlook on Windows XP. Unfortunately, the message still appears to the recipient as a text message with and attached jpeg file rather than displaying the image inline with the message. Is there something obvious that I am missing? Regards, -- Jeff sorry i can't think of anything else. that should have worked. that's what the content-disposition is supposed to mean but outlook must have its own ideas about such things. it works in thunderbird. cheers, raf
Re: Embedding a photograph within an email message (not attaching)
Jeffery Small wrote: Is there any convenient way to craft an email message using mutt that embeds a jpeg image within the body of the message for those reading with an HTML mail program, while still attaching it for others who use a text-based reader like mutt? I assume that this would require somehow formatting a message with text and HTML parts, but I'm unclear how to formally do this within mutt when using the vim editor. Thanks for any pointers you can offer. -- Jeff hi jeff, you don't need to resort to html parts. you just need to make sure that the content disposition of the image attachment is inline rather than attachment. to do this, after attaching the image file, while viewing the list of parts before sending the message, use the arrow keys if necessary to navigate to the image attachment and press Ctrl-D which toggles the disposition between inline and attachment. each time you press Ctrl-D, the first character on the left hand side toggle between A and I to indicate the disposition. cheers, raf
Re: collapse just one thread
Stefan Brandl wrote: On Wed, Mar 13, 2013 at 09:32:40AM +0100, Elimar Riesebieter wrote: * Stefan Brandl s...@r-kom.de [2013-03-12 15:44 +0100]: Hello, is it possible to start mutt with just one special thread collapsed and all others expanded? Esc v collapse-threadtoggle collapse for the current thread Esc V collapse-all toggle collapse for all threads This is not what I want. All threads should be expanded and one special thread should automatically be collapsed without hitting a key. you could create a folder-hook that expands all threads, searches for the one you want closed, closes it, and then goes back to wherever you want to start. then, there won't be any keystrokes on entry to mutt.
Re: truncating subject line in index
dexter wrote: how can i truncate the subject line to 60 columns. i tried %60s in index_format but it is not working. can someone help. assuming it follows printf syntax: %60s makes it take at least 60 characers (right justified). %-60s makes it take at least 60 characers (left justified). %60.60s makes it take exactly 60 characters (right justified or truncated). %-60.60s makes it take exactly 60 characters (left justified or truncated). so try %60.60s.
Re: mailing lists and different directories
lambda calculus wrote: Hi guys, i recently changed to mutt, and reading the documentation, but i can't find what i want: Since I'm subscribed to a couple of mailing lists i would like to configure mutt to store mails from different mailing lists to different directories. Let's li...@something1.org and li...@something2.org The choice of which directory(mailing list) to read, whould be made with the -f option. Can anyone supply an example please? in ~/.muttrc: subscribe li...@something1.org li...@something2.org save-hook '~C li...@something1.org' =list1 save-hook '~C li...@something2.org' =list2 you can set up aliases for the lists and refer to them by alias in the subscribe directive but the patterns in the save-hook directive probably can't make use of aliases. if you use different from addresses when sending to each list, you might also want something like: send-hook ~tli...@something1.org set from = me+li...@mydomain.org send-hook ~tli...@something2.org set from = me+li...@mydomain.org cheers, raf
Re: Multipart MIME
Jamie Paul Griffin wrote: Hi Does anyone have or know of a perl or python script, or even a shell script, that removes the multipart/(mixed|alternative| ... ) parts of incoming mail and leaves or converts the message into plain text? Also, i wouldn't want to lose any attachments that people might send me. Jamie. hi, i wrote something like that. by default, it converts to text anything that can be converted to text and deletes everything else but you can turn off any specific transformation. it can delete specific mail headers. it translates (most) winmail.dat attachments. if a transformation fails, it leaves the original in place for safety by default. it works via procmail on individual messages or it can be applied to an entire mbox file. it requires the presence of various utilities (e.g. perl, antiword or catdoc, xls2csv, lynx, pdftotext and mktemp). you'd probably just need lynx and mktemp installed. it is available at: http://raf.org/textmail/ and its help message is: usage: textmail [options] options: -h - Print the help message then exit -m - Print the manpage then exit -w - Print the manpage in html format then exit -r - Print the manpage in nroff format then exit -M - Output in mailbox format -T - Output in raw mail format (for smtp) -W - Don't replace MS Word attachments with text -E - Don't replace MS Excel attachments with csv -H - Don't replace HTML attachments with text -R - Don't replace RTF attachments with text -P - Don't replace PDF attachments with text -U - Don't translate winmail.dat attachments -L - Don't reduce appledouble attachments -I - Don't delete image attachments -A - Don't delete audio attachments -V - Don't delete video attachments -X - Don't delete MS Windows executable attachments -B - Don't recode text that was base64-encoded -S - Don't replace spaces in filenames with underscores -Z - Do translate signed content (discards signatures) -O - Delete all application/octet-stream attachments -! - Delete all application/* attachments -D hdrs - Delete headers (list of header prefixes and filenames) -K types - Keep attachments (list of mimetypes and filenames) -f - On translation error, keep translation, not original -? - Print paths of helper applications then exit Filters a mail message or mbox, replacing MS Word, MS Excel, HTML, RTF and PDF attachments with the plain text contained therein. By default, the following attachments are also deleted: image, audio, video and MS Windows executables. MS winmail.dat attachments are replaced by any attachments contained therein which are then replaced by text or deleted in the same fashion. Any of these actions can be suppressed with the command line options. Mail headers can also be selectively deleted. it may or may not be quite what you want. without the -H option, it replaces multipart/aternative where the alternatives are html and text with just the text part. you might want to try it with the following options: :0 fw | textmail -MWERPIAVXBS that would only translate html and leave all other attachments as they are except for winmail.dat attachments. if you want to leave winmail.dat attachments untranslated as well, add the -U option to the command. use at your own risk, obviously. :-) cheers, raf
Re: Multipart MIME
Gary Johnson wrote: On 2012-11-27, mutt wrote: Jamie Paul Griffin wrote: Hi Does anyone have or know of a perl or python script, or even a shell script, that removes the multipart/(mixed|alternative| ... ) parts of incoming mail and leaves or converts the message into plain text? Also, i wouldn't want to lose any attachments that people might send me. Jamie. hi, i wrote something like that. by default, it converts to text anything that can be converted to text and deletes everything else but you can turn off any specific transformation. it can delete specific mail headers. it translates (most) winmail.dat attachments. if a transformation fails, it leaves the original in place for safety by default. it works via procmail on individual messages or it can be applied to an entire mbox file. it requires the presence of various utilities (e.g. perl, antiword or catdoc, xls2csv, lynx, pdftotext and mktemp). you'd probably just need lynx and mktemp installed. Why aren't you all using mutt's built-in ability to select MIME-type-to-text converters? There's no risk of losing a message through improper conversion, you have some limited choice over conversion methods (depending on whether the message/attachment is displayed by the pager or via the attachment menu), and since the message itself is unaffected, you can use different methods of viewing messages in different environments and at different times as your methods improve. Regards, Gary the phrase the message itself is unaffected is the main reason. i wanted to delete/convert the attachments permanently. what you suggest wouldn't do that. i was receiving many large emails in my work mailbox at the time. they were large because they contained many useless attachments. i wanted to keep the semantic content of the messages and i wanted to delete the useless parts of the messages. by doing so, my mailbox was about a tenth of the size it would otherwise have been.
Re: Please set your line wrap to a sane value
Mark H. Wood wrote: On Tue, Nov 20, 2012 at 10:02:28PM +, Ken Moffat wrote: If someone, particularly on a support list, sends an atrociously long line, then it becomes *much* harder to select the appropriate part of that line/paragraph/epistle and delete the rest of it when replying. Ah, well, when *replying*, emacs has a rewrap command. It even recognizes quoted text and adds the quoting prefix, if I use it properly. (Still learning what properly means in this context, though.) surely, par is the ultimate mail formatter? :-) and you really don't need to understand it. http://www.nicemice.net/par/
Re: Old e-mail markup language RFC ?
Jim Graham wrote: I'm not sure of the exact year, but somewhere around 1996--1997, I was using an e-mail markup language that was similar in some respects to html, but it wasn't html. It was limited to simple text markup such as bold, simple colors, *maybe* italic and underline (don't remember), and if I remeember correctly, not much else. Does anyone remember what that is (or was) called, and/or what the RFC for it is? I do remember that Mutt supported it (and it was one of the very few that did). Thanks, --jim hi jim, it was probably text/richtext (not application/x-rtf). the rfc is http://tools.ietf.org/rfc/rfc1523.txt eudora knew about it as well. cheers, raf
Re: Old e-mail markup language RFC ?
Jim Graham wrote: On Wed, Sep 19, 2012 at 03:54:48PM +1000, m...@raf.org wrote: I tried a few tests with it last night. I used my_hdr Content-Type: text/enriched in my ~/.muttrc, and tried a few simple tags (bold, underline, etc.) and the result was text with tags mixed in. check the email headers. i tried the above and the resulting email still had the usual Content-Type: text/plain; charset=us-ascii to change the default content-type, put something like this in .muttrc: set content_type = text/enriched; charset=us-ascii to edit the content-type manually, enter Ctrl-T when composing a message (outside the editor). I'm using Mutt 1.5.21. Oh well. I was just trying to remember what it was, so that's covered. I don't know why I remember it having a 4-letter acronym, though, unless I'm just remembering it wrong (which, after my first cancer, is ALWAYS a solid possibility). Thanks, --jim /etc/mime.types on debian doesn't mention any filename extensions for text/enriched. that makes sense. it only ever existed inside mail messages, not in separate files with their own extensions. cheers, raf
Re: Old e-mail markup language RFC ?
m...@raf.org wrote: Jim Graham wrote: I'm not sure of the exact year, but somewhere around 1996--1997, I was using an e-mail markup language that was similar in some respects to html, but it wasn't html. It was limited to simple text markup such as bold, simple colors, *maybe* italic and underline (don't remember), and if I remeember correctly, not much else. Does anyone remember what that is (or was) called, and/or what the RFC for it is? I do remember that Mutt supported it (and it was one of the very few that did). Thanks, --jim hi jim, it was probably text/richtext (not application/x-rtf). oops. i mean text/enriched. the rfc is http://tools.ietf.org/rfc/rfc1523.txt eudora knew about it as well. cheers, raf
Re: Old e-mail markup language RFC ?
Jim Graham wrote: On Wed, Sep 19, 2012 at 02:32:59PM +1000, m...@raf.org wrote: m...@raf.org wrote: Jim Graham wrote: I'm not sure of the exact year, but somewhere around 1996--1997, I was using an e-mail markup language that was similar in some respects to html, but it wasn't html. It was limited to simple text markup such as bold, simple colors, *maybe* italic and underline (don't remember), and if I remeember correctly, not much else. Does anyone remember what that is (or was) called, and/or what the RFC for it is? I do remember that Mutt supported it (and it was one of the very few that did). it was probably text/richtext (not application/x-rtf). oops. i mean text/enriched. the rfc is http://tools.ietf.org/rfc/rfc1523.txt I thought I remembered it having an FLA like HTML, only different. I could be wrong, though...it's been a long time. And I did stumble across text/enriched, and either my little test was broken, or Mutt no longer supports it. Is it a dead RFC? Thanks, --jim according to wikipedia (no citation): As of 2012, enriched text remained almost unknown in e-mail traffic, while HTML e-mail is widely used. the latest rfc is rfc1896 from 1996 in the legacy stream. it sounds deadish. but my sister was using it with eudora3 until a few months ago (believe it or not). the last text/enriched email i have in my inbox was from 22 Apr 2009 (i started translated them automatically upon arrival to plain text so i probably received some since then) and mutt definitely still knows what it is and renders it sensibly. at least my Mutt 1.5.21 (2010-09-15) on my ubuntu-11.04 system at home can render it but my Mutt 1.5.20 (2009-06-14) on a debian-6.0 system doesn't render it at all. that's odd. they have the same compile options but different patches. according to http://www.mutt.org/doc/manual/manual-5.html, mutt supports text/enriched internally so it should always work. cheers, raf
Re: regexp and pattern limit
Cameron Simpson wrote: You need double backslashes because two things are happening. [...snip...] the best computing advice i've ever had was: Double the number of backslashes! - John Mackin he didn't even know what my problem was when he said it but he was right. if it doesn't fix your problem, you just haven't doubled the number of backslashes enough times. :-) the most backslashes i've ever needed was 16 (in an insanely useless and insanely expensive content management system with many languages nested inside each other). cheers, raf
Color difference between 'mutt' and 'screen -t mutt'
Hello, all, I've set most colors in mutt to red on black (for night vision reasons), when I start mutt directly by $ mutt I get http://tx0.org/2qx but when I open it 'in a new tab' in screen via $ screen -t 'mutt' mutt I get the expected http://tx0.org/2qy What on Earth can be going on? Sincerely yours, John B. -- I guess I'm gonna fade into Bolivian. -Mike Tyson ___ http://jbaber.freeshell.org
/sent: Permission denied (errno = 13)
hi, mutt-1.5.20 debian-6.0 i have the following system account in /etc/passwd: nut:x:104:107::/var/lib/nut:/bin/false when it sends email from a script using mutt: mutt -s `hostname` $1 root /dev/null it outputs the following error message: /sent: Permission denied (errno = 13) which indicates that mutt wasn't looking in /etc/passwd to get the user's home directory (i.e. /var/lib/nut) and so it used the current directory (which was /) as the directory in which to create the sent file. i thought that perhaps the fact that the nut user's home directory was owned by root might be the problem but changing its ownership to nut didn't help. to get the email working i needed to add set copy = no to a system Muttrc file because there's obviously no point putting it in the nut user's own ~/.muttrc file if mutt can't find the nut user's home directory which contains the .muttrc file. to me, this looks like two bug-like entities: 1) mutt can't find this user's home directory, 2) mutt abandons sending the email just because it can't save a copy of it as well. 2 may be justifiable but 1 is just wierd. it's almost as if mutt is only looking at $HOME rather than looking in /etc/passwd to identify the home directory but that can't be the case. mutt is too smart for that. $HOME could be set to anything or not set at all. ah, the manpage says the following in the ENVIRONMENT section: HOME Full path of the user's home directory. so it must just be using $HOME. in accordance with the principle of least astonishment, i'd like to suggest that when $HOME is unset, mutt look up the home directory in /etc/passwd (i.e. getpwuid() - pw_dir). this is an error that shouldn't ever have to happen. cheers, raf
Re: how to get Fccs of replies?
On Tue, Jan 18, 2011 at 08:59:52PM -0400, Monte Stevens wrote: On Tue, Jan 18, 2011 at 03:22:01PM -0800, travis+ml-m...@subspacefield.org wrote: Hey all, When I reply to emails from other people, they don't end up Fcc'd to =.sent, but when I compose them, or reply to myself, they do. Anyone got a guess as to why? Please provide the following muttrc variables: record, save_name and force_name, as well as all hooks, particularly save-hook, fcc-hook and fcc-save-hook. /home/travis/.mutt/muttrc:set record=+.sent # default location to save outgoing mail /home/travis/.mutt/muttrc.gpg:send-hook . 'set pgp_autosign=yes; set pgp_autoencrypt=no' /home/travis/.mutt/muttrc.gpg:send-hook '~t .*-request@.*''set pgp_autosign=no; set pgp_autoencrypt=no' /home/travis/.mutt/muttrc.gpg:send-hook '~t .*-owner@.*' 'set pgp_autosign=no; set pgp_autoencrypt=no' /home/travis/.mutt/muttrc.gpg:send-hook '~t owner-.*@.*' 'set pgp_autosign=no; set pgp_autoencrypt=no' /home/travis/.mutt/muttrc.gpg:send-hook '~t majordomo@.*' 'set pgp_autosign=no; set pgp_autoencrypt=no' /home/travis/.mutt/muttrc.gpg:send-hook '~t .*subscribe.*@.*' 'set pgp_autosign=no; set pgp_autoencrypt=no' /home/travis/.mutt/muttrc.local:set alternates=^(travis(\\+.*)?@subspacefield.org|somethingelsehere)$ /etc/mutt/Muttrc.local:set record=+.sent Does the 'alternates' command not do what you are trying to accomplish with muttedit? Maybe the backslashitis was the problem; I always get basic and extended regex syntax confused. Two backslashes seems wrong; I'll try one and see. -- http://www.subspacefield.org/~travis/ This email was brought to you by the bits 0 and 1. If you are a spammer, please email j...@subspacefield.org to get blacklisted. pgpsIVdZvfgPg.pgp Description: PGP signature
how to Fcc replies (not just compositions)?
Wondering how to do make copies of all outbound emails, not just new compositions. -- http://www.subspacefield.org/~travis/ He who lives by the computer, dies by the computer. If you are a spammer, please email j...@subspacefield.org to get blacklisted. pgp34zfg6bk7V.pgp Description: PGP signature
how to get Fccs of replies?
Hey all, When I reply to emails from other people, they don't end up Fcc'd to =.sent, but when I compose them, or reply to myself, they do. Anyone got a guess as to why? It may have something to do with my muttedit script, which I use to set the From address when replying see my Ultimate Email Config paper here for the script and rationale, you might like it: http://www.subspacefield.org/~travis/email_config/ Although, I'll be a little embarrassed if muttedit is why my replies aren't getting saved. If you woulnd't mind, if you find hte problem, CC me directly and the list optionally, since I want this fixed ASAP. -- Effing the ineffable since 1997. | http://www.subspacefield.org/~travis/ My emails do not usually have attachments; it's a digital signature that your mail program doesn't understand. If you are a spammer, please email j...@subspacefield.org to get blacklisted. pgpxMAvRC5bJ7.pgp Description: PGP signature
Re: How to match all theaded emails excluding the first one?
On 10.09.20, Yue Wu wrote: P.S., how does mutt dertermine threads? Maybe it's better and more reliable than the ~s Re: way? For correct threads, i.e. if the user hasn't chosen to use just the subject line, it uses References: which refer to the message-id of the mail(s) to which it is responding. Do H and look at the headers and you'll see under References: 20100919012315.gc36...@fbsd.t60.cpu 20100919071840.ga26...@murdoc etc. Kind regards Michael
Re: How to match all theaded emails excluding the first one?
On 10.09.20, mjsseppl-m...@yahoo.de wrote: On 10.09.20, Yue Wu wrote: Do H and look at the headers and you'll see under References: 20100919012315.gc36...@fbsd.t60.cpu 20100919071840.ga26...@murdoc etc. In-Reply-To: is also used. Kind regards Michael
Re: How to get the current folder in a macro and pass i to a Script? [WAS: Taking notes using Mutt threads]
On 10.08.31, Michelle Konzack wrote: But you can nothing use as a parameter for a script called from a macro. You can not even use: my_hdr Fcc: ^ which should save the message you are curently writing in the CURRENT mailfolder. I can't get that to work at all - even as a general default, let alone as part of a macro. my_hdr Fcc: ^ does nothing. Michael
Re: How to get the current folder in a macro and pass i to a Script? [WAS: Taking notes using Mutt threads]
Sorry - my bad. As you probably noticed, I was using an old version of mutt - I upgraded my OS, but the new upgrade had the old version of Mutt. everything's ok now - and the note taking works fine - thanks to all the contributors to this thread :) Michael
Re: Taking notes using Mutt threads
Hi, Jose. That is a very interesting set up you have and it would be great if you could post the relevant parts of your muttrc file and the configuration of Postfix. I don't use Postfix - I use Msmtp and Procmail - but I hope that I can configure Msmtp to do the same as Postfix. In any case, your idea has really got me thinking, which is good, since it has been a long time since I have had cause to look at the way I have my mail system set up. kind regards Harry. On 10.08.29, j...@telefonica.net wrote: Hi, friends. Mutt is marvellous, I start with it only some days ago and now I have configured it very very funtional to my taste. Now I use it also to Take Notes. I made an alias for Postfix to send mails to a black hole, /dev/null so I can send clean mails to a phantom address in aliases no...@localhost and with a fcc-hook all of them go to mailbox =notes I have mutt with set sort=reverse-threads so I can see my Notes threads with nice sorting and order. Reply to a Notes Subject is a new note about it. I can have as many Subjects as I will need. I can Search in body notes or Subject. With a macro F12 show me the =notes mailbox. I choose to have all my important writings in pure text, it is universal, faster than other, so I will be always able to read and edit my papers, and Notes with Mutt is pure text. If someone find it useful, please, don't doubt to ask me about config. Best regards. Jose -- Jose Angel Navarro Cortes email: j...@telefonica.net web: http://janc.es/ Usuario Linux: #49178
Re: Taking notes using Mutt threads
On a more general level, regarding Jose's idea: What are the ways to send local messages so that they end up in the mail spool file? It seems to me a simple question and I seem to remember being able to do it, but now when I try to remember how I did it, I can't find the way. There's a discussion of the problem, in french, here: http://linuxfr.org/forums/10/6606.html where they sum up the problem as a mail server without a mail server. The best solution they came up with, it seems to me, was using getmail_mbox or getmail_maildir, and putting that in a script and putting set sendmail=/path/to/my/myscript.sh presumably as part of a hook, in the rc file. Any ideas? Harry On 10.08.29, j...@telefonica.net wrote: Hi, friends. Mutt is marvellous, I start with it only some days ago and now I have configured it very very funtional to my taste. Now I use it also to Take Notes. I made an alias for Postfix to send mails to a black hole, /dev/null so I can send clean mails to a phantom address in aliases no...@localhost and with a fcc-hook all of them go to mailbox =notes I have mutt with set sort=reverse-threads so I can see my Notes threads with nice sorting and order. Reply to a Notes Subject is a new note about it. I can have as many Subjects as I will need. I can Search in body notes or Subject. With a macro F12 show me the =notes mailbox. I choose to have all my important writings in pure text, it is universal, faster than other, so I will be always able to read and edit my papers, and Notes with Mutt is pure text. If someone find it useful, please, don't doubt to ask me about config. Best regards. Jose -- Jose Angel Navarro Cortes email: j...@telefonica.net web: http://janc.es/ Usuario Linux: #49178
Re: mutt and newsletters
cat groupA groupB |sort |uniq groupC straightforward and simple. sort -u groupA groupB groupC HTH ;-)
Directory selection list to save attachment(s)
Hi, After pressing 'v' to view list of attachments, select the attachment then hit 's', backspac over the filename then hit TAB to get a directory list, it is possible to navigate the directory list but I cannot see how to make a directory selection. 'q' does exit the list but it does not maintain the directory selection. Is it possible to select from the directory list when saving an attachment? Thanks.
Re: Directory selection list to save attachment(s)
Don't backspace over the filename unless you want to change it. The tab key will initiate the directory selection listing and allow you to navagate thru the tree. Hitting the enter key will open/select the directory you choose and append it to the filename. ok thanks, I get that much. But how do you exit the directory list? Hitting enter goes into that directory - this is how I navigate from ~/ down until the desired directory is reached. Hitting q exits the directory list but the selection is not maintained. I should mention this is with Mutt 1.5.9i (2005-03-13) Perhaps it is not possible to do what I want?
admin question
hi, sorry for off topic post... could someone tell what is the contact for the moderator/admin of this list. thanks
Re: Mailbox is unchanged
On 2009-05-07 13:05:09, Rocco Rutte wrote: Please read: http://dev.mutt.org/hg/mutt/raw-file/tip/UPDATING when updating mutt. It lists incompatible changes during the development cycle. There you'll find a note about the default value for $move having changed to no so mutt no longer will move mails by default (or ask). Maybe 'set move' in .muttrc does help? Thank you! That got it. I didn't even know UPDATING existed. I'll remember to check that in future..
Re: Mailbox is unchanged
Hi. I've still not got to the bottom of this problem. My spool now has 200 read emails that I can't get mutt to move. Here is my .muttrc: #--- # headers ignore from received content- mime-version status x-status message-id ignore sender references return-path lines #--- # folders set folder=~/mail set mbox_type=Maildir set mbox=+`date +%Y`/`date +%m`_inbox set record=+`date +%Y`/`date +%m`_outbox set postponed=+postponed mbox-hook spool =`date +%Y`/`date +%m`_inbox set realname= set reverse_name=yes set reverse_realname=no #--- # globals set abort_nosubject=no set allow_8bit set ascii_chars=yes set charset=`locale charmap` set confirmappend=no set copy=yes set date_format=%Y-%m-%d %H:%M:%S set edit_headers set editor=vim set fcc_clear=yes set hostname=logik.internal.network set index_format=%.3C %S | %(%Y-%m-%d %H:%M:%S) | %-12.12a | %-12.12t | %-4.4c | %s set markers set pager=builtin set pager_context=1 set pager_format= msg %C set pager_index_lines=12 set pager_stop set smart_wrap set sort=threads set spoolfile=+spool set status_format=-- (%n/%o/%m) %l set status_on_top set strict_threads set tilde set user_agent=no unset collapse_unread # Any ideas why this might suddenly be happening? As I mentioned before, my mutt config hasn't changed in years so I'm mystified as to why this should happen now.
Mailbox is unchanged
Hi. A problem seems to have started recently: Mutt seems to think that my mailbox is always unchanged. I have around 100 read emails in my spool (and growing) and when pressing '$' to sync, mutt just says Mailbox is unchanged. I use maildir. Mail is delivered to a local spool (~/mail/spool) and then saved into maildirs organized by month/year (~/mail/2009/04_inbox). $ mutt -v Mutt 1.5.19 (2009-01-05) Copyright (C) 1996-2009 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: FreeBSD 6.4-RELEASE-p1 (i386) ncurses: ncurses 5.6.20080503 (compiled with 5.6) libiconv: 1.11 Compile options: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE -USE_FCNTL +USE_FLOCK +USE_POP +USE_IMAP -USE_SMTP +USE_SSL_OPENSSL -USE_SSL_GNUTLS -USE_SASL -USE_GSS +HAVE_GETADDRINFO +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID -USE_HCACHE -ISPELL SENDMAIL=/usr/sbin/sendmail MAILPATH=/var/mail PKGDATADIR=/usr/local/share/mutt SYSCONFDIR=/usr/local/etc EXECSHELL=/bin/sh -MIXMASTER To contact the developers, please mail to mutt-...@mutt.org. To report a bug, please visit http://bugs.mutt.org/. muttrc: ignore from received content- mime-version status x-status message-id ignore sender references return-path lines set folder=~/mail set mbox_type=Maildir set mbox=+`date +%Y`/`date +%m`_inbox set record=+`date +%Y`/`date +%m`_outbox set postponed=+postponed mbox-hook spool =`date +%Y`/`date +%m`_inbox set realname= set reverse_name=yes set reverse_realname=no set abort_nosubject=no set allow_8bit set ascii_chars=yes set charset=`locale charmap` set confirmappend=no set copy=yes set date_format=%Y-%m-%d %H:%M:%S set edit_headers set editor=vim set fcc_clear=yes set index_format=%.3C %S | %(%Y-%m-%d %H:%M:%S) | %-12.12a | %-12.12t | %-4.4c | %s set markers set pager=builtin set pager_context=1 set pager_format= msg %C set pager_index_lines=12 set pager_stop set smart_wrap set sort=threads set spoolfile=+spool set status_format=-- (%n/%o/%m) %l set status_on_top set strict_threads set tilde Any help would be appreciated.
Re: Mailbox is unchanged
On 2009-04-27 19:45:13, Grant Edwards wrote: On 2009-04-27, Kyle Wheeler kyle-m...@memoryhole.net wrote: On Monday, April 27 at 08:17 PM, quoth m...@coreland.ath.cx: A problem seems to have started recently: Mutt seems to think that my mailbox is always unchanged. Why is that a problem? OK, well, it's beginning to become a problem because now for some reason mail is piling up in my spool and refuses to go anywhere even after being read. I'm not sure why this has started happening now as my mutt config has gone unchanged for over two years.
Re: config file
signature is indeed verified.. Okay... And then there is an attachment (as seen from Outlook 'ATT00076.dat' which has : You're using Outlook as your reference? So how can we have this embedded in the body of the mail itself ? Uh... Most folks *don't* want that in the body of the mail itself. But you can force it; try adding the following to your muttrc: auto_view application/pgp-signature And then add the following to your mailcap: application/pgp-signature; cat %s; copiousoutput and have the name of the file attachment changed to 'signature.asc' You don't want to do this. See the mailing list archives for the full discussion of why mutt doesn't specify a filename (hint: it's not really a file, it's part of the MIME structure). When you send a mail, I can see in the body: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 -BEGIN PGP SIGNATURE- ... -END PGP SIGNATURE- I would like to have the same format..in the body of the mail itself A, I see. You want old-style signatures. Add the following to your muttrc: set pgp_autoinline=yes Generally, though, old-style signatures (which I use for this mailing list, because I'm often assisting people with broken email clients or configurations) have some pretty severe drawbacks. For example, it's impossible to sign your attachments, or to deal with non-ASCII email (there are some hacks, but they're unreliable workarounds for dealing with broken clients and are only applicable to specific ASCII-like character sets). As another example, the email that I'm replying to included some bits that looked like the old-style signatures, but were invalid. Email clients that attempt to verify old-style signatures will take one look at that and scream FORGED EMAIL!, and may refuse to display your email at all. You cannot include that kind of data in the body of your email and use old-style signatures, otherwise your message risks being considered corrupt by savvy email clients (I had to jump through a few hoops in order to make mutt display your corrupt message). Thankfully, most pgp programs will try to prevent you from doing stupid things like that, and will mangle your messages in order to prevent invalid messages. But my point stands. With the exception of mailing lists where I may be dealing with people with broken mail clients (such as this one), I recommend avoiding that old style of PGP signature. It's intrusive and not very capable. PGP/MIME (the newer style of PGP signature) is MUCH better, and neatly avoids all those problems. The only reason I use them for this list is because some ancient versions of Outlook Express get confused by the PGP/MIME signature and refuse to display the message (which is idiotic, but that's Microsoft for you), but whenever I have to send something in a non-ASCII character set, I switch back to PGP/MIME. ~Kyle
configuration tips
Hi, I admin a box a number of people use for shell access and reading email. I've installed w3m, gpg, and mutt. I use the default Muttrc, but include Muttrc.local, which has this: set mbox_type=Maildir set folder=~/Maildir set mask=!^\\.[^.] set mbox=+.read set record=+.sent set postponed=+.postponed set spoolfile=~/Maildir/inbox auto_view text/html set editor=nano source /usr/local/share/examples/mutt/gpg.rc Also, the default mailcap has: text/html; w3m %s; nametemplate=%s.html text/html; w3m -dump %s; nametemplate=%s.html; copiousoutput Are there any other system-wide settings that I should consider configuring for my users? I'm interested in giving them a functional, useful, relatively secure configuration out of the box, but without enabling any features that they may want to disable but couldn't. So far it seems pretty easy for users to undo any config changes I make, with few exceptions. In particular, viewing HTML emails is a pain. The w3m -dump won't let you browse, and viewing images is obviously impossible. Also, attachments are a pain; you can't save locally. I will add another box with IMAP support, but I've seen a number of people who try to brute-force account passwords through POP/IMAP and I don't want this happening on this box (we use only key-based authentication with SSH). -- https://www.subspacefield.org/~travis/ I need a better strategy for being less analytical. For a good time on my email blacklist, email [EMAIL PROTECTED]
Re: Online Address book
Hi, Thanks for your reply. ldap is running on my vServer. But I am not sure how to setup lbdb to use ldap and mutt to use lbdb. Any advise where to look? Thanks! Nathan On Mon, Feb 11, 2008 at 09:04:00PM -0500, Raffi Khatchadourian wrote: On Tue 12.Feb'08 at 1:43:25 +0100, Nathan Huesken wrote: I am using mutt from different computers (like my laptop and the desktop PC at home) and I am wondering if there is some way to always keep my address book synchronized between the two computers. The coolest solution would be, if I could install some sort of database on my vServer and make mutt query it everytime I need the address book (and also add new addresses to it). Is there some sort if solution for this kind of think? Using LDAP and lbdb kinda solves this problem.
Re: DOS text file attachments.
I think the point that the people on the Postfix mailing list were trying to make is that the MUA (in this case mutt) should not be sending something to the MTA that is marked as text/plain, but has CRLF line endings since text/plain on Unix has just LF line endings. Me, I don't know what should do what with what for this type of file. If it is converted by the MUA to have just LF line endings then the Windows PC I'm sending it to will still see it as a DOS text file since the MTA has to convert it to CRLF for the smtp protocol. Then again if the MTA noticed that the lines already had CRLF on the end and didn't convert it then that would work too. Also if the libmagic stuff noticed that a file was DOS text and reported it as application/octet-stream then I guess that would work too. Maybe I just tell mutt to use a shell script as the MTA and I get that to convert all text to LF line endings then pass it on to the real MTA. Would that work ? I assume all data from mutt to the MTA will be text ? i.e. already be base64 encoded if needs be ? Thanks everyone or your help. Scott. On Tue, Feb 05, 2008 at 12:08:07PM -0600, Kyle Wheeler wrote: On Tuesday, February 5 at 04:35 PM, quoth Michael Kjorling: On 5 Feb 2008 10:00 -0600, by [EMAIL PROTECTED] (Kyle Wheeler): The best way to send a DOS file, if it needs to *stay* a DOS file, is to compress it (e.g. to zip it) and send the compressed form. When it is decompressed, it will return to its original DOS form. This will obviously work. I was wondering though, if sent as an application/octet-stream MIME part, shouldn't the file be encoded by mutt in such a way that it can get reconstructed accurately on the receiver side? Yes, I know that calling plain text a/o-s is a borderline case, but sometimes compressing might not really be an option. (Say, if the recipient might want to read the attachment on a cell phone or PDA, which may not even be able to uncompress formats taken for granted on PCs.) Perhaps, though there are two considerations to that: first, encoding as a/o-s is a common spammer trick that most people do not employ (so it may get your message tagged as spam), and second, there's no guarantee that a cell phone or PDA can decode base64 either. Lastly, why would someone send a DOS text file to a cell phone (that's incapable of doing simple things like decompress zip files) in the first place? ~Kyle -- What progress we are making. In the Middle Ages they would have burned me. Now they are content with burning my books. -- Sigmund Freud
DOS text file attachments.
Hello I am having a problem sending a DOS text file as an attachment. I am running mutt version 1.5.11 on Linux, my MTA is Postfix. When I attach a DOS text file the mime type is text/plain and the encoding is 7bit. When the person at the other end (I get the same results sending it to myself) opens the attachment all lines are double spaced, i.e. each line has an extra CRLF on the end (when received on Linux it has 2 LFs on the end of each line rather than one). I have done some digging and it seems that postfix (the MTA) converts the LF at the end of each line into a CRLF so each line of the attachment ends up with CRCRLF, then something on the server adds the LF in the middle. I suspected that this was a postfix problem and so emailed the postfix list, discuss can be found here : http://groups.google.com/group/list.postfix.users/browse_thread/thread/4b881735fc266c39 which shows most of it. The summary of this is that since I am running on Linux text/plain MUST have unix line endings rather than DOS and so Mutt should convert the CRLF to LF before sending the file to the MTA. I was wondering what the mutt users thought about this.and if they could help me with my problem. Thanks Scott.
Mutt transport problem
Hi Mutters, I have been using Mutt for several years, but recently came across a deliver problem that relates to Mutt. On my home LAN, I just set up a separate mail server on another box, and removed it off of my main machine. In doing so, I removed Postfix from my machine, as I have no need for it, as the mail server with qmail now takes care of all the LAN's mail. However, I have no transport mechanism to move mail from Mutt to the mail server. How have others accomplished this. Previously, the small oem sendmail from Postfix would send the mail from Mutt. Any ideas greatly appreciated. -- Best regards, Today's thought: When you come to a fork in the road, take it!
Re: Mutt transport problem - stmp spken here?
Hi Sven, On Monday, September 9, 2002, 7:33 PM, you put forth, in part, about Mutt transport problem - stmp spken here?: I have no transport mechanism to move mail from Mutt to the mail server. How have others accomplished this? S install a really simple smtp speaking client like S nullmailer or ssmtp. (there were more, but.. 02:32am..) Perfect, just what I need. Thanks Sven... oh, and good night g -- Best regards, Gary How do you tell when you run out of invisible ink?
Cygwin mutt barfs on spaces in set variable?
I am having a problem setting variables whose contents should contain (one or more) spaces. I don't know if it is something I am doing wrong or what is going on. Here is an example: folder-hook mutt set from=Gary Jones my@emailaddress to which mutt says Jones: unknown variable when I enter the folder. Is it me? Is there a solution? Here is some info which may or may not be useful: $ mutt -v Mutt 1.2.5i (2000-07-28) [..] System: CYGWIN_98-4.10 1.3.12(0.54/3/2) [using ncurses 5.2] Compile options: -DOMAIN -DEBUG -HOMESPOOL -USE_SETGID -USE_DOTLOCK +USE_FCNTL -USE_FLOCK +USE_IMAP -USE_GSS +USE_SSL +USE_POP -HAVE_REGCOMP +USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP +BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS TIA. -- Gary
Re: Cygwin mutt barfs on spaces in set variable?
Lee J. Moore [EMAIL PROTECTED] wrote: On Sun, 07 Jul 2002, [EMAIL PROTECTED] wrote: Here is an example: folder-hook mutt set from=3DGary Jones my@emailaddress Try: folder-hook mutt set from=3D'Gary Jones my@emailaddress' Coo, that works fine! TVM! Why is the other way not acceptable? That seems to be the way that the example .muttrcs have. ___ The FREE service that prevents junk email http://www.mailshell.com
Cygwin mutt barfs on spaces in set variable?
I am having a problem setting variables whose contents should contain (one or more) spaces. I don't know if it is something I am doing wrong or what is going on. Here is an example: folder-hook mutt set from=Gary Jones my@emailaddress to which mutt says Jones: unknown variable when I enter the folder. Is it me? Is there a solution? Here is some info which may or may not be useful: $ mutt -v Mutt 1.2.5i (2000-07-28) [..] System: CYGWIN_98-4.10 1.3.12(0.54/3/2) [using ncurses 5.2] Compile options: -DOMAIN -DEBUG -HOMESPOOL -USE_SETGID -USE_DOTLOCK +USE_FCNTL -USE_FLOCK +USE_IMAP -USE_GSS +USE_SSL +USE_POP -HAVE_REGCOMP +USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP +BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS TIA.
Copying from one header to another
Hi, Can mutt copy the contents of one header to another one? I have many different e-mail addresses on my machine, all of which get read at a single account. Some of those addresses are for mailing lists, for example, at this mailing list I use [EMAIL PROTECTED] When I reply to the list I have to manually type in the address that the mail was sent to. My MTA puts a header at the top with the delivery address: Envelope-to: [EMAIL PROTECTED] I want to take that delivery address and put it into the From: header automatically without having to type each one in by hand. If this is not an appropriate thing for Mutt to be doing, please give me a pointer as to how to solve this problem. I'm a relatively new e-mail admin and am still learning. -- Patrick Draper| Don't |[EMAIL PROTECTED] Austin, Texas | Fear |Father Order runs at a http://www.pdrap.org | The|good pace, but old Mother Be Microsoft Free - Use Linux |Penguin |Chaos is winning the race.
AW: AW: IMAP to Exchange
Unless you can come up with how it's already been done, I don't expect that you'll find it. Public Folders and news are not the same as mail. Hm, with Netscape and Imap i have no problem at all, browsinf reading and writing fron the Public Folders. Unfortunatly the first level is also possible with mutt, so to say i can already do reading and writing in public Folders with mutt, but only to a certain level of subfolders. Netscape has no Problem with that. If you can telnet to the IMAP port on the exchange server and somehow have a news article displayed to you, then document that clearly and let us know and we'll go from there. Unfortunatly i didn´t manage to switch to the right folders on the command line. Maybe there is a way to collect the mails via fetchmail. Otherwise there will be no ways around Netscape or Outlook on Win2k. Never thought this could be so difficult with mutt Thanks anyway
