Re: Mise en place de balise dans le sujet
On Wed, Sep 11, 2002 at 10:42:55AM +, Kiouk wrote: Bonjour, Je vous écris afin de savoir si il était possible de mettre automatiquement une balise type [mutt-user-fr] dans le sujet des mails de la liste afin de pouvoir les distinguer du reste du courrier que l'on reçois. la meilleure manière de distinguer une ML du reste c'est encore de la mettre dans une boîte séparée, de plus ça permet de mettre des hooks adequats basés sur la boîte -- Bernard Massot msg00049/pgp0.pgp Description: PGP signature
collapse + pager_index_lines
Blop, Voici ma question: j'utilise set pager_index_lines=10 je vois donc un peu mes thread etc. je voudrais pouvoir les collapses (avec esc+v) sans quitter le preview de msg. quelqu'un vois ? :) -- +, MichouX Et Dieu se retourna et contempla son Oeuvre Et Il dit : Et mrde !
Re: collapse + pager_index_lines
Salut, Sébastien MICHEL a écrit : Voici ma question: j'utilise set pager_index_lines=10 je vois donc un peu mes thread etc. je voudrais pouvoir les collapses (avec esc+v) sans quitter le preview de msg. quelqu'un vois ? :) Une solution avec macros : macro pager \ev exitcollapse-threadnext-undeleteddisplay-message macro pager \eV exitcollapse-allnext-undeleteddisplay-message Sinon il y a un patch tout frais d'aujourd'hui : http://marc.theaimsgroup.com/?l=mutt-devm=103180985207302w=2 Je résume brièvement en français : * remplacement de collapse-thread et collapse-all qui sont actuellement des /bascules/ par quatres fonctions a sens unique : collapse-thread, collapse-all, uncollapse-thread et uncollapse-all. * fonctions de repliement ci-dessus accesssibles à la fois de l'index et du pager. Voilà, -- Cédric
Re: Mise en place de balise dans le sujet
* Cedric Duval [EMAIL PROTECTED] (20020912 16:22): Je ne pense pas que Sender doit-être utilisé pour ça, car il es modifié dans certains cas (par exemple, des email que je forward automatiquement d'une adresse email à une autre change le Sended:) b bounce-message renvoyer un message à un autre utilisateur Je pense qu'il parle d'un .forward installé sur un compte Unix, ou de manière générale d'un alias au niveau du serveur de mail. olive -- Ultrix just isn't the best version of Unix I've ever worked with. In fact it is the worst version of Unix I've ever worked with.
Re: Mise en place de balise dans le sujet
Olivier Tharan a écrit : * Cedric Duval [EMAIL PROTECTED] (20020912 16:22): Je ne pense pas que Sender doit-être utilisé pour ça, car il es modifié dans certains cas (par exemple, des email que je forward automatiquement d'une adresse email à une autre change le Sended:) b bounce-message renvoyer un message à un autre utilisateur Je pense qu'il parle d'un .forward installé sur un compte Unix, ou de manière générale d'un alias au niveau du serveur de mail. Exact, j'ai manqué le « automatiquement ». Cela dit, le champ d'en-têtes Sender: n'est pas la seule constante. Le List-Unsubscribe: peut aussi servir pour reconnaître la liste : List-Unsubscribe: mailto:[EMAIL PROTECTED]?body=unsubscribe Et il n'y a pas de raisons que celui-ci soit modifié lors d'un forward. -- Cédric
Re: Sourcing scripts, screen flashes.
* Sven Guckes [EMAIL PROTECTED] [2002-09-11 17:23 +0200]: * Ryan Sorensen [EMAIL PROTECTED] [2002-09-10 06:32]: source ~/.mutt/hooks/folder.recip.sh ~/.Mail/lists/| source ~/.mutt/hooks/folder.recip.sh ~/.Mail/people/| * Sven Guckes wrote: source filename source filename| filename foo is *not* a filename, i suppose. * [EMAIL PROTECTED] [EMAIL PROTECTED] [2002-09-11 14:57]: Hi Sven - I'm trying to understand what you meant by this. I'm guessing here - but does the vertical bar have to come at the end of the script name ? Not at the end of the command line ? filename stands for the name of a file. no more - no less. so - is foo bar a filename? or more specifically - is there a file named folder.recip.sh ~/.Mail/lists/ (note the space!) in Ryan's ~/.mutt/hooks directory? my guess is that this *file* does *not* exist. [...] The admirable terseness of UNIX/Linux documentation sometimes cause gaps in understanding which are not apparent to those who are already familiar with the topics being examined. I believe this is one of those times. au contraire. Ryan probably expected that he can use any kind of commmand with parameters in this value. and that's where he would be wrong because the parameter is explicitly described as a *filename*. or does it say put parameters here anywhere? exactly. But it DOES work: source awk -f ~/.mutt/gen_mailboxes.awk ~/.mutt/mailboxes| Nicolas
Re: make install error
Patrick ([EMAIL PROTECTED]) muttered: I get the following error during 'make install' and I don't understand. make[1]: *** No rule to make target mime.h', needed by ttach.o'. Stop. make[1]: Leaving directory /mnt/scratch/KeeP/mutt-1.5.1' make: *** [install-recursive] Error 1 You need to patch mutt-1.5.1. ftp://ftp.mutt.org/mutt/devel/README-1.5.1 HTH, Michael -- I've run DOOM more in the last few days than I have the last few months. I just love debugging ;-) (Linus Torvalds) PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key
Re: Trying to do too much with Mutt?
Ouch! Leaving revelation of the nub of the problem till the attempted solution, was clearly not helpful. Clearer is: In order to provide a history of correspondence, filed by project, on originating laptops and on a server, the two-part goal is to: a) Archive outgoing mail to one of many local mail folders, as selected by an email header. The archive folder name can be left at default or edited while composing the mail. b) Archive the same outgoing mail on a server, directed by *the same header*, either directly or by scripting if necessary. o Relying on the Fcc header fails, because that is stripped when the email is sent, leaving nothing to steer the remote archiving. If there is a way to configure its retention, this would be a clean solution. o Currently, an X-Topic: folder_name header is used to steer remote archiving, with an Fcc header steering local archiving. Employing wetware to synchronise the two at all times, and in all eventualities, is found to stretch its reliability beyond limits. Sven's fcc-hook proposal had been longingly looked at, but the manpage says *filename*, not command. send-hook takes a command, but generating one header from the other is more than I can synthesise from the mutt command set, as yet. (Now if command could be an external post-filter, we'd be cooking!) One way out may be to add the sender to the Bcc, and then perform the Fcc operation by means of procmail processing of the received email. (And accept the unclean dependency.) sven use +name Thanks for this suggestion. I've grepped the mutt and muttrc manpages, and /usr/share/doc/mutt/manual.txt, for +name and all occurrences of name, without locating any such reference. I'll look further, for the significance of this cryptogram. Regards, Erik
Batch mode and content-type
Hello I am a newbie to mutt and would like to use it in a bash script in order to send mails to a list. The script is like: - #!/bin/sh for i in `cat listaMail` do mutt -s All'attenzione del signore $i $i /home/info/mails/mail.html done - The only problem is that mutt always send the mail with a content-type: text/plain, while we would like to send a content-type: text/html. So the receiver sees the source HTML. Is there a way to override this default setting and let us send a personalized content-type? Many Thanks Valerio Daelli
Re: sending as who you've been addressed as.
On Wed, 11 Sep 2002, Michael Elkins wrote:
see $reverse_name in the mutt manual.
So, is there then an easy way to differentiate if an email get's
composed completely from scratch or if an email is simply a reply?
Assume the following:
- I have several email addresses that I receive emails for.
- According to the addresses in the To: field, I set the outbound
address.
- However, if I receive an email to a particular email address,
I would like to set the outbound email address to this one no matter
who will be listed in the To: field.
So far, I handle the From: field and ^^From by send-hooks.
Unfortunately, this overrides also the reverse_name feature for me.
Thanks!
Lukas
--
Lukas Ruf
http://www.lpr.ch http://www.maremma.ch
http://www.{{topsy,nodeos}.net,{promethos,netbeast,rawip}.org}
Wanna know anything about raw ip? Join [EMAIL PROTECTED] on www.rawip.org
imap and new mail
At work I now have mutt set up to properly connect via IMAP to an Exchange server. The problem is, though, that new messages always appear as old and unread. This means that mutt -Z is useless. Is there some adjustment that would have to be made on the server to make new messages appear as new (I know next to nothing about either Exchange or IMAP)? Is there something I can tell mutt to get it to treat old/unread as new, particularly with reespect to the -Z option? --Greg
adding references when resending mail
Sometimes I need to follow-up on some previously sent mail. For instance, I have forgotten to mention something or I have got some new information to add. I want my new mail to get threaded under the original mail. What is the appropriate and easiest way of adding such references. Here, I am not refering to replies or follow-ups on mailing lists. -- Anders Helmersson
Re: imap and new mail
On Thu, Sep 12, 2002 at 10:04:06 -0400, Gregory Seidman wrote: At work I now have mutt set up to properly connect via IMAP to an Exchange server. The problem is, though, that new messages always appear as old and unread. This means that mutt -Z is useless. Is there some adjustment that would have to be made on the server to make new messages appear as new (I know next to nothing about either Exchange or IMAP)? Is there something I can tell mutt to get it to treat old/unread as new, particularly with reespect to the -Z option? Here, with IMAP, I get new messages as expected. But when I reconnect to the server, all the new messages become old messages! This is very annoying, in particular when I have to quit and restart Mutt without having read all the new messages. -- Vincent Lefèvre [EMAIL PROTECTED] - Web: http://www.vinc17.org/ - 100% validated (X)HTML - Acorn Risc PC, Yellow Pig 17, Championnat International des Jeux Mathématiques et Logiques, TETRHEX, etc. Work: CR INRIA - computer arithmetic / SPACES project at LORIA
Re: imap and new mail
* Vincent Lefevre [EMAIL PROTECTED] [2002-09-12 10:12]: Here, with IMAP, I get new messages as expected. But when I reconnect to the server, all the new messages become old messages! This is very annoying, in particular when I have to quit and restart Mutt without having read all the new messages. :unset mark_old (darren) -- Quiet and courteous is often mistaken for kind and polite. -- Andrew Langmead
Re: adding references when resending mail
* Anders Helmersson [EMAIL PROTECTED] [020912 16:10]: Sometimes I need to follow-up on some previously sent mail. For instance, I have forgotten to mention something or I have got some new information to add. I want my new mail to get threaded under the original mail. What is the appropriate and easiest way of adding such references. Here, I am not refering to replies or follow-ups on mailing lists. I may or may not have understood what you mean, but here goes. The simplest way to achieve this is using the same mechanisms as for list mail. Go to the mailbox where your outgoing mail is saved, and reply to your own message (changing the To: Cc: and Bcc: fields appropriately). Make sure you have order=threading activated in the mailbox where you want these followups to be seen. -Johan -- Johan Almqvist http://www.almqvist.net/johan/qmail/
Re: adding references when resending mail - reply
* Anders Helmersson [EMAIL PROTECTED] [2002-09-12 14:08]: Sometimes I need to follow-up on some previously sent mail. For instance, I have forgotten to mention something or I have got some new information to add. I want my new mail to get threaded under the original mail. What is the appropriate and easiest way of adding such references? well - reply to your own mail and add the missing info. you could use the resend-mail command, of course, but that might start a new thread. Here, I am not refering to replies or follow-ups on mailing lists. then what? Sven
Re: [PATCH] display-subject
On Wed, Sep 11, 2002, Jeremy Blosser wrote: The attached patch copies the functionality of the display-address function to display the message subject, by default bound to S. This is useful if your term isn't infinitely wide and/or you have a crowded $index_format. I've been using a version of this since 1.3.2x without any problems; it's pretty much just a copy of the display-address stuff so it should be pretty innocuous. Very useful. Will this be in the main distribution? Seems logical. -Ken
Re: Trying to do too much with Mutt? - yes, too much!
* Erik Christiansen [EMAIL PROTECTED] [2002-09-12 10:22]: In order to provide a history of correspondence, filed by project, on originating laptops and on a server, the two-part goal is to: a) Archive outgoing mail to one of many local mail folders, as selected by an email header. The archive folder name can be left at default or edited while composing the mail. that's still the description of a *solution* - and not that of the problem. b) Archive the same outgoing mail on a server, directed by *the same header*, either directly or by scripting if necessary. you did not mention any header yet, so the same header does not reference it. o Relying on the Fcc header fails, because that is stripped when the email is sent, leaving nothing to steer the remote archiving. Fcc is no header line, anyway. If there is a way to configure its retention, this would be a clean solution. attach your own X-Fcc header then. o Currently, an X-Topic: folder_name header is used to steer remote archiving, with an Fcc header steering local archiving. ok - so you already do that then.. Employing wetware to synchronise the two at all times, and in all eventualities, is found to stretch its reliability beyond limits. wetware? (is there some sexual connotation that i'm not getting?) Sven's fcc-hook proposal had been longingly looked at, .. you mean, multiple copies of one sent mail by use of multiple foldernames in Fcc? ..but the manpage says *filename*, not command. well, - feature. one copy suffices. send-hook takes a command, but generating one header from the other is more than I can synthesise from the mutt command set, as yet. (Now if command could be an external post-filter, we'd be cooking!) how many filters does one need? One way out may be to add the sender to the Bcc, and then perform the Fcc operation by means of procmail processing of the received email. (And accept the unclean dependency.) yep.. a) my_hdr Fcc: default_project_name sven use +name Thanks for this suggestion. I've grepped the mutt and muttrc manpages, and /usr/share/doc/mutt/manual.txt, for +name and all occurrences of name, without locating any such reference. I'll look further, for the significance of this cryptogram. i meant use a '+' sign in front of the folder name, so $folder/name is used rather than './name'. clear now? anyway, i think you should take a look at Gnus - there you can really program it all. the archiving problem leads to databases, backup stategies and synchronization problems. and the MUA is *not* the right tool for it. sorry if this burts your bubble.. Sven
Re: pattern question
Ren? Clerc wrote: is it possible to use patterns to specify a message that is directed to [EMAIL PROTECTED], but not to someone else and not cc'ed to someone else either? Sorry, but I'm no pattern or regexp guru... It depends upon what you're talking about. You can't do this with a regexp by itself, so that means you can't do it for variables like $alternates. However, for searching/hooks you can use Mutt's higher level search pattern to do this: ~[EMAIL PROTECTED] !~[EMAIL PROTECTED]
Re: Batch mode and content-type
vdaelli wrote: The only problem is that mutt always send the mail with a content-type: text/plain, while we would like to send a content-type: text/html. So the receiver sees the source HTML. Is there a way to override this default setting and let us send a personalized content-type? This functionality exists in the Mutt 1.5 branch in CVS. There is now a $content_type variable that lets you set the default content-type for the main body of the message. So you can do things like set the content-type from the command line: mutt -e 'set content_type=text/html' [EMAIL PROTECTED] test.html
Re: sending as who you've been addressed as.
Lukas Ruf wrote: So, is there then an easy way to differentiate if an email get's composed completely from scratch or if an email is simply a reply? Assume the following: - I have several email addresses that I receive emails for. - According to the addresses in the To: field, I set the outbound address. - However, if I receive an email to a particular email address, I would like to set the outbound email address to this one no matter who will be listed in the To: field. So far, I handle the From: field and ^^From by send-hooks. Unfortunately, this overrides also the reverse_name feature for me. Yes, this is a problem. In Mutt 1.5 (CVS) there is now a reply-hook that lets you determine if you are sending a reply or not. It was added to solve exactly this problem.
Re: imap and new mail
On Thu, Sep 12, 2002 at 10:15:04 -0400, darren chamberlain wrote: * Vincent Lefevre [EMAIL PROTECTED] [2002-09-12 10:12]: Here, with IMAP, I get new messages as expected. But when I reconnect to the server, all the new messages become old messages! This is very annoying, in particular when I have to quit and restart Mutt without having read all the new messages. :unset mark_old No, the old messages will be marked as new, and I don't want that. -- Vincent Lefèvre [EMAIL PROTECTED] - Web: http://www.vinc17.org/ - 100% validated (X)HTML - Acorn Risc PC, Yellow Pig 17, Championnat International des Jeux Mathématiques et Logiques, TETRHEX, etc. Work: CR INRIA - computer arithmetic / SPACES project at LORIA
Re: Batch mode and content-type
* vdaelli [EMAIL PROTECTED] [2002-09-12 12:40]: - #!/bin/sh for i in `cat listaMail` do mutt -s All'attenzione del signore $i $i /home/info/mails/mail.html done - The only problem is that mutt always send the mail with a content-type: text/plain, while we would like to send a content-type: text/html. So the receiver sees the source HTML. Is there a way to override this default setting and let us send a personalized content-type? Many Thanks Not exactly what you want, I think, but you could use -a and send it as an attachment instead. -- David Rock [EMAIL PROTECTED] msg30926/pgp0.pgp Description: PGP signature
Re: pattern question
At 12:03 +0200 12 Sep 2002, René Clerc [EMAIL PROTECTED] wrote: is it possible to use patterns to specify a message that is directed to [EMAIL PROTECTED], but not to someone else and not cc'ed to someone else either? ^~C ^[EMAIL PROTECTED]$ The ^ modifier specifies that all addresses must match rather than succeeding if there's at least one match. -- Aaron Schrab [EMAIL PROTECTED] http://www.schrab.com/aaron/ What is the sound of Perl? Is it not the sound of a wall that people have stopped banging their heads against? -- Larry Wall
.mailcap start prog in background
Hi, is it possible to define a .mailcap entry that way, that the viewer runs in the background and mutt is free to work with? I mean something like: image/*; feh -x %s ; TIA sascha -- Sascha Huedepohl [EMAIL PROTECTED]
Re: .mailcap start prog in background
On 2002-09-12 Sascha Huedepohl wrote: Hi, is it possible to define a .mailcap entry that way, that the viewer runs in the background and mutt is free to work with? I mean something like: image/*; feh -x %s ; I use a script named mutt_bgrun for this. Found it somewhere on the net. You can find it with google and also on my homepage http://www.christophmaurer.de/linux/mutt_bgrun Regards, Christoph -- Christoph Maurer - D - 52072 Aachen mailto:[EMAIL PROTECTED] - http://www.christophmaurer.de On my Homepage: SuSE 7.0 on an Acer Travelmate 508 T Notebook
Re: imap and new mail
Vincent Lefevre said: On Thu, Sep 12, 2002 at 10:15:04 -0400, darren chamberlain wrote: * Vincent Lefevre [EMAIL PROTECTED] [2002-09-12 10:12]: Here, with IMAP, I get new messages as expected. But when I reconnect to the server, all the new messages become old messages! This is very annoying, in particular when I have to quit and restart Mutt without having read all the new messages. :unset mark_old No, the old messages will be marked as new, and I don't want that. You don't want them marked as old and unread; you don't want them to stay marked as new (which implies unread), if you exit and restart mutt. What do you want, then? -- PGP Fingerprint: 0AA8 DC47 CB63 AE3F C739 6BF9 9AB4 1EF6 5AA5 BCDF Member, LEAF Project http://leaf.sourceforge.netAIM: MikeLeone Public Key - http://www.mike-leone.com/~turgon/turgon-public-key.asc ( Memoriam ) ;===;() # # # #:: # # # #:: # # # #:: # # # #:: # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # Random Thought: -- Remember thee Ay, thou poor ghost while memory holds a seat In this distracted globe. Remember thee! Yea, from the table of my memory I'll wipe away all trivial fond records, All saws of books, all forms, all pressures past, That youth and observation copied there. Hamlet, I : v : 95 William Shakespeare
Re: adding references when resending mail - reply
well - reply to your own mail and add the missing info. you could use the resend-mail command, of course, but that might start a new thread. What concerns me with this method is that in-reply-to will include my own mail id, even if it is not a reply but a resending of my own mail. Here, I am not refering to replies or follow-ups on mailing lists. then what? One applicable situation could be when I would like to arrange a meeting, with someone (say Beth). However, after sending the first mail, I discover that I forget to say when the meeting is going to take place. I resend the mail with the date and time. I do not consider this as a reply and, thus, In-reply-to should not be set, but only References (according to RFC2076, para 3.6). Though, I may be to restrictive in definition of reply. What I had in mind in my original thinking was to have a quadoption question in the resend function for including the reference of the original mail. That would keep the To: field intact. Anders
removing self from group reply
I know this has come up before, but I can't find it anywhere: When I group reply to a message, is there any way to remove my own address from the recipient list? -- David Rock [EMAIL PROTECTED] msg30933/pgp0.pgp Description: PGP signature
Re: removing self from group reply
David Rock wrote: I know this has come up before, but I can't find it anywhere: When I group reply to a message, is there any way to remove my own address from the recipient list? unset metoo should do what you want. if that doesn't work, perhaps you don't have $alternates set correctly. -- Will Yardley input: william hq . newdream . net .
Re: removing self from group reply
* David Rock [EMAIL PROTECTED] [020912 21:02]: When I group reply to a message, is there any way to remove my own address from the recipient list? Mutt should do this for you if you have set alternates correctly... -Johan -- Johan Almqvist http://www.almqvist.net/johan/qmail/
Re: removing self from group reply
* Johan Almqvist [EMAIL PROTECTED] [2002-09-12 21:10]: * David Rock [EMAIL PROTECTED] [020912 21:02]: When I group reply to a message, is there any way to remove my own address from the recipient list? Mutt should do this for you if you have set alternates correctly... Duh, worked great. Is it just me, or does the Mutt manual not have any direct explanation of how alternates relates to the rest of mutt? for example: 6.3.7. alternates Type: regular expression Default: A regexp that allows you to specify alternate addresses where you receive mail. This affects Mutt's idea about messages from you and addressed to you. 6.3.96. metoo Type: boolean Default: no If unset, Mutt will remove your address from the list of recipients when replying to a message. Neither of these really explains that metoo needs alternates to be set. Maybe metoo should be expounded to include a note stating as much? Thanks again for the help. -- David Rock [EMAIL PROTECTED] msg30937/pgp0.pgp Description: PGP signature
Re: imap and new mail
On Thu, Sep 12, 2002 at 14:12:14 -0400, Michael Leone wrote: Vincent Lefevre said: No, the old messages will be marked as new, and I don't want that. You don't want them marked as old and unread; you don't want them to stay marked as new (which implies unread), if you exit and restart mutt. What do you want, then? I want 4 levels (in the same mailbox, to get the benefit of threading): 1) Messages that mustn't be deleted. 2) Messages I've read but I want to keep for some time. 3) Messages I've read or partly read which I need to read again (e.g. because I need to reply or to look at a URL or whatever). 4) Really new messages. So I use: 1) flagged read 2) read 3) old (or flagged old) 4) new -- Vincent Lefèvre [EMAIL PROTECTED] - Web: http://www.vinc17.org/ - 100% validated (X)HTML - Acorn Risc PC, Yellow Pig 17, Championnat International des Jeux Mathématiques et Logiques, TETRHEX, etc. Work: CR INRIA - computer arithmetic / SPACES project at LORIA
Re: imap and new mail
Vincent Lefevre said: On Thu, Sep 12, 2002 at 14:12:14 -0400, Michael Leone wrote: Vincent Lefevre said: No, the old messages will be marked as new, and I don't want that. You don't want them marked as old and unread; you don't want them to stay marked as new (which implies unread), if you exit and restart mutt. What do you want, then? I want 4 levels (in the same mailbox, to get the benefit of threading): 1) Messages that mustn't be deleted. 2) Messages I've read but I want to keep for some time. 3) Messages I've read or partly read which I need to read again (e.g. because I need to reply or to look at a URL or whatever). Well, mutt can't know that you want to read them again. :-) To mutt, it's read. Whether you want to keep it or not, or want to reply later, is your decision. And so you've flagged them. 4) Really new messages. So I use: 1) flagged read 2) read 3) old (or flagged old) 4) new I'm still not understanding where the problem is. You get new mail; it's flagged as new. You exit mutt. You restart mutt. The message is still flagged as new (presuming that you unset mark_old in your .muttrc). Have you not picked up exactly where where you left off, before you exited mutt? The messages that were flagged as new (meaning unread) are still flagged that way, aren't they? Or are you saying that their status has changed in some other way? You wanted unread mail to still show as unread, even if you exit and restart mutt, or am I misunderstanding what you want? -- PGP Fingerprint: 0AA8 DC47 CB63 AE3F C739 6BF9 9AB4 1EF6 5AA5 BCDF Member, LEAF Project http://leaf.sourceforge.netAIM: MikeLeone Public Key - http://www.mike-leone.com/~turgon/turgon-public-key.asc ( Memoriam ) ;===;() # # # #:: # # # #:: # # # #:: # # # #:: # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # Random Thought: -- Necessity is the plea for every infringement of human freedom. It is the argument of tyrants; it is the creed of slaves. -- William Pitt, 1783
Re: imap and new mail
On Thu, Sep 12, 2002 at 16:15:36 -0400, Michael Leone wrote: Vincent Lefevre said: I want 4 levels (in the same mailbox, to get the benefit of threading): 1) Messages that mustn't be deleted. 2) Messages I've read but I want to keep for some time. 3) Messages I've read or partly read which I need to read again (e.g. because I need to reply or to look at a URL or whatever). Well, mutt can't know that you want to read them again. :-) To mutt, it's read. No, I use the toggle-new command to mark them as new (and they become old when I quit the mailbox with the quit command). You get new mail; it's flagged as new. You exit mutt. You restart mutt. The message is still flagged as new (presuming that you unset mark_old in your .muttrc). No, when using a normal folder (where normal means non-IMAP), it depends on how I quit Mutt. Quit with 'quit' - the new messages are marked as 'old'. Quit with 'exit' (or after setting the folder in read-only mode) - the new messages remain 'new'. This works very well to use the 4 levels, but not with IMAP. -- Vincent Lefèvre [EMAIL PROTECTED] - Web: http://www.vinc17.org/ - 100% validated (X)HTML - Acorn Risc PC, Yellow Pig 17, Championnat International des Jeux Mathématiques et Logiques, TETRHEX, etc. Work: CR INRIA - computer arithmetic / SPACES project at LORIA
Re: adding references when resending mail - reply
* Anders Helmersson [EMAIL PROTECTED] [2002-09-12 18:44]: well - reply to your own mail and add the missing info. you could use the resend-mail command, of course, but that might start a new thread. What concerns me with this method is that in-reply-to will include my own mail id, even if it is not a reply but a resending of my own mail. yes, that's a grave problem, of course.i think... not. One applicable situation could be when I would like to arrange a meeting, with someone (say Beth). However, after sending the first mail, I discover that I forget to say when the meeting is going to take place. I resend the mail with the date and time. I do not consider this as a reply and, thus, In-reply-to should not be set, but only References (according to RFC2076, para 3.6). what does the RFC say about users who want a special technical solution with each possible situation in life then? anything? ;-) Though, I may be to restrictive in definition of reply. loosen up! What I had in mind in my original thinking was to have a quadoption question in the resend function for including the reference of the original mail. That would keep the To: field intact. use resend-message then. use your editor to add the necessary changes. and let the MTA let its work by giving the message a new Message-ID. and don't forget to wear your sun screen! ;-) Sven -- Don't worry about the future; or worry, but know that worrying is as effective as trying to solve an algebra equation by chewing bubble gum.
Re: imap and new mail
* Vincent Lefevre [EMAIL PROTECTED] [2002-09-12 22:31 +0200]:
On Thu, Sep 12, 2002 at 16:15:36 -0400, Michael Leone wrote:
Vincent Lefevre said:
I want 4 levels (in the same mailbox, to get the benefit of threading):
1) Messages that mustn't be deleted.
2) Messages I've read but I want to keep for some time.
3) Messages I've read or partly read which I need to read again
(e.g. because I need to reply or to look at a URL or whatever).
Well, mutt can't know that you want to read them again. :-) To mutt, it's
read.
No, I use the toggle-new command to mark them as new (and they become
old when I quit the mailbox with the quit command).
You get new mail; it's flagged as new. You exit mutt. You restart mutt.
The message is still flagged as new (presuming that you unset mark_old
in your .muttrc).
No, when using a normal folder (where normal means non-IMAP),
it depends on how I quit Mutt. Quit with 'quit' - the new messages
are marked as 'old'. Quit with 'exit' (or after setting the folder
in read-only mode) - the new messages remain 'new'. This works very
well to use the 4 levels, but not with IMAP.
I use the attached patch (with mark_old is unset). But I must admit,
I use it only with local Maildirs.
Nicolas
--- parse.c.ori Wed Oct 31 10:18:28 2001
+++ parse.c Sat Nov 10 16:38:12 2001
@@ -1149,8 +1149,7 @@
hdr-replied = 1;
break;
case 'O':
- if (option (OPTMARKOLD))
- hdr-old = 1;
+ hdr-old = 1;
break;
case 'R':
hdr-read = 1;
--- ori Fri Jul 12 22:47:53 2002
+++ mh.cFri Jul 12 22:47:28 2002
@@ -689,7 +689,7 @@
if (subdir)
{
snprintf (buf, sizeof (buf), %s/%s, ctx-path, subdir);
-is_old = (mutt_strcmp (cur, subdir) == 0) option (OPTMARKOLD);
+is_old = (mutt_strcmp (cur, subdir) == 0);
}
else
strfcpy (buf, ctx-path, sizeof (buf));
Re: imap and new mail
On Thu, Sep 12, 2002 at 23:47:23 +0200, Nicolas Rachinsky wrote: I use the attached patch (with mark_old is unset). But I must admit, I use it only with local Maildirs. What does it do? -- Vincent Lefèvre [EMAIL PROTECTED] - Web: http://www.vinc17.org/ - 100% validated (X)HTML - Acorn Risc PC, Yellow Pig 17, Championnat International des Jeux Mathématiques et Logiques, TETRHEX, etc. Work: CR INRIA - computer arithmetic / SPACES project at LORIA
Re: removing self from group reply
Alas! David Rock spake thus: 6.3.96. metoo Type: boolean Default: no If unset, Mutt will remove your address from the list of recipients Mutt can only know who you are by $alternates. Neither of these really explains that metoo needs alternates to be set. Maybe metoo should be expounded to include a note stating as much? I don't think that is necessary. Perhaps alternates could have a note saying that it must be set for any of the features that depend on who you are to work. -- Rob 'Feztaa' Park http://members.shaw.ca/feztaa/ -- When anyone says `theoretically,' they really mean `not really.' -- David Parnas msg30944/pgp0.pgp Description: PGP signature
Re: removing self from group reply
* David Rock [EMAIL PROTECTED] [2002-09-12 19:32]: * Johan Almqvist [EMAIL PROTECTED] [2002-09-12 21:10]: * David Rock [EMAIL PROTECTED] [020912 21:02]: When I group reply to a message, is there any way to remove my own address from the recipient list? Mutt should do this for you if you have set alternates correctly... Duh, worked great. Is it just me, or does the Mutt manual not have any direct explanation of how alternates relates to the rest of mutt? [..] Neither of these really explains that metoo needs alternates to be set. Maybe metoo should be expounded to include a note stating as much? yes, the manual can be improved. there's *your* chance to help! hint hint hint hint hint hint hint hint hint hint hint hint hint :-) Sven
Mutt support for mixmaster 2.9bxx
Why doesn't mutt support mixmaster 2.9bxx? The mutt manual says: Mixmaster support in mutt is for mixmaster version 2.04 (beta 45 appears to be the latest) and 2.03. It does not support earlier versions or the later so-called version 3 betas, of which the latest appears to be called 2.9b23. The latest release is 2.9b38 (10-Sep-2002), and the 2.9bxx series has been under development since 1998, with the first public release in 1999. Isn't it past time to support it? There is a patch for 2.9b23 at http://lacebark.ntu.edu.au/mutt.html and also a patch for mutt 1.3.10 to use mixmaster nyms, but will they work with 2.9b38 and mutt 1.4? Thanks, -rex
imap/pop w/cyrus virtual domains
After beating my head against the wall for several days, I finally convinced my Exim 4.x MTA to deliver to a [EMAIL PROTECTED]@mydomain.net style address via LMTP to a Cyrus mailstore. I was ecstatic to say the least. And then I go to check everything is working (without having to resort back to the old 'telnet localhost pop3' trick), and what do I fine? Mutt seems to not handle [EMAIL PROTECTED] as a username to a host with either pop3 or imap4!? :( I tried all forms of escaping the @ (at symbol) when prompted for a username, but alas, nothing works. Has this come up before? I didn't find anything in the list archives, but it's hard to search for the at symbol (@) on most search engines. -- Mark Nippere-contacts: Computing and Information Services [EMAIL PROTECTED] Texas AM Universityhttp://arrakis.tamu.edu/nipsy/ College Station, TX 77843-3142 AIM: texasnipsy ICQ: 66971617 (979)575-3193Yahoo: texasnipsy -BEGIN GEEK CODE BLOCK- GG/IT d- s++:+ a-- C++$ UBL+++$ P---+++ L+++$ E--- W++ N+ o K++ w(---) O++ M V(--) PS+++(+) PE(--) Y+ PGP++(+) t 5 X R tv b+++ DI+(++) D+ G e h r++ y+(**) --END GEEK CODE BLOCK-- ---begin random quote of the moment--- Well, I too worry for all young lovers. The darkness is not the light, my child, and there are lights. You are one of the lights, dear Mina, the light of all light. -- Professor Abraham van Helsing, Bram Stoker's Dracula, 1992 end random quote of the moment msg30947/pgp0.pgp Description: PGP signature
Re: adding references when resending mail - reply
On Thu, 12 Sep 2002, Anders Helmersson wrote: well - reply to your own mail and add the missing info. you could use the resend-mail command, of course, but that might start a new thread. What concerns me with this method is that in-reply-to will include my own mail id, even if it is not a reply but a resending of my own mail. Here, I am not refering to replies or follow-ups on mailing lists. then what? One applicable situation could be when I would like to arrange a meeting, with someone (say Beth). However, after sending the first mail, I discover that I forget to say when the meeting is going to take place. I resend the mail with the date and time. I do not consider this as a reply and, thus, In-reply-to should not be set, but only References (according to RFC2076, para 3.6). Though, I may be to restrictive in definition of reply. What I had in mind in my original thinking was to have a quadoption question in the resend function for including the reference of the original mail. That would keep the To: field intact. Anders Hi, set in your .muttrc set copy=ask-yes (if you have changed your default settings). After you recognized that your original mail was wrong or something was missing copy from your mailsent-mailbox the email you want to correct to your postponed mailbox. Then resend it and you are able to correct the missing datas. Oliver -- ... don't touch the bang-bang fruit
