Hi everyone This question might seem very trivial, but it needs to be asked: How does one if they get a whole lot of messages (ie. more than 400) move messages according to most recent into a particular folder?
Thanking you in advance for your invaluable assistance. Regards Deon CELL: +27 73 195-0299 ----- Original Message ----- From: "mutt-users-digest" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, January 12, 2002 2:46 AM Subject: mutt-users-digest V1 #954 > > mutt-users-digest Saturday, January 12 2002 Volume 01 : Number 954 > > > > Today's Topics: > > Re: mail being returned > Re: mail being returned > Re: Patch trouble > Folder View problems > Re: Suggestion for List Etiquette > Re: For messages without charset specified > Re: individual index_formats > Mutt dumps core... > Re: patch to force pgp_create_traditional on non-us-ascii mails (was: application/pgp breaks Pine, too (was: applying pgp-outlook patch)) > Re: Suggestion for List Etiquette > Be more clear (was: Re: mailboxes command confusion.) > Re: Suggestion for List Etiquette > Re: Getting Keys From Keyserver? > Re: mail being returned > Re: patch to force pgp_create_traditional on non-us-ascii mails (was: application/pgp breaks Pine, too (was: applying pgp-outlook patch)) > Re: Suggestion for List Etiquette > Re: patch to force pgp_create_traditional on non-us-ascii mails (was: application/pgp breaks Pine, too (was: applying pgp-outlook patch)) > > ---------------------------------------------------------------------- > > Date: Fri, 11 Jan 2002 13:56:15 -0500 > From: David T-G <[EMAIL PROTECTED]> > Subject: Re: mail being returned > > - --XpNX0AP0or0vBirh > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > Nick -- > > =2E..and then Nick Wilson said... > %=20 > % * On 11-01-02 at 19:20=20 > % * David T-G said.... > %=20 > % > You really should pick a cool name for your machine, you know :-) > % =20 > % Well, I had named it explodingnet.com (my websites name also) but then I > > No, that won't work, as you saw; there already is one of those. > % had problems mailing [EMAIL PROTECTED] Still trying to come > % up with something suitably stupid. > > To really do it right you should get a domain and have that at your house, > but realistically you could probably use home.explodingnet.com (since > you control the domain and it's your home computer) or nick.yourisp.com > (though that won't show up in a DNS lookup, either) or some such. But you > shouldn't leave it localhost 'cuz every machine has one of those :-) > %=20 > % > % Problem is I keep getting failure to deliver notices. > % > % Why, and what can I do? > % >=20 > % > Because some mailers care from whence the message comes because they > % > don't want to deliver any spam (among other things). > %=20 > % Yeah, I figured that far. > > yep. > %=20 > % > Do you have $envelope_from set? If not, are you forcing it ing in your > % > $sendmail setting? If not, do you have your MTA configured to announce > %=20 > % Well I have the envelope jobbie set now and all seems well. I guess some > % servers/lists are just more sensitive than others. Bless 'em. > > Indeed. > %=20 > % Ta very much. > > No problem! > %=20 > % --=20 > %=20 > % Nick Wilson > %=20 > % Tel: +45 3325 0688 > % Fax: +45 3325 0677 > % Web: www.explodingnet.com > %=20 > :-D > - --=20 > David T-G * It's easier to fight for one's principles > (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie > (work) [EMAIL PROTECTED] > http://www.justpickone.org/davidtg/ Shpx gur Pbzzhavpngvbaf Qrprapl Npg! > - --XpNX0AP0or0vBirh > 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 > > iD8DBQE8PzVPGb7uCXufRwARAo+eAKDT9Fri+fZq91SFXfFYWzlaTqvTmACg3AR6 > tzQLiuLsVWYbpZ/rbDS4r74= > =hE23 > - -----END PGP SIGNATURE----- > > - --XpNX0AP0or0vBirh-- > > ------------------------------ > > Date: Fri, 11 Jan 2002 14:22:14 -0500 > From: Samuel Padgett <[EMAIL PROTECTED]> > Subject: Re: mail being returned > > David T-G <[EMAIL PROTECTED]> writes: > > To really do it right you should get a domain and have that at your house, > > but realistically you could probably use home.explodingnet.com (since > > you control the domain and it's your home computer) or nick.yourisp.com > > (though that won't show up in a DNS lookup, either) or some such. > Services like <URL:http://www.dyndns.org> are good for this > purpose. > Sam > > ------------------------------ > > Date: Fri, 11 Jan 2002 13:43:26 -0600 > From: Aaron Schrab <[EMAIL PROTECTED]> > Subject: Re: Patch trouble > > At 09:00 +0100 11 Jan 2002, Nick Wilson <[EMAIL PROTECTED]> wrote: > > can anyone make sense of the output I'm getting when trying to use the > > %_patch? > > can't find file to patch at input line 4 > > Perhaps you should have used the -p or --strip option? > The above line is patch itself telling you what the problem is. You > need to use an appropriate -p option. This option tells it how many > levels of directory names to strip from the front of file names in patch > files. By default it will strip all directories, and just look for the > named file in the current directory. > > The text leading up to this was: > > -------------------------- > > |diff -durp mutt-1.3.22.1/doc/manual.sgml mutt-1.3.22.1.oe.%_.1/doc/manual.sgml > > |--- mutt-1.3.22.1/doc/manual.sgml Wed Sep 5 02:52:17 2001 > > |+++ mutt-1.3.22.1.oe.%_.1/doc/manual.sgml Wed Sep 5 03:01:26 2001 > Here with no -p option, patch would try to change the file named > manual.sgml in the current directory. With -p1 it would strip off only > the top level directory, and so look for a file named doc/manual.sgml to > change; this is likely what you want. If you used -p0, patch would look > for the file to change using either of the complete names mentioned > above, including the mutt-* part. > As a general rule of thumb, you should always run patch from inside the > top level directory of the source tree for the program you're patching. > If the patch file contains file names that mention what looks like the > distribution directory (in this case stuff like mutt-version or possibly > just mutt by itself), you should use -p1. Otherwise you probably want > to use -p0 (although in these cases you can often get away without using > a -p option at all). > - -- > Aaron Schrab [EMAIL PROTECTED] http://www.execpc.com/~aarons/ > Let's say the docs present a simplified view of reality... :-) > --Larry Wall > > ------------------------------ > > Date: Fri, 11 Jan 2002 11:54:18 -0800 > From: Igor Pruchanskiy <[EMAIL PROTECTED]> > Subject: Folder View problems > > Hello List, > It has been a long time since i posted questions here, because RTFM is a > magical thing. Well, this time it is something i can not solve on my > own... > I have been doing some changes to my ~/.muttrc, restructuring stuff and so > on. Tried to use IMAP but since i did not have time to figure out how to > conveniently archive my mail i still have some mailboxes with ~4500 > messages. I also tried using IMAP with Michael Elkins's isync which worked > great, but then there is a problem of maintaining 2 sets of configs and > mutt versions, here at work, and at home. So here am I, using good old > method. SSH into the server. Type 'mutt'. Hit enter :o) > Anyway, back to the problem > Mutt does not or absolutely randomly displays "N" in the Folder View in front > of the mailboxes that have new mail... Each of those folders has at least > 20 messages. > I have not touched $folder_format at all. This problem also affects > $status_format %b which is supposed to tell you number of mailboxes with the > new mail. > I have spent 3 hours going through my ~/.muttrc and can not find anything > that could be wrong. > My .muttrc is here. Feel free to take a pick > http://cvs.linuxinside.com/cgi-bin/cvsweb.cgi/configs/.muttrc > Using > Mutt 1.3.25-current-20020110i (2002-01-01) > I had to install the CVS version since \012 in PGP signed mail drove me > nuts :) > igor > - -- > Uptime : 30 days, 11:55 > > ------------------------------ > > Date: Fri, 11 Jan 2002 20:40:05 +0000 > From: Dallam <[EMAIL PROTECTED]> > Subject: Re: Suggestion for List Etiquette > > - --VS++wcV0S1rZb1Fb > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > > On Fri, Jan 11, 2002 at 06:24:47PM +0000, Benjamin Smith wrote: > > > Yeah, but the problem is that when 'chitchat' spins off from another > > thread, it rarely (in my experience) ends up getting moved. Although if > > people think that it will actually get used, I would support it > > We had the "chitchat" on the suse-linux-e list as well. One of the > list users now hosts an OT suse-list and it has helped keep the off > topic posts off the main list. > Regards, > Dallam > - -- > Dallam Wych [EMAIL PROTECTED] > 1024: A89A2371 "Ipsa scientia potestas est" > 2717 4EB8 461D 743B 47CF Registered Linux User > 0D68 C32A 5CDE A89A 2371 counter.li.org:213656 > > - --VS++wcV0S1rZb1Fb > 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 > > iD8DBQE8P02lwypc3qiaI3ERApITAKCww6TXnOHIZ0UHQ7vzRxMpKYR0pgCgvscF > QXF+q/JW0xeKED+76aZ1lI0= > =Myzq > - -----END PGP SIGNATURE----- > > - --VS++wcV0S1rZb1Fb-- > > ------------------------------ > > Date: Sat, 12 Jan 2002 04:41:23 +0800 > From: Charles Jie <[EMAIL PROTECTED]> > Subject: Re: For messages without charset specified > > - --huG+SbfbdD6eblZQ > Content-Type: text/plain; charset=big5 > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > Thank you very much, Cristiano. > > Thanks to this MAGIC setting, now the pager display right. > > Frankly speaking, I've read 'charset-hook' section of the manual a > couple of times, which defines "alias". I can hardly imagine we can set > and use it this way. :-) > > best regards, > charlie > > On Fri, Jan 11, 2002 at 02:18:33PM -0200, Cristiano Reis Monteiro wrote: > > I had the same problem an used: > > > > charset-hook "" iso-8859-1 > > > > I think you can use: > > > > charset-hook "" big5 > > > > This will match any message without 'charset' specified. > > > > Hope this helps > > > > []'s > > > > - Cristiano > > > > Em Thu, 10 Jan 2002, Charles Jie escreveu: > > > > > In our country, I used to receive messages without 'charset' specifed in > > > Content-Type:, while the text body is encoded in big5. > > > > > > I have my mutt "set charset=3Dbig5" but the pager just display '?'s for > > > such messages (other charset-tagged messages are OK). > > > > > > In Mozilla, I can have the following settings for 'Message Display': > > > > > > [v] Apply default to all messages (ignore character coding specified > > > by MIME header) > > > > > > How can I do it in mutt? "set charset=3Dbig5" looks not working. > > > > > > charlie > > > > -- > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= > =3D=3D=3D=3D=3D=3D > > /^\__/\ > > /' , : "Conhecimento nao e' crime !" > > ~ < o o > > / , \ [EMAIL PROTECTED] > > ( `- ..__" Estudante de Ciencia da Computacao - UFBA > > ' /' http://cristiano.dhs.org > > PGP public key available by WWW and on request. > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= > =3D=3D=3D=3D=3D=3D > > > > /"\ > > \ /? CAMPANHA DA FITA ASCII - CONTRA MAIL HTML > > X?? ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL > > / \ > > - -- > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > Charles Jie (=AC=F6=ACK=BF=B3) Keya Technologies (=B6}=B6=AE= > =AC=EC=A7=DE) > (O) +886 2 2936 0813 (Mobile) 0920 397 746 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > - --huG+SbfbdD6eblZQ > 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 > > iD8DBQE8P03yaeHJPU1Zge8RAmmmAKCCeK8VGo2BfgidYKQ7jT7cy3iHPwCeL4JV > uLo9dFAY9tF2Qm04kmKPwB0= > =wNFW > - -----END PGP SIGNATURE----- > > - --huG+SbfbdD6eblZQ-- > > ------------------------------ > > Date: Fri, 11 Jan 2002 14:53:29 -0600 > From: Aaron Schrab <[EMAIL PROTECTED]> > Subject: Re: individual index_formats > > At 17:04 -0600 10 Jan 2002, I wrote: > > http://schrab.com/aaron/mutt/patch-1.3.24.ats.date_optional.1 > Unfortunately, that URL won't work for anybody but me. The correct one > is: > http://pug.schrab.com/aaron/mutt/patch-1.3.24.ats.date_optional.1 > - -- > Aaron Schrab [EMAIL PROTECTED] http://www.execpc.com/~aarons/ > The only disadvantage I see is that it would force everyone to > get Perl. Horrors. :-) --Larry Wall > > ------------------------------ > > Date: Fri, 11 Jan 2002 23:22:54 +0100 > From: Nils Holland <[EMAIL PROTECTED]> > Subject: Mutt dumps core... > > Hi folks, > I've been using Mutt for quite some time, and now I have a problem. My > current mutt (1.2.5i on FreeBSD 4.5-PRERELEASE) seems to have some > problems: > I have set up mutt so that it accesses new mail that has been filtered into > my various inboxes and, once I have read these new messages, moves them to > other folders for later review by me. > Now, my "archive" folders have always worked fine, i.e. I could always > successfully access them when I wanted to look at some old message. > However, today I noticed that when accessing a few (but not all) of these > folders, mutt dumps core. > I have tried several things, but I don't know what's wrong. Therefore, I > uploaded one of my mbox files which triggers a core dump. It can be found > at http://www.tisys.org/misc/xpert (it's a folder containing XFree86 > mailing list messages, about 3.3 MB in size). I'd appreciate if someone > could try downloading and opening it it mutt, preferrably also in 1.2.5i, > but probably also in the latest beta. > If you try that and it also crashed your mutt, my mailbox file(s) must have > gotten corrupt (although I could not find any sign for that). If it works > for you, something must be wrong with my configuration ;-) > So, I'd be glad if some folks would try this out and report the results to > me. I've already tried opening the mailbox file(s) on all of my machines > without success, so the only thing left to do is probably call others for a > test... > Greetings > Nils > - -- > Nils Holland > Ti Systems - FreeBSD in Tiddische, Germany > http://www.tisys.org * [EMAIL PROTECTED] > > ------------------------------ > > Date: Fri, 11 Jan 2002 23:56:04 +0100 > From: Viktor Rosenfeld <[EMAIL PROTECTED]> > Subject: Re: patch to force pgp_create_traditional on non-us-ascii mails (was: application/pgp breaks Pine, too (was: applying pgp-outlook patch)) > > - --Bn2rw/3z4jIqBvZU > Content-Type: multipart/mixed; boundary="sm4nu43k4a2Rpi4c" > Content-Disposition: inline > - --sm4nu43k4a2Rpi4c > Content-Type: text/plain; charset=iso-8859-1 > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > Hi David, > > David T-G wrote: > > > How, however, is the proposed behavior (making $p_c_t generate a > > text/plain instead of an application/pgp message) different from what we > > have now with $p_c_t and $p_o_c? Note that I don't say that it fixes the > > problem you bring up, but it will fix the problem as Cristian wrote -- > > for any message that would have been text/plain anyway. > > $p_c_t and $p_o_c do exactly what is proposed: Create a clear-signed > message with "Content-Type: text/plain". This way, Outlook users see > the content of the message in the message window and not as two > attachments. This is *good*. > > Unfortunately, if the message contains any hi-bit characters (like > German umlauts or most other non-English languages), ie. if the charset > is not us-ascii, $p_c_t and thus $p_o_c never get evaluated. See the > function pgp_protect() in pgp.c for that. > > So for mails which are iso-latin-1 or something else, mutt will always > create a message that is PGP/MIME signed. While this might be what the > standard suggests (I don't really know), it breaks for a lot of people > and is not what I call user-friendly. > > > Right. Thus there are lots of folks with macros out there, which > > I personally don't like because I think that mutt should be able to > > handle it. As it stands I just whine a really lot and then just make > > my LookOut! users deal with MIME encryption :-) > > Exactly. I also have a macro, which re-maps the "y"-key (default for > send-message) and filters the message through `gpg --clearsign`. This=20 > is nearly perfect, as I don't have to remember anything special for > Outlook users. I just always hit "y" and mutt does the right thing. It > has three drawbacks, though: > > - I have to enter the passphrase, ie mutt won't use it's > remembered passphrase for those messages. Irritating, esp. > for newbies. > - There is a possibility of data loss. If you exceed all > retry-attempts of gnupg, because of a bad passphrase, the > message is lost, because it is replaced by the output of > gnupg, which is empty in this case. This is not common, but > nonetheless a Bad Thing [tm]. > - It's not very aesthetical (sp?). As you have said: mutt > should be able to do that internally. > > > % Here's a patch which creates pgp_force_traditional, which if > > % p_c_t is set, will always create a clear-signed PGP messages (not sure > > % for mails of attachments though). That way, p_o_c can do the job it's > > % supposed to do. I haven't tested it a lot since I wrote it, but it > > % appears to do the right thing. > >=20 > > That's a start. I haven't learned about either the workings of mutt or > > the structure of the messages, but does this generate iso-latin-1 or > > text/plain messages? > > It generates text/plain messages with a charset different from us-ascii, > eg. iso-latin-1. Ie, the headers look like this: > > Content-Type: text/plain; charset=3Diso-latin-1 > Content-Transfer-Encoding: 8bit > > BTW, you'll get exactly the same headers if you clear-sign the message > outside of mutt and send it then. Contrast messages that are created > with $p_c_t and $p_o_c, which only have this header: > > Content-Type: text/plain > > There is no Content-Transfer-Encoding; it would be 7bit though. > > I don't really now a lot about e-mail standards, however a message can > be text/plain and have any charset (as indicated above). > > BTW, I determine the Content-Type and the Transfer-Encoding by taking > the values from the original, non-signed message. Dunno if that's the > Right Thing [tm], but it appears to me, that clear-signing the message > outside of mutt would do exactly the same. Can someone from mutt-dev > clear that up? > > > % Patch is against mutt-1.3.24, I'll test it tomorrow against 1.3.25, and > > % you need to have the pgp_outlook_compat patch applied first. > > %=20 > > % I don't know a lot about the mutt source, so this might break stuff, > > % haven't tested it a lot. > >=20 > > I'll probably wait for you to test more and perhaps wait to see how the > > mutt source itself shakes down, but I like the idea. > > The problem is, that I don't know a lot about e-mail, I just use it > daily. :) In fact, I didn't check it with Outlook yet, I went to bed, > when I received a message without data loss (ie =E4=F6=FC did not become ??= > ?) > with the right headers. > > Also, with this patch $p_c_t will still be ignored, when the message is > not of text/plain, ie any message with attachment. See again > pgp_protect(), why this is so. I don't really know how to do it > differently, ie clear-signing the message and leaving the attachment as > it is or signing everything. I don't know enough about the mutt > workings. :( > Okay, this was long. Could someone with inside knowledge of mutt and > the relevant standards please comment on this patch? BTW, it won't > cause any data loss, the worst thing that can happen is that you receive > a message which signature can't be verified, so it would be nice, if > some people could test it. My access to an Outlook machine is somewhat > limited. :) > > Cheers, > Viktor > > PS: I resent the patch as yesterday's mail to mutt-dev got dropped, > because I wasn't subscribed. > - --=20 > Viktor Rosenfeld > WWW: http://www.informatik.hu-berlin.de/~rosenfel/ > > - --sm4nu43k4a2Rpi4c > Content-Type: text/plain; charset=us-ascii > Content-Disposition: attachment; filename="patch-1.3.24.vrr.force_traditional.1" > Content-Transfer-Encoding: quoted-printable > > diff -ur mutt-1.3.24-outlook+compress/init.h mutt-1.3.24-vrr/init.h > - --- mutt-1.3.24-outlook+compress/init.h Thu Jan 3 20:45:04 2002 > +++ mutt-1.3.24-vrr/init.h Thu Jan 3 20:39:56 2002 > @@ -1311,6 +1311,25 @@ > ** to generate messages readable by users of MS Outlook using PGP. > */ > =20 > + { "pgp_force_traditional", DT_BOOL, R_NONE, OPT_PGPFORCETRAD, 0}, > + /* > + ** .pp > + ** If pgp_create_traditional is defined above, this option will force > + ** the creation of old-style PGP messages for text/plain messages, even = > when > + ** the character set is different from us-ascii. > + ** > + ** .pp > + ** This option really only makes sense together with pgp_create_traditio= > nal > + ** and pgp_outlook_compat; when all three are set, Outlook users will be > + ** able to read any mail, including language-specific characters like > + ** German umlauts, without problems. > + ** > + ** .pp > + ** Note, however, that using the old-style PGP message format is > + ** \fBdeprecated\fP, and the using the old-style PGP message format with= > a > + ** character set other than us-ascii might result in broken signatures. > + */ > + > /* XXX Default values! */ > =20 > { "pgp_decode_command", DT_STR, R_NONE, UL &PgpDecodeCommand, 0}, > diff -ur mutt-1.3.24-outlook+compress/mutt.h mutt-1.3.24-vrr/mutt.h > - --- mutt-1.3.24-outlook+compress/mutt.h Thu Jan 3 20:45:04 2002 > +++ mutt-1.3.24-vrr/mutt.h Thu Jan 3 20:30:56 2002 > @@ -258,6 +258,7 @@ > #ifdef HAVE_PGP > OPT_VERIFYSIG, /* verify PGP signatures */ > OPT_PGPTRADITIONAL, /* create old-style PGP messages */ > + OPT_PGPFORCETRAD, /* force old-style PGP messages even for non us-asci= > i */ > OPT_PGPOUTLOOK, /* Create even older broken outlook compatible messa= > ges */ > #endif > =20 > diff -ur mutt-1.3.24-outlook+compress/pgp.c mutt-1.3.24-vrr/pgp.c > - --- mutt-1.3.24-outlook+compress/pgp.c Thu Jan 3 20:44:59 2002 > +++ mutt-1.3.24-vrr/pgp.c Fri Jan 11 01:21:47 2002 > @@ -1646,7 +1646,9 @@ > =20 > b =3D mutt_new_body (); > =20 > - - b->encoding =3D ENC7BIT; > + b->parameter =3D (PARAMETER *) malloc(sizeof(PARAMETER)); =20 > + b->parameter =3D memcpy(b->parameter, a->parameter, sizeof(PARAMETER)); > + b->encoding =3D a->encoding; > =20 > /* Outlook seems to work by scanning the message itself for PGP informat= > ion, */ > /* not the headers. If the headers are anything but text/plain, it will= > */ > @@ -1710,7 +1712,9 @@ > =20 > if ((msg->content->type =3D=3D TYPETEXT) && > !ascii_strcasecmp (msg->content->subtype, "plain") && > - - ((flags & PGPENCRYPT) || (msg->content->content && msg->content->con= > tent->hibin =3D=3D 0))) > + ((flags & PGPENCRYPT) || (msg->content->content && > + msg->content->content->hibin =3D=3D 0) || > + option(OPT_PGPFORCETRAD))) > { > if ((i =3D query_quadoption (OPT_PGPTRADITIONAL, _("Create an applicat= > ion/pgp message?"))) =3D=3D -1) > return -1; > > - --sm4nu43k4a2Rpi4c-- > > - --Bn2rw/3z4jIqBvZU > 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 > > iD8DBQE8P22EkWI06CMxQ0ARAhGFAJwKtB664mnovlWlXuMyjeVLd2GwEwCfV3tk > YzpOjKwU9qovei3tEvVNATk= > =wwX+ > - -----END PGP SIGNATURE----- > > - --Bn2rw/3z4jIqBvZU-- > > ------------------------------ > > Date: Fri, 11 Jan 2002 16:28:05 -0700 > From: Rob 'Feztaa' Park <[EMAIL PROTECTED]> > Subject: Re: Suggestion for List Etiquette > > - --wULyF7TL5taEdwHz > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > Alas! Roman Neuhauser spake thus: > > I guess that quite a few of the subscribers are just devoted to > > flooding this list with chitchat. I would suggest creating > > mutt-chat, so that those who feel the urge to send non-technical, OT > > stuff to mutt-users would have a place to go. > > I support this idea. This place would be really boring if it were all > technical, I think it's healthy to be sociable. If the socializing must > be in a different list, though with roughly the same group of people, > then I'm for it. > > - --=20 > Rob 'Feztaa' Park > [EMAIL PROTECTED] > - -- > In college, Biology is really Chemistry, Chemistry is really Physics, > Physics is really Calculus, and Calculus is really hard. > > - --wULyF7TL5taEdwHz > 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 > > iD8DBQE8P3UFPTh2iSBKeccRAoQyAJ9r+P/FwZHDSB2V8SuxLzHlOlysugCfQvRJ > Tl3Rrn3nhJRXdpLbjVzBUvg= > =TtvG > - -----END PGP SIGNATURE----- > > - --wULyF7TL5taEdwHz-- > > ------------------------------ > > Date: Fri, 11 Jan 2002 16:33:38 -0700 > From: Rob 'Feztaa' Park <[EMAIL PROTECTED]> > Subject: Be more clear (was: Re: mailboxes command confusion.) > > - --ffoCPvUAPMgSXi6H > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > Alas! Knute spake thus: > > > --=3D=3D Jerri =3D=3D-- > > > Homepage: http://www.jerri.de/ ICQ: 54160208 > >=20 > > It could be, ... > > No, I'm certain that that is Jerri's homepage and ICQ number. > > _PLEASE_ put your response directly after what you are replying to, it > makes everything so much easier to understand. > > - --=20 > Rob 'Feztaa' Park > [EMAIL PROTECTED] > - -- > "Things are more like they are now than they ever were before." > -- Dwight D. Eisenhower > > - --ffoCPvUAPMgSXi6H > 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 > > iD8DBQE8P3ZSPTh2iSBKeccRAstYAJ41Fc0oWNKB9/wyQyTh03pryL8SUQCeM7pt > 8xDaG0C0GSyme5fcrJoHu68= > =BpnM > - -----END PGP SIGNATURE----- > > - --ffoCPvUAPMgSXi6H-- > > ------------------------------ > > Date: Fri, 11 Jan 2002 16:37:55 -0700 > From: Rob 'Feztaa' Park <[EMAIL PROTECTED]> > Subject: Re: Suggestion for List Etiquette > > - --i3lJ51RuaGWuFYNw > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > Alas! Knute spake thus: > > This is quoted text: ----- End forwarded message ----- > >=20 > > So what do you think? > > (I think I need to put on my asbestos long john's!) > > You die. You die and go to hell! > > Just kidding ;) > > > 9o) > > BTW, what the heck is that thing? > > - --=20 > Rob 'Feztaa' Park > [EMAIL PROTECTED] > - -- > "Fiction writing is great. You can make up almost anything." > -- Ivana Trump > > - --i3lJ51RuaGWuFYNw > 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 > > iD8DBQE8P3dTPTh2iSBKeccRAs2xAJwKAcmT2m4m1H5WJ2z99S/vFQnz6QCeL1cH > QJWgpYcCXCzcuETeojFcPhY= > =OLt1 > - -----END PGP SIGNATURE----- > > - --i3lJ51RuaGWuFYNw-- > > ------------------------------ > > Date: Fri, 11 Jan 2002 16:44:05 -0700 > From: Rob 'Feztaa' Park <[EMAIL PROTECTED]> > Subject: Re: Getting Keys From Keyserver? > > - --iAL9S67WQOXgEPD9 > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > Alas! Stephan Seitz spake thus: > > > Getting needed keys from a keyserver is completely a function of > > > your pgp/gpg program... the keyserver line is all that's needed if > > > you're using gpg. (Well, it works for verifying sigs anyway... I've > >=20 > > Fine, but IIRC that only works if I wish to verify a mail. > > If I wish to send a mail, I can't do a keyserver lookup to search, if > > this person may have a pgp key on the server. > > Well, considering that gpg won't let you download named keys from > keyservers, only specified key IDs, if you want to encrypt something to > somebody who's key you don't know, it would be your best bet to ask them > for their key, then encrypt a message for them with it. > > - --=20 > Rob 'Feztaa' Park > [EMAIL PROTECTED] > - -- > "Fiction writing is great. You can make up almost anything." > -- Ivana Trump > > - --iAL9S67WQOXgEPD9 > 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 > > iD8DBQE8P3jFPTh2iSBKeccRArtCAJ9FtWBUf6cjV/RITlWjeNtuCYD1ZwCggqz1 > OGwlxT0Sxznm3n7jDDZEE2s= > =Intu > - -----END PGP SIGNATURE----- > > - --iAL9S67WQOXgEPD9-- > > ------------------------------ > > Date: Fri, 11 Jan 2002 17:00:14 -0700 > From: Rob 'Feztaa' Park <[EMAIL PROTECTED]> > Subject: Re: mail being returned > > - --k+G3HLlWI7eRTl+h > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > Alas! David T-G spake thus: > > ...and then Nick Wilson said... > > % In my muttrc I have set the hostname=3D"localhost" 'cos that's what it = > is. > > So if I were to email root@localhost, which one of us do you think would > get the message? You should pick a better hostname ;) > > > You really should pick a cool name for your machine, you know :-) > > Agreed. > > - --=20 > Rob 'Feztaa' Park > [EMAIL PROTECTED] > - -- > "What's the three words you never want to hear while making > love? 'Honey, I'm home.'" > -- Ken Hammond > > - --k+G3HLlWI7eRTl+h > 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 > > iD8DBQE8P3yOPTh2iSBKeccRAvVbAJ0aOYi4EKEWqfjSef0NciXnIK2QMQCePH7Y > Fkl1VYmR4ROelcNeS+GrGnE= > =R/8e > - -----END PGP SIGNATURE----- > > - --k+G3HLlWI7eRTl+h-- > > ------------------------------ > > Date: Sat, 12 Jan 2002 00:58:54 +0100 > From: Cristian <[EMAIL PROTECTED]> > Subject: Re: patch to force pgp_create_traditional on non-us-ascii mails (was: application/pgp breaks Pine, too (was: applying pgp-outlook patch)) > > - -----BEGIN PGP SIGNED MESSAGE----- > Viktor, > I agree with everything you say (though I do hope the story about > rebinding the y-key was a joke). Your patch is important for the > wide-spread use of PGP in non-english communication. > I just checked that with your patch, I can finally use Mutt to sign > messages in the iso-latin-1 charset in the traditional way and verify > it in Pine. > This is what I did exactly: > - - - compose message in ISO-Latin-1 > - - - using Mutt/1.3.25 with=20 > patch-1.3.15.sw.pgp-outlook.1 > patch-1.3.24.vrr.force_traditional.1 > - - - sign traditionally inside Mutt calling GnuPG 1.0.6 with > force-v3-sigs set using RSA key=20 > - - - open message at work in Pine 4.44 > - - - message is successfully verified on opening > by PGP-aware display filters (selfmade) calling PGP 2.6.3ia > - - - just to make shure: I can also verify the signature with GnuPG 1.0.6 > by hitting ESC P in Mutt. > Latin-1 characters such as German Umlauts, sharp s and Franco-German > quotes like these: =BB=E4=F6=FC=C4=D6=DC=DF=AB were still intact. > My test email had the header line, ``Content-Transfer-Encoding: 8bit''. > I don't know if there'll be problems if the message is transformed to > quoted/printable by an MTA. Would somebody else check that please? > > Okay, this was long. Could someone with inside knowledge of mutt and > > the relevant standards please comment on this patch? > I am not this person. > This Email is signed the same way as described above. So you can try > to verify it with whatever you use. > Cheers, > Cristian > - - --=20 > }{ Cristian Pietsch > }{ http://www.interling.de > - -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.6 (GNU/Linux) > Comment: Weitere Infos: siehe http://www.gnupg.org > iQCVAwUBPD98Pilhg9yhk42tAQGztQQApuEKOr8tf4sU9R9yVZPSEPHYffIW/NTf > UzJtiZpr8CBBi20uwqJBZwlS2RnH4wAeeRdLdR7Q2tXUkV0RsBJMdRa87vYyrfPm > IuP1vz4FjyicW3dtBycXRbm75GrjR3DeSxISBXSgMoHsYfDkm5rZ54njd1ATdsn4 > DWxJsWLPvRw=3D > =3DlHvr > - -----END PGP SIGNATURE----- > > ------------------------------ > > Date: Fri, 11 Jan 2002 16:43:43 -0800 > From: Jonathan Irving <[EMAIL PROTECTED]> > Subject: Re: Suggestion for List Etiquette > > - --C7zPtVaVf+AK4Oqc > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > Rob 'Feztaa' Park <[EMAIL PROTECTED]> [11 Jan 2002 16:37 -0700]: > > > 9o) > >=20 > > BTW, what the heck is that thing? > > He has a big nose and a monocle, obviously. > - --=20 > http://www.epic.org - Electronic Privacy Information Center > > - --C7zPtVaVf+AK4Oqc > Content-Type: application/pgp-signature > Content-Disposition: inline > > - -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.6 (SunOS) > > iD8DBQE8P4a8f0dtvRaW92oRApCNAJ0c3lOuLN69o/RO7ubDiu7yfNIrdgCgn8Fs > 19DdzGejOR3E42iex1CQpbs= > =Qfde > - -----END PGP SIGNATURE----- > > - --C7zPtVaVf+AK4Oqc-- > > ------------------------------ > > Date: Sat, 12 Jan 2002 01:47:17 +0100 > From: Viktor Rosenfeld <[EMAIL PROTECTED]> > Subject: Re: patch to force pgp_create_traditional on non-us-ascii mails (was: application/pgp breaks Pine, too (was: applying pgp-outlook patch)) > > - --xHFwDpU9dbj6ez1V > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > Hi Christian, > > > I agree with everything you say (though I do hope the story about > > rebinding the y-key was a joke). Your patch is important for the > > wide-spread use of PGP in non-english communication. > > Why? It's the best I could come up with. =20 > > > I just checked that with your patch, I can finally use Mutt to sign > > messages in the iso-latin-1 charset in the traditional way and verify > > it in Pine. > >=20 > > - - open message at work in Pine 4.44 > > - - message is successfully verified on opening > > by PGP-aware display filters (selfmade) calling PGP 2.6.3ia > > Great! > > My test email had the header line, ``Content-Transfer-Encoding: 8bit''. > > I don't know if there'll be problems if the message is transformed to > > quoted/printable by an MTA. Would somebody else check that please? > > This is the reason for my fear of broken signatures. If the > quoted-printable message is verified, the (mangled) signature will > obviously be wrong. Same with base64 and whatever. If the re-converted > text is verified, everything should work though. > > > This Email is signed the same way as described above. So you can try > > to verify it with whatever you use. > > 01:40 viktor@bart:~ $ gpg --verify christian > gpg: Signature made Sam 12 Jan 2002 00:58:54 CET using RSA key ID > A1938DAD > gpg: Good signature from "Christian Boltin Pietsch > <[EMAIL PROTECTED]>" > Could not find a valid trust path to the key. Let's see whether we > can assign some missing owner trust values. > > No path leading to one of our keys found. > > gpg: WARNING: This key is not certified with a trusted signature! > gpg: There is no indication that the signature belongs to the > owner. > gpg: Fingerprint: 38 CC 39 22 FE 4C 9A 95 12 F2 8A 15 71 72 DE 3F > 01:40 viktor@bart:~ $ > > Looks good! > > Cheers, > Viktor > - --=20 > Viktor Rosenfeld > WWW: http://www.informatik.hu-berlin.de/~rosenfel/ > > - --xHFwDpU9dbj6ez1V > 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 > > iD8DBQE8P4eUkWI06CMxQ0ARAl0MAJ4j+BQasAoZwi3RbTV4gLlaMA3CqwCffFLO > B9iKbQL3T9O+4HEe9dUBCgQ= > =vC5F > - -----END PGP SIGNATURE----- > > - --xHFwDpU9dbj6ez1V-- > > ------------------------------ > > End of mutt-users-digest V1 #954 > ******************************** >
