Re: List-Reply
How does this delete the personal copy, but not the list copy? Both messages will have the same Message-ID field in the header. Correct answer, but to the question how does it recognise duplicates. I should have been more specific - what I meant was: how does it delete the personal copy, as opposed to the list copy, or the copy which arrives later? I want to make sure I keep thelist copy... Thanks, Volker -- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.orcon.net.nz Please do not CC list postings to me.
Re: Organizing mailfolders (strategies and using with mutt)
[examples of directory structures] Mutt's default for saving messages seems to revolve around the From address (e.g. mail from [EMAIL PROTECTED] wants to save to ~/Mail/foo). Does anyone have some good ideas about how to manage their mailboxes? What I tried fcc-save-hook (mutt-users.*@mutt.org) =LISTS/appsoft/mutt-users-List fcc-save-hook '~e [EMAIL PROTECTED]' =LISTS/appsoft/mutt-users-List but it's becoming very tidious very fast and is not really the way to go IMHO, esp when using procmail anyway. I have programmed some generic filters for various list servers: http://volker.orcon.net.nz/soft/procmail/ (the files named l_*.rc). The mutt lists then become ### # mutt-announce majordomo LISTNAME=mutt-anno LISTEMAIL=mutt-announce LISTSERVERDOMAIN=(mutt.org|gbnet.net) LISTFOLDER=$THISLISTS/$LISTEMAIL-List INCLUDERC=$PROCDIR/l_majordomo.rc ### # mutt-devmajordomo LISTNAME=mutt-dev LISTFOLDER=$THISLISTS/$LISTNAME-List INCLUDERC=$PROCDIR/l_majordomo.rc ### # mutt-users majordomo LISTNAME=mutt-users LISTFOLDER=$THISLISTS/$LISTNAME-List INCLUDERC=$PROCDIR/l_majordomo.rc ### which is supposed to catch all the list administrative mail as well (subscribe etc). It doesn't work with all lists, there seem to be more differences in server setup than are conveniently allowed, but I'm working on it... Using procmail has the advantage of being mailer-independent, if you want to play around with others (or is saying that here heresy??). Volker -- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.orcon.net.nz Please do not CC list postings to me.
Re: /var/spool/mail/.... is not a mailbox
However, when you make fetchmail deliver directly to procmail, fetchmail does not generate a From line at all, and neither does procmail - big barf results. In that case, use fetchmail - formail | procmail. I believe that this is misleading/incorrect information. I have mda '/usr/bin/procmail -d %T' That's interesting - I would have expected procmail to generate the From_ but it surely didn't with fetchmail --mda 'procmail /dev/null $logfile 21' Perhaps the explicit delivery mode (-d) makes the difference, there's also -f- but you're not using that. But the main thing is we get it working. Volker -- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.orcon.net.nz Please do not CC list postings to me.
AW: IMAP to Exchange
via mapi or imap protocol? Imap I am running: Debian Linux woddy kernel 2.4.7 with imaptool 0.9-4 $ apt-cache search imaptool imaptool - A tool for creating client-side image maps I have also installed imap All folders i have Problems with have subdirectories. In my pager they have IMAP + notation. All with the + down´t work. Unfortnatly i have the problem one step before: I can open several folders, which don´t have any subfolders... For exaple - my own mailbox is no problem (even with subfolders, but when i try to open the Öffentliche Ordner/mailinglists/ many subfolders i get only the message: Getting folder list But when i try to open a mailbox directly located in Öffentliche Ordner/xxx It is no problem, there seems only to be a problem when i try to open/browse subdirs one level below Have you tried both space and enter to select those folders? I am one step before being able to open anything ! I already searched the newsgroups concerning imap and mutt and didn´t find anything helpful. But i am seeking to read my mailinglists and news on exchange with my mutt. Can anyone help !
Re: fork() ?
Michael Elkins [Mon, Apr 15, 2002 at 09:23:59AM -0700]: Nico Schottelius wrote: I am wondering why mutt has to be locked while G-taking pop mails. I think I still could work/send new mails while mutt does this work. I also think that it would be senseful, if I get 500 messages, I could start to answer the first while recieving the last 400. So my question, why don't we easily fork() this process ? You probably want to install fetchmail instead of using Mutt's built in POP3 support. This will give you more flexibility, and allow you to download mail in the background. okay, this will be what I will do soon, but I am wondering why we shouldn't allow mutt to fork out the pop process. Nico -- Nico Schottelius Please send your messages pgp-signed or pgp-encrypted. If you don't know what pgp is visit www.gnupg.org. (public pgp key: ftp.schottelius.org/pub/familiy/nico/pgp-key) msg27297/pgp0.pgp Description: PGP signature
Re: fork() ?
17-Apr-02 at 10:23, Nico Schottelius ([EMAIL PROTECTED]) wrote : okay, this will be what I will do soon, but I am wondering why we shouldn't allow mutt to fork out the pop process. POP3 support seems to be more of an afterthought. Most people who use POP to access their mailboxes swear by fetchmail. Mutt is principally for accessing local spool files, and has reasonable IMAP support too. It would be a shift in the philosophy of Mutt, as I understand it, for Mutt to have full POP support. Problems people have had with POP that I have seen have consistently been told to use fetchmail. There is of course the argument that as soon as native POP support is included in the source tree for Mutt, then it should be a good implementation. That is a question for the developers. The current development team have other priorities for Mutt (and possibly other projects), but if someone wanted to implement POP downloading with forks and so on, then there's nothing stopping them. Already a number of patches are available to extend Mutt functionality... it's your call, if you can improve the POP support, I suppose. Not really my place to say much more than that, until I learn to code in C ;-) -- [Simon White. vim/mutt. [EMAIL PROTECTED] GIMPS:76.07% see www.mersenne.org] Recognizing disagreements in belief requires having enough agreements in belief to translate or understand the words and deeds of my opponent. -- Anthony O'Hear (combining, somewhat, several modern philosophers).
Re: Re: Outlook pst import: What about awk?
Michael,
BRAVO! Worked like a charm! Thank you very much!
This is clearly one for the mutt archives. Congratulations to you.
John
On 04/17/02, 04:59:46PM +0200, Michal 'hramrach' Suchanek wrote:
Yes, the files are identical, you do not need to attach the same thing
twice ;-)
The difference is that while the email contained spaces after the From:
the mailbox contains a tab. There are two lines in the script containing
regexp which identify the From and Sent headers. The From: did not
match From:\t and the from header was not identified. Try changing the
lines like this in the script(only regexps inside quotes changed):
{ if ($0 ~ ^From:\t) {
# ^ here \t stands for tab
# space in original script does not match the tabs found in mailbox
...
if ($0 ~ ^Sent:\t) {
# you may append \t here as well ^
well I finally decided to attach the whole hack again
--
Michal Suchanek
[EMAIL PROTECTED]
{ if ($0 ~ ^From:\t) {
# a From: line is eaten
from=$0
start=1
}else{
#not From:
if (start) {
#but after From:
start=0
if ($0 ~ ^Sent:\t) {
# Sent: after From:
mail=from;
sub(^.*\\[,,mail);
sub(\\].*$,,mail);
wday=substr($2,1,3);
mon=substr($3,1,3);
mday=substr($4,1,2);
year=$5
hour=substr($6,1,2);
min=substr($6,4,4);
if ($7==PM) hour+=12;
date= wday mon mday hour : min year
print From mail date
print Date: date
}
#doesnt look like a header
# just print the eaten line
print from
}
# not even after From:
# nothing special
print $0
}
}
--
John P. Verel
Living Proof That Low Tech Beats High Tech!
Re: mail-followup-to header
Eduardo Gargiulo ([EMAIL PROTECTED]) muttered: I'm running mutt 1.3.28 and i have set followup_to honor_followup_to. Good. :) I want to configure mutt to set mail-followup-to header just only with the address of the mailing list i'm posting to, and not with my address. Is there any way to do that? I mean remove other addresses than mailing list? set alternates appropriately and configure the lists you are subscribed to with the subscribe command. If you list-reply to a mailinglist mail which has a mft header mutt will only reply to the adresses in the mft header. HTH, Michael -- ...[Linux's] capacity to talk via any medium except smoke signals. (By Dr. Greg Wettstein, Roger Maris Cancer Center) PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key
Re: fork() ?
begin Simon White quotation: Can you not just do $ fetchmail (options) $ mutt Or, better: fetchmail -d300 mutt -- Shawn McMahon| McMahon's Laws of Linux support: http://www.eiv.com | 1) There's more than one way to do it AIM: spmcmahonfedex, smcmahoneiv | 2) Somebody thinks your way is wrong msg27301/pgp0.pgp Description: PGP signature
Re: mutt as news reader ...
--+QahgC5+KEYLbs62 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Eduardo Gargiulo [EMAIL PROTECTED], 2002-04-17 13:03 -0400: Hi all. Hi Eduardo! It is possible to use mutt as news reader? My favorite nntp patch is Orjan Stromberg's: http://www.ing.umu.se/~connor/programs/mutt.html I wrote a little wrapper around NNTPPost: #/bin/sh #/usr/local/bin/newspost, a wrapper for /usr/bin/NNTPPost # assumes your /etc/news/server contains the name of your newsserver touch $USER/.muttnntp_spol /usr/bin/NNTPPost $USER/.muttnntp_spol $(cat /etc/news/server) \ cat $HOME/.muttnntp_spol $HOME/.muttnntp_spol.SENT 2 /dev/null and have this in my .muttrc: #nntp-patch set nntp_offline=3Dyes bindindex F followup=20 bindpager F followup=20 macro index i !newspost\nB deliver and get news macro pager i !newspost\nB deliver and get news I like this patch much better than Vladimir's vvv-nntp, but YMMV. If the answer is yes, how should i configure it? You can use the patched source Orjan provides, make sure you compile mutt with --enable-nntp option. -Andre --+QahgC5+KEYLbs62 Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8vbLtWkhBtALlJZ0RAtIaAJ4+ySzq0wnBKm0zLuN3EfJ/Vs3JnACgzMCB Lbp6TRNiHX+z45JYz13Hk1A= =ha+S -END PGP SIGNATURE- --+QahgC5+KEYLbs62--
Re: List-Reply
On Wed, Apr 17, 2002 at 01:17:53PM -0400, Dan Lowe wrote: Previously, s. keeling wrote: I think that last bit is the important part here. Why does it matter? Who cares how it got to you. What's important is what you do with it now. Are you goingg to reply to the poster who cc:'d you, or are you going to reply to the list? Once you're on enough lists, sorting them into proper contains (folders) becomes important. I, like many, use Procmail for that. I don't use the Message-ID trick to delete duplicates; I used to, but I had to stop because it kept deleting the wrong copy, as described in this thread (the mail would end up in my inbox instead of the list folder). I too use procmail. Everything from mutt-users ends up in my IN.mutt-users file. I also use the Message-ID trick, but the duplicate (whatever comes in that matches a previously seen M-ID) ends up in IN.duplicates You seem to have sent this to something other than [EMAIL PROTECTED] Yes, I forgot to repoint my alias for mutt-users. As the list maintainer said, both work but only one of them's correct. I've since fixed this. -- Any technology distinguishable from magic is insufficiently advanced. TopQuark Software Serv. Contract programmer, server bum.
Re: mutt as news reader ...
--+HP7ph2BbKc20aGI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline * Andre Berger [EMAIL PROTECTED], 2002-04-17 13:39 -0400: * Eduardo Gargiulo [EMAIL PROTECTED], 2002-04-17 13:03 -0400: [...] I wrote a little wrapper around NNTPPost: Here's the correct version: #/bin/sh #/usr/local/bin/newspost, a wrapper for /usr/bin/NNTPPost # assumes your /etc/news/server contains the name of your newsserver touch $HOME/.muttnntp_spol 2 /dev/null /usr/bin/NNTPPost $HOME/.muttnntp_spol $(cat /etc/news/server) \ cat $HOME/.muttnntp_spol $HOME/.muttnntp_spol.SENT 2 /dev/null rm $HOME/.muttnntp_spol 2 /dev/null Sorry, stupid me messed the other one up :( -Andre --+HP7ph2BbKc20aGI Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8vbVkWkhBtALlJZ0RAtwMAKCZL17sYb0nVsN94LCBvqGHO3CisgCgoqpj Wa0VZZ0sJjV3LZ09Xtf/gmY= =FP9m -END PGP SIGNATURE- --+HP7ph2BbKc20aGI--
Re: mutt as news reader ...
--0ntfKIWw70PvrIHh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Andre Berger [EMAIL PROTECTED], 2002-04-17 13:48 -0400: * Andre Berger [EMAIL PROTECTED], 2002-04-17 13:39 -0400: * Eduardo Gargiulo [EMAIL PROTECTED], 2002-04-17 13:03 -0400: [...] I wrote a little wrapper around NNTPPost: =20 Here's the correct version: =20 #/bin/sh #/usr/local/bin/newspost, a wrapper for /usr/bin/NNTPPost # assumes your /etc/news/server contains the name of your newsserver touch $HOME/.muttnntp_spol 2 /dev/null /usr/bin/NNTPPost $HOME/.muttnntp_spol $(cat /etc/news/server) \ cat $HOME/.muttnntp_spol $HOME/.muttnntp_spol.SENT 2 /dev/null rm $HOME/.muttnntp_spol 2 /dev/null =20 Sorry, stupid me messed the other one up :( And one more time : #/bin/sh #/usr/local/bin/newspost, a wrapper for /usr/bin/NNTPPost # assumes your /etc/news/server contains the name of your newsserver /usr/bin/NNTPPost $HOME/.muttnntp_spol $(cat /etc/news/server) \ cat $HOME/.muttnntp_spol $HOME/.muttnntp_spol.SENT 2 /dev/null rm $HOME/.muttnntp_spol 2 /dev/null The touch line confused NNTPPost. Argh, it's one of those days... -Andre --0ntfKIWw70PvrIHh Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8vbaMWkhBtALlJZ0RAgygAKDUYwo4a9d/eGnrKr27Cxh1ssb6eQCgm1c7 IXV+lbfPS6+ODTctIJ6iU6o= =PhiR -END PGP SIGNATURE- --0ntfKIWw70PvrIHh--
Re: /var/spool/mail/.... is not a mailbox
* Volker Kuhlmann [EMAIL PROTECTED] [04-17-02 02:28]: However, when you make fetchmail deliver directly to procmail, fetchmail does not generate a From line at all, and neither does procmail - big barf results. In that case, use fetchmail - formail | procmail. I believe that this is misleading/incorrect information. I have mda '/usr/bin/procmail -d %T' That's interesting - I would have expected procmail to generate the From_ but it surely didn't with fetchmail --mda 'procmail /dev/null $logfile 21' Perhaps the explicit delivery mode (-d) makes the difference, there's also -f- but you're not using that. But the main thing is we get it working. No, apparently procmail is providing From , or my mails would not contain it. Guess you need to look another place ?? Is it possible that mbox is not being used?? -- Patrick Shanahan Registered Linux User #207535 Registered at: http://counter.li.org
Re: fork() ?
* Edmund GRIMLEY EVANS [EMAIL PROTECTED] [2002-04-17 11:51:51 +0100]: I think getmail does better than fetchmail if the network goes down while it's polling the server: fetchmail has an annoying habit of losing its fetchids when this happens, resulting in the delivery of several hundred duplicate messages in my case. However, I don't care about that so much any more as I have a procmail script to filter out duplicates (using an MD5 sum of the message contents rather than trusting Message-IDs). Would you share it? I would like such a thing. Nicolas
Re: mail-followup-to header
Michael Tatge [EMAIL PROTECTED] wrote: set alternates appropriately and configure the lists you are subscribed to with the subscribe command. If you list-reply to a mailinglist mail which has a mft header mutt will only reply to the adresses in the mft header. HTH, thanks, it works. May i ask a quetion about alternates in this thread? ok ... I use diferent email addresses to subscribe to diferent lists, ejg-mutt for mutt-users and ejg-qmail for qmail lists. I use ejg too. Is the following alternetes set appropriately for my scenario? set alternates=^ejg.*(-mutt|-qmail)@ar.homelinux.org$ thanks and sorry for my english ;) -- Eduardo Gargiulo ejg(at)ar.homelinux.org msg27308/pgp0.pgp Description: PGP signature
Re: List-Reply
(the mail would end up in my inbox instead of the list folder). That should not happen. What does, say, your mutt-users procmail recipe look like? Mine's: :0 H * ^TO.*@mutt.org mutt/ (plus a few others, for guug.de and gbnet.net messages too) If you were to send a message to both me and mutt-users, i would of course get both copies. This recipe would put both copies in my mutt folder. If i were using formmail, regardless of which one got deleted, the other would end up in the mutt folder. This is because the rule is based on a To header containing mutt.org, and both copies of the message will have that. -- Mike Schiraldi VeriSign Applied Research msg27309/pgp0.pgp Description: PGP signature
folder-hook index_format
I want my sentbox folder to show me the recipient's name, the date, etc. So I use this line in .muttrc. But all I get are blank lines. folder-hook sentbox set index_format=%d %t (%3l) %s If I use this line: folder-hook sentbox set index_format=%d %s All I get is the date. What am I missing? -- Michael Montagne [EMAIL PROTECTED] http://www.boora.com
Re: /var/spool/mail/.... is not a mailbox
On Wed, Apr 17, 2002 at 04:18:18PM +1200, Volker Kuhlmann wrote: However, when you make fetchmail deliver directly to procmail, fetchmail does not generate a From line at all, and neither does procmail - big barf results. In that case, use fetchmail - formail | procmail. I believe that this is misleading/incorrect information. I have mda '/usr/bin/procmail -d %T' That's interesting - I would have expected procmail to generate the From_ but it surely didn't with fetchmail --mda 'procmail /dev/null $logfile 21' Perhaps the explicit delivery mode (-d) makes the difference, there's also -f- but you're not using that. But the main thing is we get it working. Volker -- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.orcon.net.nzPlease do not CC list postings to me. It seems that is exactly the problem. with just plain mda 'procmail' /var/spool/mail/ is not seen as a proper mailbox but with -d %T options it's ok. I'm not sure if this is the case with others but it seems that way here. But what do I care I only use mutt itself to check my pop mail anyhow. -- Chad Young Linux User #195191
Re: mail-followup-to header
Eduardo Gargiulo wrote: I'm running mutt 1.3.28 and i have set followup_to honor_followup_to. I want to configure mutt to set mail-followup-to header just only with the address of the mailing list i'm posting to, and not with my address. Is there any way to do that? I mean remove other addresses than mailing list? change lists foo to subscribe foo. -- Will Yardley input: william hq . newdream . net .
Re: mail-followup-to header
* Eduardo Gargiulo [EMAIL PROTECTED] [2002-04-17 14:06]: I use diferent email addresses to subscribe to diferent lists, ejg-mutt for mutt-users and ejg-qmail for qmail lists. I use ejg too. Is the following alternetes set appropriately for my scenario? set alternates=^ejg.*(-mutt|-qmail)@ar.homelinux.org$ I'd do it like: set alternates = ejg(-mutt|-qmail)?@ar\.homelinux\.org I have something like: set alternates = dlc(-.*)?@(host1|host2) So that I don't have to keep updating $alternates when I add new -pieces. (darren) -- All is fear in love and war.
Re: folder-hook index_format
Hi, * Michael Montagne [04/17/02 20:25:08 CEST] wrote: I want my sentbox folder to show me the recipient's name, the date, etc. So I use this line in .muttrc. But all I get are blank lines. folder-hook sentbox set index_format=%d %t (%3l) %s Works here. Why not use %v or %L instead ot %t? So you wouldn't have to use folder-hooks, I guess, because %v makes exactly the distinction you'd like to have. If I use this line: folder-hook sentbox set index_format=%d %s Hmm, you could try enclosing the command in ''. %d requires a $date_format to be set, so check that, too. And btw, your first version really will look ugly. You probably would want to use something like: %d %-15.15t (%3l) %s HTH, Cheers, Rocco. msg27314/pgp0.pgp Description: PGP signature
Re: List-Reply [OT]
On Wed, Apr 17, 2002 at 02:16:47PM -0400, Mike Schiraldi wrote: (the mail would end up in my inbox instead of the list folder). That should not happen. What does, say, your mutt-users procmail recipe look like? Mine's: :0 H * ^TO.*@mutt.org mutt/ Isn't that supposed to be * ^TO_.*@...? Aren't you missing an underscore there? -- Any technology distinguishable from magic is insufficiently advanced. TopQuark Software Serv. Contract programmer, server bum.
OT: .procmailrc
Isn't that supposed to be * ^TO_.*@...? Aren't you missing an underscore there? From the procmailrc man page: If the regular expression contains `^TO_' it will be sub stituted by `(^((Original-)?(Resent-)?(To|Cc|Bcc)|(X- Envelope|Apparently(-Resent)?)-To):(.*[^-a-zA-Z0-9_.])?)', which should catch all destination specifications containing a specific address. If the regular expression contains `^TO' it will be sub stituted by `(^((Original-)?(Resent-)?(To|Cc|Bcc)|(X- Envelope|Apparently(-Resent)?)-To):(.*[^a-zA-Z])?)', which should catch all destination specifications containing a specific word. -- Mike Schiraldi VeriSign Applied Research msg27316/pgp0.pgp Description: PGP signature
Re: procmail script for deleting duplicates
* Edmund GRIMLEY EVANS [EMAIL PROTECTED] [2002-04-17 21:31:00 +0100]: Nicolas Rachinsky [EMAIL PROTECTED]: I think getmail does better than fetchmail if the network goes down while it's polling the server: fetchmail has an annoying habit of losing its fetchids when this happens, resulting in the delivery of several hundred duplicate messages in my case. However, I don't care about that so much any more as I have a procmail script to filter out duplicates (using an MD5 sum of the message contents rather than trusting Message-IDs). Would you share it? I would like such a thing. The start of my .procmailrc is below. The in-line Perl script removes all header fields except Date, From, Subject, To and Cc. MD5 sums are appended to $MAILDIR/MD5, so you should remove the beginning of that file from time to time. Duplicates are sent to =dupes. It's not efficient or elegant, but it seems to work. Thanks. Looks quite nice. Nicolas
Re: procmail script for deleting duplicates
On Wed, Apr 17, 2002 at 10:42:46PM +0200, Nicolas Rachinsky wrote: * Edmund GRIMLEY EVANS [EMAIL PROTECTED] [2002-04-17 21:31:00 +0100]: Nicolas Rachinsky [EMAIL PROTECTED]: I think getmail does better than fetchmail if the network goes down while it's polling the server: fetchmail has an annoying habit of losing its fetchids when this happens, resulting in the delivery of several hundred duplicate messages in my case. However, I don't care about that so much any more as I have a procmail script to filter out duplicates (using an MD5 sum of the message contents rather than trusting Message-IDs). Would you share it? I would like such a thing. The start of my .procmailrc is below. The in-line Perl script removes all header fields except Date, From, Subject, To and Cc. MD5 sums are appended to $MAILDIR/MD5, so you should remove the beginning of that file from time to time. Duplicates are sent to =dupes. It's not efficient or elegant, but it seems to work. Thanks. Looks quite nice. Somehow I've missed the start of Edmund's .procmailrc. But why wouldn't one do it this way rather than MD5 all that stuff manually? Have you found the message-id header to be that unreliable? :0 Wh: msgid.lock | formail -D 8192 .msgid.cache -- David Kelly N4HHE, [EMAIL PROTECTED] = The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system.
Re: Organizing mailfolders (strategies and using with mutt)
Hi, * David Rock [EMAIL PROTECTED] [02-04-17 05:38]: On Thu, Apr 11, 2002 at 02:51:56PM +0200, Thorsten Haude wrote: I have something similar: Mail/in Mail/ML/Mutt Mail/ML/NEdit Mail/ML/Debian/user Mail/ML/Debian/misc etc. Mutt's default for saving messages seems to revolve around the From address (e.g. mail from [EMAIL PROTECTED] wants to save to ~/Mail/foo). Does anyone have some good ideas about how to manage their mailboxes? What happens when you have a thread involving multiple people? If you use the above example, the thread would be destroyed as you save to different folders. Is there a way to track a thread across different folders (maybe by message ids)? You got something wrong. I get most mails from mailing lists (see /ML/ above) and sort them after 'To:' or 'Cc:'. So threads remain untouched. If you have a thread with some friends, you can send you a copy of every mail and keep the thread in your inbox. Thorsten -- Question Authority!
Re: procmail script for deleting duplicates
Hi, * Edmund GRIMLEY EVANS [04/17/02 22:31:00 CEST] wrote: The start of my .procmailrc is below. The in-line Perl script removes all header fields except Date, From, Subject, To and Cc. MD5 sums are appended to $MAILDIR/MD5, so you should remove the beginning of that file from time to time. Duplicates are sent to =dupes. It's not efficient or elegant, but it seems to work. [...] ,[ procmailex(5) ]- | If you are subscribed to several mailinglists and people | cross-post to some of them, you usually receive several | duplicate mails (one from every list). The following sim- | ple recipe eliminates duplicate mails. It tells formail | to keep an 8KB cache file in which it will store the Mes- | sage-IDs of the most recent mails you received. Since | Message-IDs are guaranteed to be unique for every new | mail, they are ideally suited to weed out duplicate mails. | Simply put the following recipe at the top of your rcfile, | and no duplicate mail will get past it. | | :0 Wh: msgid.lock | | formail -D 8192 msgid.cache | | Beware if you have delivery problems in recipes below this | one and procmail tries to requeue the mail, then on the | next queue run, this mail will be considered a duplicate | and will be thrown away. For those not quite so confident | in their own scripting capabilities, you can use the fol- | lowing recipe instead. It puts duplicates in a separate | folder instead of throwing them away. It is up to you to | periodically empty the folder of course. | | :0 Whc: msgid.lock | | formail -D 8192 msgid.cache | | :0 a: | duplicates `- Cheers, Rocco. msg27321/pgp0.pgp Description: PGP signature
Re: List-Reply
--ZfOjI3PrQbgiZnxM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Alas! Dan Lowe spake thus: Once you're on enough lists, sorting them into proper contains (folders) becomes important. I, like many, use Procmail for that. I don't use the Message-ID trick to delete duplicates; I used to, but I had to stop becau= se it kept deleting the wrong copy, as described in this thread (the mail would end up in my inbox instead of the list folder). There's a very simple fix, here. In your procmail rules, stop using ^To: and start using ^TO_ (sans quotes of course). ^TO_ is special procmail shorthand for some regex that basically matches To:, Cc:, and Bcc: (I think). That way, when you get both copies of the email, even the one that is Cc'd to you, will be filtered into the mutt folder. THEN you can be like me and not give two flips about whether you're reading the list copy or the Cc'ed copy, because they both end up in the correct folder. And you can turn duplicate filtering back on, too ;) --=20 Rob 'Feztaa' Park [EMAIL PROTECTED] -- There is nothing more silly than a silly laugh. -- Gaius Valerius Catullus --ZfOjI3PrQbgiZnxM Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8vgTHPTh2iSBKeccRAm3KAJ9RoenOKbv6G24tSUtktkpEeBuf/ACfdE9/ zpObxcjxisAeGNt6YB0PbDw= =NkyC -END PGP SIGNATURE- --ZfOjI3PrQbgiZnxM--
Re: List-Reply
--R+My9LyyhiUvIEro Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Alas! Mike Schiraldi spake thus: That should not happen. What does, say, your mutt-users procmail recipe l= ook like? =20 Mine's: =20 :0 H * ^TO.*@mutt.org mutt/ Like I said in my other message: :0: * ^TO_mutt-user $MAILDIR/mutt And it all gets sorted out The Right Way. ;) If you were to send a message to both me and mutt-users, i would of course get both copies. This recipe would put both copies in my mutt folder. If i were using formmail, regardless of which one got deleted, the other would end up in the mutt folder. This is because the rule is based on a To header containing @mutt.org, and both copies of the message will have that. Exactly ;) --=20 Rob 'Feztaa' Park [EMAIL PROTECTED] -- The difference between dogs and cats is that dogs come when they're called. Cats take a message and get back to you. --R+My9LyyhiUvIEro Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8vgV3PTh2iSBKeccRAgotAJ0eeOV9w1EVA1yj+PzhhRShE4zdiACfa0hH mqHweqe26np9g0lZqcw3pZo= =eJzq -END PGP SIGNATURE- --R+My9LyyhiUvIEro--
Re: List-Reply
Alas! Mike Schiraldi spake thus: I'm not sure what kind of procmail voodoo you would need to grab this information from Delivered-To and fulfill the user's request, but it would be weird and scary. You're so simple-minded. All you have to do is set up a temporal anomaly in which procmail runs /backwards/ through time, such that it is able to recognize the second email before the first arrives, and delete the first one instead of the second ;) -- Rob 'Feztaa' Park [EMAIL PROTECTED] -- Knowledge, sir, should be free to all! -- Harry Mudd, I, Mudd, stardate 4513.3 msg27324/pgp0.pgp Description: PGP signature
Re: List-Reply
On Wed, Apr 17, 2002 at 05:20:45PM -0600, Rob 'Feztaa' Park wrote:
Alas! Mike Schiraldi spake thus:
I'm
not sure what kind of procmail voodoo you would need to grab this
information from Delivered-To and fulfill the user's request, but it would
be weird and scary.
You're so simple-minded. All you have to do is set up a temporal anomaly
in which procmail runs /backwards/ through time, such that it is able to
recognize the second email before the first arrives, and delete the
first one instead of the second ;)
ROTFLMAO.
- Geeks all over the world are (as we write) trying to figure out
how to implement this. It'll be in the next version.
- _Something_ doesn't show you new mail 'til a few days after it
arrives ('cause you have to wait for possible duplicates to
arrive). Inconvenient, but for those who can't stand seeing
duplicates (or the wrong duplicate), well worth the wait.
- Kibo probably already has the fix implemented.
Simpler is to ignore what was done in the past. Decide what you will
do in the future. Now, we can all go out and hunt down and kill those
miscreants who reply to the author and cc: the list. And you thought
there was no real reason for netiquette ...
--
Any technology distinguishable from magic is insufficiently advanced.
TopQuark Software Serv. Contract programmer, server bum.
Re: search in browser
OK. I suppose that I can not locate a folder with new email using something like /~N. How can I search a string or go to a folder with new emails in file browser? The / command seems to be working in a different way as that in index. Thanks. -- Bo Peng Department of Statistics Rice University http://www.stat.rice.edu/~bpeng -- Bo Peng Department of Statistics Rice University http://www.stat.rice.edu/~bpeng
limit to subjects with only CAPITALS
How do you limit to subjects in CAPS only, ie containing not a single lowercase letter? caveat: the subjects may have other characters - but all the letters are uppercase. note: a pattern containing only lowercase letters default to checking uppercase letters, too. so this does not work: ! ~s [a-z] and it does not help making at least one uppercase letter a requirement: ~s [A-Z] ! ~s [a-z] ideas? Sven [04:14am *yawn*]
Re: limit to subjects with only CAPITALS
Have you tried this pattern? [^a-z] Joel On Thu, Apr 18, 2002 at 04:14:18AM +0200, Sven Guckes wrote: How do you limit to subjects in CAPS only, ie containing not a single lowercase letter? caveat: the subjects may have other characters - but all the letters are uppercase. note: a pattern containing only lowercase letters default to checking uppercase letters, too. so this does not work: ! ~s [a-z] and it does not help making at least one uppercase letter a requirement: ~s [A-Z] ! ~s [a-z] ideas? Sven [04:14am *yawn*]
Re: List-Reply
in message [EMAIL PROTECTED],
wrote s. keeling thusly...
- _Something_ doesn't show you new mail 'til a few days after it
arrives ('cause you have to wait for possible duplicates to
arrive). Inconvenient, but for those who can't stand seeing
duplicates (or the wrong duplicate), well worth the wait.
if large enough cache size is used, late arriving duplicate mail
could be caught by procmail.
--
Re: limit to subjects with only CAPITALS
On Thu, Apr 18, 2002 at 04:14:18AM +0200, Sven Guckes wrote: How do you limit to subjects in CAPS only, ie containing not a single lowercase letter? caveat: the subjects may have other characters - but all the letters are uppercase. I've used this as a search pattern in the pager to highlight newsletter section headings: /\^[A-Z0-9][A-Z0-9 [:punct:]]*$^M So you could probably adapt it for your subject search. Maybe this (untried): ~s \^[A-Z0-9 [:punct:]]+$ Sven [04:14am *yawn*] Just going to bed or just getting up? Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Spokane, Washington, USA http://www.spocom.com/users/gjohnson/mutt/ |
Re: limit to subjects with only CAPITALS
* Joel Hammer [EMAIL PROTECTED] [2002-04-18 02:20]: Have you tried this pattern? [^a-z] no - because the limit command would then match all subject lines which contain at least one non-letter, such as Subject: can you spot the non-letter? to repeat: i'm trying to limit all mails to those matching a pattern in subject line which contain at least one letter - but all of the letters are uppercase. Sven [05:09am *YAWN*]
Re: limit to subjects with only CAPITALS - solved!
* Gary Johnson [EMAIL PROTECTED] [2002-04-18 03:04]: On Thu, Apr 18, 2002 at 04:14:18AM +0200, Sven Guckes wrote: How do you limit to subjects in CAPS only, ie containing not a single lowercase letter? caveat: the subjects may have other characters - but all the letters are uppercase. I've used this as a search pattern in the pager to highlight newsletter section headings: /\^[A-Z0-9][A-Z0-9 [:punct:]]*$^M So you could probably adapt it for your subject search. Maybe this (untried): ~s \^[A-Z0-9 [:punct:]]+$ sorry, no. the subject line may have a LOT of other characters - much more than just letters and punctuation. hmm... '^' and '$' do work? ~s '^[^a-z]+$' YES! :-) Sven [04:14am *yawn*] Just going to bed or just getting up? guess ;-) Sven [05:15am zzzZZZ]
Re: limit to subjects with only CAPITALS - unsolved!
* Sven Guckes [EMAIL PROTECTED] [2002-04-18 03:16]: How do you limit to subjects in CAPS only, ie containing not a single lowercase letter? ~s '^[^a-z]+$' YES! :-) silly me. this solves another nice problem, of course, but not the one I proposed. *sigh* any more ideas, folks? here are some examples to test your ideas: Subject: THIS SUBJECT IS IN CAPS ONLY Subject: THIS 1 2! Subject: !ME TOO! Subject: A N D M E T H R E E Subject: !$#A^N%@D#*M%*E!#^ anyone? Sven [05:20am *bed*!]
Re: limit to subjects with only CAPITALS
--IS0zKkzwUGydFO0o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Alas! Sven Guckes spake thus: * Joel Hammer [EMAIL PROTECTED] [2002-04-18 02:20]: Have you tried this pattern? [^a-z] =20 no - because the limit command would then match all subject lines which contain at least one non-letter, such as =20 Subject: can you spot the non-letter? So then how about ^[^a-z]+$ ? That would match anything that contained only non-lowercase-letters, wouldn't it? --=20 Rob 'Feztaa' Park [EMAIL PROTECTED] -- Art is either plagiarism or revolution. -- Paul Gauguin --IS0zKkzwUGydFO0o Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8vj0sPTh2iSBKeccRAjFNAJ406npzne+ZaQFdcuoj09eTBxdOzwCfcfQo Jen5LfAgZ0FDX5+kjM10aGs= =LDBN -END PGP SIGNATURE- --IS0zKkzwUGydFO0o--
Re: limit to subjects with only CAPITALS
* Rob 'Feztaa' Park [EMAIL PROTECTED] [2002-04-18 03:28]: Have you tried this pattern? [^a-z] no - because the limit command would then match all subject lines which contain at least one non-letter, such as Subject: can you spot the non-letter? So then how about ^[^a-z]+$ ? That would match anything that contained only non-lowercase-letters, wouldn't it? correct. but I do want subjects with letters! however, all of these must *not* be lowercase letters, but only uppercase. try again? :-) Sven [yes, my clone is asleep now ;-)]
Re: limit to subjects with only CAPITALS
* On 2002.04.17, in [EMAIL PROTECTED], * Rob 'Feztaa' Park [EMAIL PROTECTED] wrote: So then how about ^[^a-z]+$ ? That would match anything that contained only non-lowercase-letters, wouldn't it? No, because mutt makes that a case-insensitive match since the pattern contains only lowercase letters. This should work: ~s ^A*[^a-z]+$ -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: limit to subjects with only CAPITALS - unsolved!
On Thu, Apr 18, 2002 at 05:15:54AM +0200, Sven Guckes wrote: * Gary Johnson [EMAIL PROTECTED] [2002-04-18 03:04]: So you could probably adapt it for your subject search. Maybe this (untried): ~s \^[A-Z0-9 [:punct:]]+$ sorry, no. the subject line may have a LOT of other characters - much more than just letters and punctuation. What else is there? From the mutt manual: [:punct:] Punctuation characters (characters that are not letter, digits, control characters, or space characters). so it seems to me that upper-case letters, digits, spaces, and [:punct:] would include everything that would be in a subject except perhaps a tab. On Thu, Apr 18, 2002 at 05:20:12AM +0200, Sven Guckes wrote: here are some examples to test your ideas: Subject: THIS SUBJECT IS IN CAPS ONLY Subject: THIS 1 2! Subject: !ME TOO! Subject: A N D M E T H R E E Subject: !$#A^N%@D#*M%*E!#^ I tested the search pattern [A-Z0-9 [:punct:]]+ on the above examples and it matched all of every one. Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Spokane, Washington, USA http://www.spocom.com/users/gjohnson/mutt/ |
Re: List-Reply
Shawn McMahon writes: IMHO, if you hit list-reply and Mutt doesn't recognize a list, it should assume you know what you're talking about, and pop up the To: address as a yes/no default. Then if you say no, it should cycle through the Cc: addresses until you say yes or q. Alternately, just do the To:, and ignore the Cc:, because people shouldn't be Cc:ing lists. But that may just be me. Either one would be fine (the latter is probably the most useful). Mike Schiraldi writes: If a message said: From: Alice To: A list the request is for a command which will initiate a reply to A list but not Alice. Exactly! However, in both cases i'd say you should just group-reply to everyone, and if the recipient is annoyed at getting two copies of the message, they should just use the one-line procmail/formmail solution to remove duplicate messages. And if their OS doesn't support that, it's a great incentive to upgrade to one which does. :) Believe me, I would love to see everyone upgrade to an OS that supports Procmail! But do you really think that telling them I'm sending you two copies, and suggesting that you change your OS and then learn how to use procmail and write your own filter script to detect duplicates, because the mailer I'm using on Linux doesn't know how to reply to a mailing list is likely to be very persuasive toward that goal? Personally, I'd rather be able to tell them Hey, look at the great reply mode my mailer has -- I don't even have to edit the headers after replying! Wouldn't you like to be able to do that yourself? So I gather that mutt currently has no way of doing this. If I add one, is there any chance it might make it back into the source tree? Or are people really opposed to this on principle? ...Akkana
