Re: some attachments disappearing
++ 26/12/15 15:20 -0500 - Fred Smith: > >This problem has been going on for some time, but it has lately become an >irritant: > >some emails in which photos or other images are sent arrive here with no >such item, neither attached, nor inline. For all of those e-mails, what MUA is used on the sending end? I have seen these behaviour before, but only with some versions of Apple's Mail.app. If there is an attachment, it should be visible when looking at the plain text of the actual message. You could do this by finding the message on your file system or possibly from within the pager by hitting the "e" key. -- Rejo Zenger E r...@zenger.nl | P +31(0)639642738 | W https://rejo.zenger.nl T @rejozenger | J r...@zenger.nl OpenPGP 1FBF 7B37 6537 68B1 2532 A4CB 0994 0946 21DB EFD4 XMPP OTR 271A 9186 AFBC 8124 18CF 4BE2 E000 E708 F811 5ACF Signal0507 A41B F4D6 5DB4 937D E8A1 29B6 AAA6 524F B68B 93D4 4C6E 8BAB 7C9E 17C9 FB28 03 signature.asc Description: PGP signature
Re: understanding PGP encrypt to myself
++ 14/11/15 22:47 -0500 - Xu Wang: >> >> A copy of the message will also be encrypted by your own public key and saved >> in the folder you have specified for Sent messages. It is this copy which >> you >> can decrypt with your private key later on, if you wish to read what you sent >> to the recipient. [...] >I see. So it is one email, but there is never actual double encryption >on the same text. It is two single encryptions. I think I am >understanding more. As I understand it: your message is encrypted to a session key, and that session key is encrypted with your and the recipients' key. That way, the message may have a large number of recipients, but doesn't increase in size as much. -- Rejo Zenger E r...@zenger.nl | P +31(0)639642738 | W https://rejo.zenger.nl T @rejozenger | J r...@zenger.nl OpenPGP 1FBF 7B37 6537 68B1 2532 A4CB 0994 0946 21DB EFD4 XMPP OTR 271A 9186 AFBC 8124 18CF 4BE2 E000 E708 F811 5ACF Signal0507 A41B F4D6 5DB4 937D E8A1 29B6 AAA6 524F B68B 93D4 4C6E 8BAB 7C9E 17C9 FB28 03 signature.asc Description: PGP signature
Re: Saving a message as unread
++ 10/05/15 22:49 -0400 - Xu Wang: After I am in Mutt and use the macro I mentioned above, if I then use my browser to go to gmail and then go to All mail, it shows up as unread. However, if I start all over again and use my browser to go to GMail and do the archiving using GMail's web interface, then the message shows up as read in GMail. Does that make sense? Not sure whether I have a correct understanding of your problem, but let's suppose I have, then this may be the solution: macro index \Ca enter-commandset resolve=noenterclear-flagNclear-flagOsave-message[mailbox]enternext-entryenter-commandset resolve=yesenter ... where [mailbox] designates the destination. Kind regards, -- Rejo Zenger E r...@zenger.nl | P +31(0)639642738 | W https://rejo.zenger.nl T @rejozenger | J r...@zenger.nl OpenPGP 1FBF 7B37 6537 68B1 2532 A4CB 0994 0946 21DB EFD4 XMPP OTR 271A 9186 AFBC 8124 18CF 4BE2 E000 E708 F811 5ACF Signal0507 A41B F4D6 5DB4 937D E8A1 29B6 AAA6 524F B68B 93D4 4C6E 8BAB 7C9E 17C9 FB28 03 signature.asc Description: PGP signature
Re: Multiple crypt-hook behavior
++ 19/04/15 13:30 -0700 - Kevin J. McCarthy: I've just pushed the multiple crypt hook patch along with Dale's $crypt_confirmhook option. Please let me know if there are any issues. I have been using the nightly build for a couple of days now, it seems to work flawlessly. Thanks for your work! -- Rejo Zenger E r...@zenger.nl | P +31(0)639642738 | W https://rejo.zenger.nl T @rejozenger | J r...@zenger.nl OpenPGP 1FBF 7B37 6537 68B1 2532 A4CB 0994 0946 21DB EFD4 XMPP OTR 271A 9186 AFBC 8124 18CF 4BE2 E000 E708 F811 5ACF Signal0507 A41B F4D6 5DB4 937D E8A1 29B6 AAA6 524F B68B 93D4 4C6E 8BAB 7C9E 17C9 FB28 03 signature.asc Description: PGP signature
Re: Multiple crypt-hook behavior
++ 17/04/15 14:53 -0700 - Kevin J. McCarthy: Another option could be something like: $crypt_use_hooks as a quadoption: - yes means all crypt-hooks are used without prompting - ask-yes/ask-no prompt for each hook - no disables all crypt-hooks. This could provide a way to disable the crypt-hooks in certain circumstances. I don't know if something like that is useful or is overkill. Not sure. I would set it to yes, as I have these well-defined and defined with the purpose that these particular should be used. For me, there is not a real added value, but then again, it doesn't hurt I think. -- Rejo Zenger E r...@zenger.nl | P +31(0)639642738 | W https://rejo.zenger.nl T @rejozenger | J r...@zenger.nl OpenPGP 1FBF 7B37 6537 68B1 2532 A4CB 0994 0946 21DB EFD4 XMPP OTR 271A 9186 AFBC 8124 18CF 4BE2 E000 E708 F811 5ACF Signal0507 A41B F4D6 5DB4 937D E8A1 29B6 AAA6 524F B68B 93D4 4C6E 8BAB 7C9E 17C9 FB28 03 pgp2XFNBY4UiL.pgp Description: PGP signature
Re: Multiple crypt-hook behavior
++ 03/04/15 18:44 -0700 - Kevin J. McCarthy: I'm cleaning up and looking into committing the multiple crypt hook patch, but need some feedback from people who use it. The current behavior (without that patch) is to prompt whether to use the crypt-hook value if one is found. If the user answers no then Mutt will use the original address for key selection instead. Since there can be at most one crypt-hook, this makes sense. With this patch, it's less clear what the correct behavior should be if the user user says no. The current patch will use the original address and perform key selection with it, but doing this multiple times doesn't seem right. I'm a heavy user of this patch. My use case is fairly simple: either it should encrypt to all of the keys that are listed in the crypt-hook, or to a subset of them or the message shouldn't be sent at all. I have specificaly selected and configured a number of key ID's for a mailinglist. This is a deliberate action, and if a key is not available there is no need to select an alternative. Keys are always available ay my keyring. If they are not, something has gone wrong. One of the reasons the key selection still fails is when a key is available, but unusable (e.g. the key has expired). In that case I would like to have the option to either send the message encrypted to the remaining keys (the other crypt-hooks), or to cancel the sending of the message. Anyway, that is me. :) -- Rejo Zenger E r...@zenger.nl | P +31(0)639642738 | W https://rejo.zenger.nl T @rejozenger | J r...@zenger.nl OpenPGP 1FBF 7B37 6537 68B1 2532 A4CB 0994 0946 21DB EFD4 XMPP OTR 271A 9186 AFBC 8124 18CF 4BE2 E000 E708 F811 5ACF Signal0507 A41B F4D6 5DB4 937D E8A1 29B6 AAA6 524F B68B 93D4 4C6E 8BAB 7C9E 17C9 FB28 03 pgp0G0Z1NvBAM.pgp Description: PGP signature
Re: Multiple crypt-hook behavior
++ 04/04/15 09:28 +0200 - Heinz Diehl: On 04.04.2015, Kevin J. McCarthy wrote: I'm cleaning up and looking into committing the multiple crypt hook patch, but need some feedback from people who use it. Where can I find the patch? See: - http://dev.mutt.org/trac/ticket/3727 - https://github.com/rejozenger/mutt-multiple-crypt-hook -- Rejo Zenger E r...@zenger.nl | P +31(0)639642738 | W https://rejo.zenger.nl T @rejozenger | J r...@zenger.nl OpenPGP 1FBF 7B37 6537 68B1 2532 A4CB 0994 0946 21DB EFD4 XMPP OTR 271A 9186 AFBC 8124 18CF 4BE2 E000 E708 F811 5ACF Signal0507 A41B F4D6 5DB4 937D E8A1 29B6 AAA6 524F B68B 93D4 4C6E 8BAB 7C9E 17C9 FB28 03 pgp6ifvk2rhm0.pgp Description: PGP signature
Re: Multiple crypt-hook behavior
++ 04/04/15 16:33 +0200 - Rejo Zenger: I have specificaly selected and configured a number of key ID's for a mailinglist. This is a deliberate action, and if a key is not available there is no need to select an alternative. Keys are always So, actually, the current situation where mutt asks whether it should use the key specified with the crypt-hook is superflucious in my setup. If I have designated a specific key for a specific user using the hook, there is no need to ask me for a verification. -- Rejo Zenger E r...@zenger.nl | P +31(0)639642738 | W https://rejo.zenger.nl T @rejozenger | J r...@zenger.nl OpenPGP 1FBF 7B37 6537 68B1 2532 A4CB 0994 0946 21DB EFD4 XMPP OTR 271A 9186 AFBC 8124 18CF 4BE2 E000 E708 F811 5ACF Signal0507 A41B F4D6 5DB4 937D E8A1 29B6 AAA6 524F B68B 93D4 4C6E 8BAB 7C9E 17C9 FB28 03 pgp8oIoQDUQRE.pgp Description: PGP signature
Re: Encrypting when possible
++ 31/03/15 11:47 -0700 - Kevin J. McCarthy: I've been working on this patch series for a while, and finally committed it to the repository yesterday. For those of you who would like to encrypt by default and don't mind compiling from the repository, please check it out. That sounds like a welcome feature. I have a encrypt by default policy and I have solved it by running a script on a daily basis that generates send-hooks for all e-mailaddress that it can find in my public keyring. So, a better solution is most welcome. :) To get a copy of your code, I just need to clone the default branch from the Mercurial repository? I haven't had a look at the code yet, but can you explain how it does work (e.g. how does it determine when there's a key for a recipient on the keyring and encrypting is feasable and when it is not)? Additionaly, may I draw your attention to these two tickets: - http://dev.mutt.org/trac/ticket/3727, which is patch to allow for encryption to multiple keys based on a single recipient (which is usefull when sending encrypted mail to mailinglist with a static set of subscribers) - http://dev.mutt.org/trac/ticket/3728, which is a bugreport for a case in which users are not able to read application/pgp-encrypted attachments (unless the user saves the attachments and runs gpg and openssl manually on the saved message part) Not sure if you can do anything with those, but the first one is ready to implement (I am using the patch myself on a daily basis). -- Rejo Zenger E r...@zenger.nl | P +31(0)639642738 | W https://rejo.zenger.nl T @rejozenger | J r...@zenger.nl OpenPGP 1FBF 7B37 6537 68B1 2532 A4CB 0994 0946 21DB EFD4 XMPP OTR 271A 9186 AFBC 8124 18CF 4BE2 E000 E708 F811 5ACF Signal0507 A41B F4D6 5DB4 937D E8A1 29B6 AAA6 524F B68B 93D4 4C6E 8BAB 7C9E 17C9 FB28 03 pgp_2WhxG69n3.pgp Description: PGP signature
Re: Encrypting postponed messages
++ 07/01/15 14:57 -0800 - Kevin J. McCarthy: I'm wondering if that is sufficient for people interested in the patch, or whether a quadoption for postpone_encrypt would be more useful. For a quadoption, I would keep the behaviour the same: the quadoption would only be consulted if the message encryption flag was set. Thanks for the patch, I will apply it one of these days. Seems to be a usefull addition for me. I don't need the quadoption solution, but that may be different for other people. However, a quadoption would somewhat make it more consistent with the other options. Would it be useful to be able to encrypt, even if the message encryption flag is not set? If so, I could use some opinions, because defining the interface for that starts to get complicated. To me, that is of no particular use. Against what version is the patch you have provided? -- Rejo Zenger E r...@zenger.nl | P +31(0)639642738 | W https://rejo.zenger.nl T @rejozenger | J r...@zenger.nl OpenPGP 1FBF 7B37 6537 68B1 2532 A4CB 0994 0946 21DB EFD4 XMPP OTR 271A 9186 AFBC 8124 18CF 4BE2 E000 E708 F811 5ACF pgpqj5KBWf9GJ.pgp Description: PGP signature
Re: integration with mu (or similar programm)
++ 20/05/14 08:34 +1000 - Cameron Simpson: [1] http://dev.mutt.org/trac/wiki/UseCases/SearchingMail My approach to this is twofold. That's an interesting approach. However, it still requires an external terminal (or screen session) to get this working, right? I was looking for something even better: having the results presented in the same window. I'd think you could adapt this approach to your own mail indexer. Sure, sure, but it wasn't exactly what I was looking for. Second best, for now. -- Rejo Zenger E r...@zenger.nl | P +31(0)639642738 | W https://rejo.zenger.nl T @rejozenger | J r...@zenger.nl OpenPGP 1FBF 7B37 6537 68B1 2532 A4CB 0994 0946 21DB EFD4 XMPP OTR 271A 9186 AFBC 8124 18CF 4BE2 E000 E708 F811 5ACF pgp_8iujhs7Qo.pgp Description: PGP signature
Re: integration with mu (or similar programm)
++ 20/05/14 19:55 +1000 - Cameron Simpson: I was looking for something even better: having the results presented in the same window. The results are presented in the current terminal/window. Yes, of course. I didn't look right, but I was more or less on the right track: it does open another instance of mutt, then switches back to the first instance when closing the second. Functional-wise, this does what I asked for. Thanks! Others who have replied, thanks! -- Rejo Zenger E r...@zenger.nl | P +31(0)639642738 | W https://rejo.zenger.nl T @rejozenger | J r...@zenger.nl OpenPGP 1FBF 7B37 6537 68B1 2532 A4CB 0994 0946 21DB EFD4 XMPP OTR 271A 9186 AFBC 8124 18CF 4BE2 E000 E708 F811 5ACF pgpZbTSPe9hwG.pgp Description: PGP signature
integration with mu (or similar programm)
Hi, Any implementation of mu into mutt I have found or could think of requires a two step process. One that does the actual search and compiles a list of results, another to browse this list. [1] Now, I would like to do this more smoothly: only give one command (one shortcut), provide the search string and have the results returned immediately. Does anyone know if this is possible - other than hacking the code of mutt? [1] http://dev.mutt.org/trac/wiki/UseCases/SearchingMail -- Rejo Zenger E r...@zenger.nl | P +31(0)639642738 | W https://rejo.zenger.nl T @rejozenger | J r...@zenger.nl OpenPGP 1FBF 7B37 6537 68B1 2532 A4CB 0994 0946 21DB EFD4 XMPP OTR 271A 9186 AFBC 8124 18CF 4BE2 E000 E708 F811 5ACF pgp2xJZaYKksD.pgp Description: PGP signature
Re: Encrypting to gpg groups
++ 07/04/14 13:36 +0200 - Patrick Ben Koetter: is it possible to automatically send encrpyted messages to GnuPG groups? Maybe you are looking for the solution I am using. I am sending lots of encrypted e-mail to a number of mailinglist with a list of subscribers that doesn't change frequently. I have in my configuration file lines like these: send-hook '~C n...@lists.example.net'set pgp_autoencrypt=yes crypt-hook n...@lists.example.net 0x012345678ABCDEFG crypt-hook n...@lists.example.net 0xABSDEFGH01234567 When sending mail to n...@lists.example.net, the mail will be signed against ID's 0x012345678ABCDEFG and 0xABSDEFGH01234567. This doesn't work out of the box. You need to patch mutt for that. See: - https://github.com/rejozenger/mutt-multiple-crypt-hook - https://github.com/rejozenger/mutt-multiple-crypt-hook/releases Hope this helps. -- Rejo Zenger E r...@zenger.nl P +31(0)639642738 W https://rejo.zenger.nl T @rejozenger PGP 1FBF 7B37 6537 68B1 2532 A4CB 0994 0946 21DB EFD4 pgpKw_QKjgJAF.pgp Description: PGP signature
Re: Cancel limit-search?
++ 21/03/14 14:13 -0400 - Peter P.: when I run a search across a folder using the limit function, I can't find a way to stop it while it is searching through messages (apart from killing mutt). Ctl-g doesn't work. Is there any this can be done? Limit to all, so limit to ~A. -- Rejo Zenger . r...@zenger.nl . 0x21DBEFD4 . https://rejo.zenger.nl GPG encrypted e-mail preferred . +31.6.39642738 . @rejozenger pgplBGgfpfcri.pgp Description: PGP signature
Re: how do disable Fcc?
++ 02/02/14 14:06 -0500 - glphvgacs: right now i have: set record = /dev/null but i have a feeling that's not the canonical way of doing this. any suggestions? Untested, but I presume unset record will work. -- Rejo Zenger . r...@zenger.nl . 0x21DBEFD4 . https://rejo.zenger.nl GPG encrypted e-mail preferred . +31.6.39642738 . @rejozenger pgpKJtd4JiZ9R.pgp Description: PGP signature
Re: folder-hook for sending to lists
++ 02/02/14 14:05 -0500 - glphvgacs: when starting the Mail composition in mutt, is there a way skip the 'To:' header by filling it up based on a given pattern? i don't think a folder-hook would do this since i don't think there is such a thing as 'set to = ' in configuration file (correct me if i'm wrong please). so perhaps a macro? Untested, probably something like the following will work: unmy_hdr To: -- Rejo Zenger . r...@zenger.nl . 0x21DBEFD4 . https://rejo.zenger.nl GPG encrypted e-mail preferred . +31.6.39642738 . @rejozenger pgp8ofTavLqC2.pgp Description: PGP signature
Re: auto reply to html-mails
++ 20/01/14 21:40 +0100 - Jan-Herbert Damm: i would like to send an automatic answer to html-mails sent to me (because i'm tired of writing back that i prefer plain-text). I am aware that this is hardly an issue of mutt, but rather procmail or scripting. But i am curious how this could be approached. Procmail would suffice and definately for a rudimentary filter: :0 * ^Content-type: text/html * ! ^X-Loop: autoreply_because_html | (formail -rt \ -APrecedence: junk \ -AX-Loop: autoreply_because_html ; \ cat $HOME/body_of_autoreply.txt) | $SENDMAIL -t Or something along those lines. Untested. Procmail has lots of example in the procmailex manpage as well as on the internet. -- Rejo Zenger . r...@zenger.nl . 0x21DBEFD4 . https://rejo.zenger.nl GPG encrypted e-mail preferred . +31.6.39642738 . @rejozenger pgpsJs4E3Pe5M.pgp Description: PGP signature
Re: sending encrypted mail to mailinglist
++ 08/12/13 10:21 -0700 - Chris Down: not a mailing list thread where none of us are lawyers. Either way, I [...] No. We are not lawyers. So, I contacted a well-known Dutch lawyer. His response was practically the same as Remco Rijnders': given the circumstances it's safe to assume GPLv2 applies to the patches of Dale (as they are derivates to an aplication that was released under GPLv2 and GPLv2 requires derivates to be released under the same license). I mentioned the theoretical possibility of Dale having received the code of mutt under a different license. The lawyer replied with the notion that this would be extremely unlikely and that, under Dutch law [1], in such cases it's safe to asume it was released under GPLv2. [1] Artikel 3:35 Burgerlijk Wetboek. -- Rejo Zenger . r...@zenger.nl . 0x21DBEFD4 . https://rejo.zenger.nl GPG encrypted e-mail preferred . +31.6.39642738 . @rejozenger pgpQVGGesNi6i.pgp Description: PGP signature
Re: sending encrypted mail to mailinglist
Hi Chris and others, I'll start with Chris' most interesting question: If you wanted to help others, why did you license it under such a restrictive license? If someone used the GPLv2 to license any of my work because I hadn't specified a license, I would be pretty annoyed, because the GPL is awful. I choose to use GPLv2 because that's exactly the same license that mutt uses. From the wide range of choices, that seemed to me to be the most fairest. Then Chris also mentioned the consequences of copyright a bit (on which, contrary to what he seems to think, not something we disagree about): Copyright doesn't even expire on death in most countries. I'd consider uncontactable to be less egregious than dead. I am aware of that. To quote myself: my comments were not to justify my behaviour, just an explanation. I am aware of the fact that the Berner Convention has this clause that copyright expires 70 years (or technically, between 70 and 71 years) after the death of the author. And I am aware that there's a lively debate on this, as not being able to determine the owner or not being able to contact owner is considered to be a problem: orphaned works. Credit does not mitigate copyright violation. Like I said: I am aware of that. I will not repeat quoting myself. -- Rejo Zenger . r...@zenger.nl . 0x21DBEFD4 . https://rejo.zenger.nl GPG encrypted e-mail preferred . +31.6.39642738 . @rejozenger pgp5u6waLYwqt.pgp Description: PGP signature
Re: sending encrypted mail to mailinglist
++ 08/12/13 07:05 +0100 - Remco Rijnders: The existing patches by Dale Woolridge, and made publically available* are patches for mutt to enhance its functionality. They are thus a derivative work. As mutt is GPLv2 licensed, so must derivative works be, even when Dale's patches do not contain any copyright or license information. The only [...] I believe Rejo is within rights to publish these modified patches under a GPLv2 license. IATNAL. Good catch. -- Rejo Zenger . r...@zenger.nl . 0x21DBEFD4 . https://rejo.zenger.nl GPG encrypted e-mail preferred . +31.6.39642738 . @rejozenger pgplpF8tZ9UEZ.pgp Description: PGP signature
Re: sending encrypted mail to mailinglist
++ 16/09/13 23:12 +0200 - Rejo Zenger: I am using mutt to send encrypted e-mail to mailinglist with a small and stable set of subscribers. In order to automate this I am running 1.5.16 with a slightly modified patch for 1.5.6 from [1]. This patch allows me to define multiple crypt-hook like: [...] Remco Rijnders transcribed this patch to work with mutt version 1.5.22 and the patch now can be foudn here: https://github.com/rejozenger/mutt-multiple-crypt-hook. With this patch, you can have multiple crypt-hook instances with the same pattern (recipient). This allows one to specify multiple key-ids for a particular pattern (recipient). This comes in handy when one wants to send encrypted email to a mailinglist with a static set subscribers. This patch was originaly written by Dale Woolridge for mutt versions 1.5.3 to 1.5.6. Dale Woolridge didn't mention the license under which he released his patch to the public. I have taken the liberty to release this patch under a GPLv2 license. -- Rejo Zenger . r...@zenger.nl . 0x21DBEFD4 . https://rejo.zenger.nl GPG encrypted e-mail preferred . +31.6.39642738 . @rejozenger pgpYWpI0WaAKI.pgp Description: PGP signature
Re: sending encrypted mail to mailinglist
++ 07/12/13 13:53 -0700 - Chris Down: This patch was originaly written by Dale Woolridge for mutt versions 1.5.3 to 1.5.6. Dale Woolridge didn't mention the license under which he released his patch to the public. I have taken the liberty to release this patch under a GPLv2 license. That's not even close to how copyright works (q.v. Berne Convention). Go ask the copyright holder what license it is under, or don't do anything at all. No, I know about that. The repository no longer exists. Not to justify my behaviour, just an explanation: - I have made several attempts to contact Dave before (on the availability of updated patched, not the license), but to no avail. - As, I presume, he has made his patches available to the general public with the intention to help others with a similar problem and, I presume, he has no longer interest in maintaining the patches himself, I assumed he would not have a problem in someone else putting an effort in creating an updated version of his patches. Yes, these are just pre- and assumptions. - For the same reason I presume he has made the earlier version of his patches available to the general public, I wanted to make the updated version available to the general public. I am aware of all the effort he (and Remco) has put in it, which is why I credited them. - I know how copyright works. Of course. I am aware that there is no room for these afformentioned pre- and assumptions in copyright. So, I just removed the repository from github.com. -- Rejo Zenger . r...@zenger.nl . 0x21DBEFD4 . https://rejo.zenger.nl GPG encrypted e-mail preferred . +31.6.39642738 . @rejozenger pgppAigZlmT64.pgp Description: PGP signature
Re: mutt: new user
++ 17/11/13 08:16 -0600 - rlhar...@oplink.net:
$ mkdir -p ~/.mail/archive/(cur,new,tmp)
That should have curly brackets and read:
mkdir -p ~/.mail/archive/r{ur,new,tmp}
--
Rejo Zenger . r...@zenger.nl . 0x21DBEFD4 . https://rejo.zenger.nl
GPG encrypted e-mail preferred . +31.6.39642738 . @rejozenger
pgpbOa5i5QYD_.pgp
Description: PGP signature
Re: mutt: new user
++ 17/11/13 20:48 +0100 - Suvayu Ali:
$ mkdir -p ~/.mail/archive/(cur,new,tmp)
That should have curly brackets and read:
mkdir -p ~/.mail/archive/r{ur,new,tmp}
Correcting the typo:
mkdir -p ~/.mail/archive/{cur,new,tmp}
Right. :)
I was in insert mode of vim already, when I see the typo.
--
Rejo Zenger . r...@zenger.nl . 0x21DBEFD4 . https://rejo.zenger.nl
GPG encrypted e-mail preferred . +31.6.39642738 . @rejozenger
pgpZVsF_o4IIT.pgp
Description: PGP signature
Re: viewing encrypted multipart attachments
++ 22/10/13 12:38 + - miro: In addition to this, the MIME-structure is: - multipart/mixed - multipart/encrypted - application/pgp-encrypted - application/octet-stream - multipart/mixed - text/plain - binary/octet-stream - text/plain Anyway, thanks a lot for helping me access the encrypted attachment (binary/octet-stream) from within mutt. [...] I'm not expert here, but do you have urlview installed? And what are the other programs, don't remember but those that view the M$ word docs... (there must be mention in the manual and/or on the wiki) And if you have all those installed, well, then, try debugging... The problem is not that I don't have a viewer available. If the binary/octet-stream would be html or something else, the problem would remain. The shortcut v will show the hierarchy like this: - multipart/mixed - multipart/encrypted - text/plain But it won't make accessible what is inside the multipart/encrypted container. -- Rejo Zenger . r...@zenger.nl . 0x21DBEFD4 . https://rejo.zenger.nl GPG encrypted e-mail preferred . +31.6.39642738 . @rejozenger pgp00y9qipjo0.pgp Description: PGP signature
Re: viewing encrypted multipart attachments
++ 23/10/13 19:03 +0100 - Mick: The problem is not that I don't have a viewer available. If the binary/octet-stream would be html or something else, the problem would remain. The shortcut v will show the hierarchy like this: - multipart/mixed - multipart/encrypted - text/plain But it won't make accessible what is inside the multipart/encrypted container. No it won't. It requires a two step process of gpg decrypting it, then piping it to the application that can handle the mime type of the file; you may need something like xdg-open to process it and call the default application for the mime type, or perhaps .mailcap can play a role here? Someone with better knowledge in this should come along soon to explain. Thanks for all your help, fellow listmembers! I understand it first needs to be decrypted, but I am not sure whether I do understand the second part. I don't want the binary/octet-stream inside the multipart/encrypted to be rendered automatically. It's fine if it just shows the default message [1]. I don't have a problem opening the binary/octet-stream part as long as it is not included in a multipart/encrypted container. The problem is, I can't select it binary/octet-stream within the multipart/encrypted container as, after I hit v the inital view the hierarchy is collapsed and is rendered as quoted above. If I scroll down to the multipart/encrypted part, then hit enter, it'll reveal all parts it contains but it'll be shown as plain text (and I am not able to specifically select the binary/octet-stream part and hit enter to open in it's default application. [1] ... is unsupported (use 'v' to view this part) -- Rejo Zenger . r...@zenger.nl . 0x21DBEFD4 . https://rejo.zenger.nl GPG encrypted e-mail preferred . +31.6.39642738 . @rejozenger pgpnxM60Tp7lV.pgp Description: PGP signature
viewing encrypted multipart attachments
Hi, Sometimes, I receive e-mails that are (at least partly) encrypted and that included attachments. I am not able to view those attachments. So, when I open the message I see: | [-- Attachment #1 --] | [-- Type: multipart/encrypted, Encoding: 7bit, Size: 1.9M --] | | [...] | | [-- The following data is PGP/MIME encrypted --] | | [-- Attachment #1 --] | [-- Type: text/plain, Encoding: quoted-printable, Size: 1.2K --] | | [...] | | [-- Attachment #2: column.pdf --] | [-- Type: binary/octet-stream, Encoding: base64, Size: 1.9M --] | | [-- binary/octet-stream is unsupported (use 'v' to view this part) --] | | [-- End of PGP/MIME encrypted data --] | | [-- Attachment #2 --] | [-- Type: text/plain, Encoding: 7bit, Size: 0.1K --] So, in order to view the attachment, I should prees v. When doing so, I get to this: |I 1 no description [multipa/encrypted, 7bit, 1.9M] |I 2 no description [text/plain, 7bit, us-ascii, 0.1K] This isn't helpful, as I am unable to view the attachment. How should I do this? How am I supposed to see the attachment (column.pdf in the example)? Thanks for the help! -- Rejo Zenger . r...@zenger.nl . 0x21DBEFD4 . https://rejo.zenger.nl GPG encrypted e-mail preferred . +31.6.39642738 . @rejozenger pgpKivyNhVAKH.pgp Description: PGP signature
Re: viewing encrypted multipart attachments
++ 16/10/13 17:36 +0200 - Rejo Zenger: Sometimes, I receive e-mails that are (at least partly) encrypted and that included attachments. I am not able to view those attachments. So, when I open the message I see: [...] So, in order to view the attachment, I should prees v. When doing so, I get to this: |I 1 no description [multipa/encrypted, 7bit, 1.9M] |I 2 no description [text/plain, 7bit, us-ascii, 0.1K] This isn't helpful, as I am unable to view the attachment. How should I do this? How am I supposed to see the attachment (column.pdf in the example)? In addition to this, the MIME-structure is: - multipart/mixed - multipart/encrypted - application/pgp-encrypted - application/octet-stream - multipart/mixed - text/plain - binary/octet-stream - text/plain Anyway, thanks a lot for helping me access the encrypted attachment (binary/octet-stream) from within mutt. -- Rejo Zenger . r...@zenger.nl . 0x21DBEFD4 . https://rejo.zenger.nl GPG encrypted e-mail preferred . +31.6.39642738 . @rejozenger pgpCVWP11Of0R.pgp Description: PGP signature
message could not copy upon opening message
Hi, I have https://rejo.zenger.nl/tmp/mail.txt as a message in my mailbox. When I attempt to open the message (by hitting enter after selecting), I'll get the error Could not open message in return and I am left in the mailbox overview. When running with -d5 I get: [...] pgp.c:520: mutt_mktemp returns /tmp/mutt-ix-501-8083-2. Checking mailcap file: /Users/rejo/.mailcap mailcap entry: text/html; elinks -dump %s ; copiousoutput field: copiousoutput handler.c:1589: mutt_mktemp returns /tmp/mutt-ix-501-8083-3. Checking mailcap file: /Users/rejo/.mailcap mailcap entry: text/html; elinks -dump %s ; copiousoutput field: copiousoutput pgp.c:520: mutt_mktemp returns /tmp/mutt-ix-501-8083-4. commands.c:111: mutt_mktemp returns /tmp/mutt-ix-501-8083-5. WEED is Set Reorder: x = 0; hdr_count = 1 Reorder: x = 0; hdr_count = 1 Reorder: x = 0; hdr_count = 1 Reorder: x = 0; hdr_count = 1 Reorder: x = 0; hdr_count = 1 Reorder: x = 0; hdr_count = 1 handler.c:1589: mutt_mktemp returns /tmp/mutt-ix-501-8083-6. Could not copy message mutt_index_menu[613]: Got op 145 Any clues as to why? -- Rejo Zenger . r...@zenger.nl . 0x21DBEFD4 . https://rejo.zenger.nl GPG encrypted e-mail preferred . +31.6.39642738 . @rejozenger pgp2e2qO0PtH7.pgp Description: PGP signature
Re: message could not copy upon opening message
++ 05/10/13 13:27 +0200 - Christian Brabandt: Any clues as to why? This is just a guess, but do you have enough space left on the device where /tmp is mounted? Yup. More than enough. Additionaly, this is reproducable on multiple (similar) systems (with none of them running out of disk space :P)). -- Rejo Zenger . r...@zenger.nl . 0x21DBEFD4 . https://rejo.zenger.nl GPG encrypted e-mail preferred . +31.6.39642738 . @rejozenger pgpyUI2XORZzF.pgp Description: PGP signature
Re: sending encrypted mail to mailinglist
++ 17/09/13 19:56 +0200 - Remco Rijnders: Now I am willing to give it try and update the patch to reflect the current code-base. However, as I am not a coder and definately not C, such an update will most likely take me quite some time. Before I would embark on such a journey: has anyone this done already? :) [...] As I had to cancel a key signing with you at The Hague HS train station years ago, I do owe you a small favour. I have edited the patch of [1] so it hopefully applies to the current 1.5.21 mutt release*. Note, I have not tested it myself, you can be the guinea pig :-) Ha, that's sounds like a deal! For what it is worth: I had already forgotten about our cancelled appointment. Still, thanks a lot for the offer. From your second e-mail I understand the proposed patch is not working, so I won't test it. However, if you have a new patch, I'm happy to be a guinea pig. *) The original patch was also nice enough to update the documentation to document this change, I'm too lazy for that as the documentation files seem to have changed / moved / depend on some other patch. The format of the document has changed from one markup language to the other. If you do the code, I'll do the documentation. :P) -- Rejo Zenger . r...@zenger.nl . 0x21DBEFD4 . https://rejo.zenger.nl GPG encrypted e-mail preferred . +31.6.39642738 . @rejozenger pgp8RemZRBFMW.pgp Description: PGP signature
Re: why is there no auto $ (save changes to mailbox)?
++ 11/08/09 18:41 +0200 - Rocco Rutte: I can't think of a reason why this would be bad (especialy if it's configurable and the default is off). [...] For eexample, you tag tag delete messages and cover messages you didn't want, or have hooks like me that mark duplicates for duplication which would delete valid mail automatically if I weren't paying [...] These are automatically deleted after you have marked them for deletion but this time you did the latter using a hook, instead of hitting a key. For sure, I can understand you do not want to use such a auto-sync fuctionality. This is why such a variable should be left off by default (and configurable). If it's off by default, I think this functionality would be a usefull addition. It's not something I am missing now per se, but I would consider start using it when it's available. -- Rejo Zenger . r...@zenger.nl . 0x21DBEFD4 . https://rejo.zenger.nl GPG encrypted e-mail prefered. signature.asc Description: Digital signature
Re: why is there no auto $ (save changes to mailbox)?
++ 10/08/09 16:44 +0200 - Michael Tatge: there is no automatic way to execute $. i.e. save changes to mailbox. This is particularly a problem for IMAP because losing your internet connection (e.g. sleeping your laptop) usually means losing mailbox changes. No, there isn't. And that's a good thing (TM). I don't want messages to be auto deleted. No messages will be auto deleted. The only thing that happens is that messages you earlier have marked as to be deleted will be actually deleted. Or better, any changes you have made to the status of the message is comitted. The behaviour wouldn't be any different from exiting a mailbox or pressing $. And, in the spirit of mutt, such a setting would be configurable. One can turn it on or off and set the interval. I can't think of a reason why this would be bad (especialy if it's configurable and the default is off). -- Rejo Zenger . r...@zenger.nl . 0x21DBEFD4 . https://rejo.zenger.nl GPG encrypted e-mail prefered. signature.asc Description: Digital signature
Re: multipart/alternative question
++ 16/07/09 09:03 -0500 - Kyle Wheeler: Since mutt is set to prefer text/plain, all I see is the plain text message, with no indication that there is an attachment (or even an html part). First, of course there's no obvious indication that there's an html part. Why should there be? Unless you press v to view the MIME hierarchy of the message, mutt doesn't tell you about alternative components to your email. [...] The same issue has been discussed before on this list: [1]. Kyle did a good job of explaining at [2]. [1] http://www.mail-archive.com/mutt-users@mutt.org/msg37364.html [2] http://www.mail-archive.com/mutt-users@mutt.org/msg37430.html -- Rejo Zenger . r...@zenger.nl . 0x21DBEFD4 . https://rejo.zenger.nl GPG encrypted e-mail prefered. signature.asc Description: Digital signature
Re: accecepted ssl certificate suddenly not remembered
++ 09/07/09 21:41 +0200 - Rejo Zenger: Hmm. Kinda sounds like a certificate problem to me. When does your certificate expire? I'm guessing it expired yesterday. [...] No, it will be valid for some more months. However, your remark made me investigate the certificate (using openssl s_client) and it seems there is another problem with the certificate indeed. Will investigate and update when I have cleared this. I haven't finished checking out this particular problem yet, but I have another question... While investigating the cause yesterday, I installed the most recent development version of mutt and this version (1.5.20, running with exactly the same configuration) doesn't barth this warning about the certificate. Why would that be? -- Rejo Zenger . r...@zenger.nl . 0x21DBEFD4 . https://rejo.zenger.nl GPG encrypted e-mail prefered. signature.asc Description: Digital signature
accecepted ssl certificate suddenly not remembered
Hi,
I am running mutt from the official Ubuntu Hardy repository on a x86_64
server. As of today, mutt is no longer able to remember previously
accepted SSL certificates and is unable to the certificate_file.
When I remove the default $certificate_file, first time I startup mutt
it will present me with some details of the certificate and asks me to
reject it, accept it once or accept it permanently. When I choose the
latter, I can proceed using mutt. Then, after closing and restarting
mutt, it will show me the certificate again, it will ask me the same
question, but it's no longer possible to save it. It will barf back a
warning: couldn't save certificate.
I can't think of a reason for this to suddenly popup. Certificate hasn't
changed, I haven't made a change to mutt or it's environment (or at
least, I can remember...).
A small snippet from a strace:
| write(1, \33[H\33[0;10;1m\33[33m\33[41m-- Mutt: TLS/SSL Certificate
check\33[K\r\n\33[0;10m\33[37mThis certificate belongs to:\r\n
|rejo.zenger.nl\r\n rej..., 565) = 565
| rt_sigaction(SIGINT, {0x4645d0, [], SA_RESTORER, 0x7f536d000100}, NULL, 8) = 0
| read(0, a, 1) = 1
| rt_sigaction(SIGINT, {0x4645d0, [], SA_RESTORER|SA_RESTART, 0x7f536d000100},
NULL, 8) = 0
| open(/home/rejo/.mutt_certificates, O_WRONLY|O_CREAT|O_APPEND, 0666) = 5
| fstat(5, {st_mode=S_IFREG|0600, st_size=2538, ...}) = 0
| mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f536c2fc000
| fstat(5, {st_mode=S_IFREG|0600, st_size=2538, ...}) = 0
| lseek(5, 2538, SEEK_SET)= 2538
| close(5)= 0
| munmap(0x7f536c2fc000, 4096)= 0
| write(1, \7, 1) = 1
| write(1, \r\33[43d\33[31mWarning: Couldn\'t save
certificate\33[37m\33[K\33[39m\33[0;10m, 65) = 65
| rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
| rt_sigaction(SIGCHLD, NULL, {0x464260, [],
SA_RESTORER|SA_RESTART|SA_NOCLDSTOP, 0x7f536d000100}, 8) = 0
| rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
| nanosleep({2, 0}, {2, 0}) = 0
| write(1, \r\33[37mSSL/TLS connection using TLS 1.0 (DHE RSA/AES 256
CBC/SHA)\33[39m\33[0;10m, 76) = 76
The file to save it to does exist, seems to be a correctly formatted
file and has the right permissions:
| r...@trillian:~$ head -4 /home/rejo/.mutt_certificates
| #H localhost 816B 21E4 F1D3 EFF6 9D30 085E 524B DEFC
| -BEGIN CERTIFICATE-
| MIIDXDCCAsWgAwIBAgIJAKedR4iKYzkZMA0GCSqGSIb3DQEBBAUAMHUxCzAJBgNV
| BAYTAk5MMQswCQYDVQQIEwJaSDESMBAGA1UEBxMJUm90dGVyZGFtMRAwDgYDVQQK
| r...@trillian:~$ ls -la .mutt_certificates
| -rw--- 1 rejo rejo 2538 2009-07-09 17:51 .mutt_certificates
| r...@trillian:~$ lsattr .mutt_certificates
| -- .mutt_certificates
Now, I have found others having the same problem. But, apart from a few
workarounds, I haven't been able to find the real cause (and the proper
solution).
So, for one reason or another mutt is unable to find the alredy present
certificate in the file and is then unable to add. Anyone sees why this
happens?
--
Rejo Zenger . r...@zenger.nl . 0x21DBEFD4 . https://rejo.zenger.nl
GPG encrypted e-mail prefered.
signature.asc
Description: Digital signature
Re: accecepted ssl certificate suddenly not remembered
++ 09/07/09 14:29 -0500 - Kyle Wheeler: Hmm. Kinda sounds like a certificate problem to me. When does your certificate expire? I'm guessing it expired yesterday. [...] No, it will be valid for some more months. However, your remark made me investigate the certificate (using openssl s_client) and it seems there is another problem with the certificate indeed. Will investigate and update when I have cleared this. Thanks a lot for the input. -- Rejo Zenger . r...@zenger.nl . 0x21DBEFD4 . https://rejo.zenger.nl GPG encrypted e-mail prefered. signature.asc Description: Digital signature
Re: mutt removing stuff in brackets from subject
++ 18/06/09 14:23 +0200 - Rocco Rutte: I see. I expected mutt to use this regular expression to determine whether it should prepand the current subject with Re: or that it should leave it intact (if there is a match) - instead of removing whatever is matched and replacing it. That has the potential to produce a horrible mess like: Re: Aw: Re: ... that is unreadable. It's not really relevant, but I disagree. If the behaviour would be like I said above, mutt won't make things worse. If the regular expression matched both Re: and Aw: and otehr variations, then mutt would recognize the subject is already prepended and would not touch the subject to do it again. So, if subject is Example, it would be prepended with Re: and if the subject is something like Re: Example or even Re: Aw: Re: Example (which both would match the given regular expression) it would leave the subject alone. As a result, mutt would never create a mess like Re: Aw: Re: - but it would leave it that way if it's there already. -- Rejo Zenger . r...@zenger.nl . 0x75FC50F3 . https://rejo.zenger.nl GPG encrypted e-mail prefered. signature.asc Description: Digital signature
Re: mutt removing stuff in brackets from subject
++ 17/06/09 14:57 +0200 - Michael Tatge: Mutt will match $reply_regexp match against the subject and replace everything matching (at the start of the string) with just Re: Say you get a message with the subject Aw: test and reply to it. You get with the default reply_regexp Re: test. I see. I expected mutt to use this regular expression to determine whether it should prepand the current subject with Re: or that it should leave it intact (if there is a match) - instead of removing whatever is matched and replacing it. Thanks for the clarification. -- Rejo Zenger . r...@zenger.nl . 0x75FC50F3 . https://rejo.zenger.nl GPG encrypted e-mail prefered. signature.asc Description: Digital signature
Re: Maildir or mbox?
++ 10/05/09 17:26 +0100 - Rafal Czlonka: Chris Bannister wrote: You can convert your mbox to maildir first. The only difference between mbox and maildir in procmail is / at the end of the mailbox name. No, that is not the only difference. Maildir doesn't require locking. Yes, I know that, thank you. Still, in procmail, the only difference between setting up those two is / at the end of the mailbox name. Well, from a practical point of view, this is not completely true. As noted by Chris, maildir does not require file locking. The other one, mbox, does. When writing recipes, you should tell when procmail when to use locking and when it should not. For example, for a mbox mailbox, one would use: :0: /home/example/mail For a maildir the same thing would be: :0 /home/example/mail/ There are two differences: the trailings slash in the mailbox name and the trailing colon on the first line of the recipe. If the colon is present, procmail will use file locking. Without the colon, procmail will not lock the file before writing. Anyway, this is off topic. :P) -- Rejo Zenger . r...@zenger.nl . 0x75FC50F3 . https://rejo.zenger.nl GPG encrypted e-mail prefered. signature.asc Description: Digital signature
Re: Sort the mbox by arbitrary way?
++ 08/05/09 20:35 +0800 - Wu, Yue: When I start mutt -y to read the mbox mails, mutt always sort them by alphabetic sequence, can I configure its sorting method to fit my preference? I guess http://www.mutt.org/doc/manual/manual-6.html#sort is what you are looking for? -- Rejo Zenger . r...@zenger.nl . 0x75FC50F3 . https://rejo.zenger.nl GPG encrypted e-mail prefered. signature.asc Description: Digital signature
Re: not detecting new mail in MailDir format?
++ 25/04/09 07:31 +1000 - Cameron Simpson:
[pid 28316] stat(/home/cameron/mail/me, {st_mode=S_IFDIR|0755,
st_size=4096, ...}) = 0
[pid 28316] stat(/home/cameron/mail/me, {st_mode=S_IFDIR|0755,
st_size=4096, ...}) = 0
It makes no attempt to stat me/new or me/cur, or to read them.
My feeling says, mutt doesn't know about your mailboxes being maildir
format. That brings us to the mbox_type variable:
and mentions maildir here:
set maildir_header_cache_verify=no
set mbox_type=Maildir
I am not sure whether this is of any influence, but I have a lowercase
only value for this variable:
| r...@trillian:~$ grep mbox_type .mutt/muttrc.common
| set mbox_type = maildir
Maybe, this value is case sensitive? I don't this is the problem, as it
is mentioned in the official documentation with the capital M. However,
without any other solutions, you may want to test this?
The official documentation also denotes mbox being the default. Ergo,
if unset, it will use mbox.
Are you sure your configuration file is actually read? What happens if
you set the mbox_type variable inside mutt (using :set mbox_type =
maildir in the index) and then check for mail?
--
Rejo Zenger . r...@zenger.nl . 0x75FC50F3 . https://rejo.zenger.nl
GPG encrypted e-mail prefered.
signature.asc
Description: Digital signature
Re: no list-id header for mutt-u...@mutt.org
++ 12/04/09 07:12 +0200 - Michael Wagner: I tried to use lisd-id to filter mutt mailing list in with procmail. But I did not find it in mutt mailing list emails. So how do you filter out mutt mailing list emails? Hello Zhengquan, for the mutt-users ML I have the following recipe in my procmailrc: --+ :0 H: | * ^List-Post:.*mailto:mutt-users@mutt.org.* | mutt-users| Few remarks on this procmail recipe: - The H flag is default when filtering messages, there is no need to specify it in this recipe. - The . matches any character and should be escaped when matching a literal dot. Highly theoretical of course. - The .* at the end isn't needed, as it will match the regular expression without an ending. In other words, if you want to explicitly this phrase and there shouldn't be no characters aftewards, use the $ marker. So, this would become: :0: * ^List-Post:.*mailto:mutt-us...@mutt\.org mutt-users Or, as this header isn't supposed to look differently: :0: * ^List-Post: mailto:mutt-us...@mutt\.org$ mutt-users -- Rejo Zenger . r...@zenger.nl . 0x75FC50F3 . https://rejo.zenger.nl GPG encrypted e-mail prefered. signature.asc Description: Digital signature
Re: no list-id header for mutt-u...@mutt.org
++ 12/04/09 07:54 +0200 - Markus Mueller: So how do you filter out mutt mailing list emails? it's a bit reduntant, but alas, somebody asked a question i actually can answer! snipplet_of_muttrc [...] I presume the following is an excerpt from your procmailrc, not your muttrc. :) :0: * ^to.*mutt-us...@mutt\.org ml1/mutt-users/ I guess it's better to use the List-Post header as it is more constant than the To header. One other remark: the trailing slash at the mailbox name suggests that the mailbox is in the maildir format. If so, than the trailing colon on the first line is superflucious. It's needed for file locking, which you want when multiple processes could write to the same file at the same time. When using maildir, you will not see that problem and therefor you don't need the file locking. The first line would become :0 only. -- Rejo Zenger . r...@zenger.nl . 0x75FC50F3 . https://rejo.zenger.nl GPG encrypted e-mail prefered. signature.asc Description: Digital signature
Re: quoting urls in replies
++ 10/02/09 09:48 -0800 - Gary Johnson: message formatting (HTML?) to text. There may be an option in the program to inhibit that behavior, or you can find the program in your mailcap file and add | col -b after it. The generic mailcap file in /etc/ told mutt to use html2text to use for the conversion from html message parts to plain text only. One of the options for this application is -nobs: By default, html2text renders underlined letters with sequences like underscore-backspace- character and boldface letters like character-backspace-character, which works fine when the output is piped into more(1), less(1), or similar. For other applications, or when redi‐ recting the output into a file, it may be desirable not to render character attributes with such backspace sequences, which can be accomplished with this command line option. I now have overruled the generic text/html mailcap entry with a specific one in ~/.mailcap, using the same line as in the generic file, but with the addition of this particular option. This seems to do the trick. thank you all for all of your help. -- Rejo Zenger . r...@zenger.nl . 0x75FC50F3 . https://rejo.zenger.nl GPG encrypted e-mail prefered. signature.asc Description: Digital signature
Re: quoting urls in replies
++ 10/02/09 18:02 +0100 - Rocco Rutte: Please read the manual at http://www.mutt.org! Then, when I try to reply to that message, this line is quoted like: Please read the manual at h_^Ht_^Ht_^Hp_^H:_^H/_^H/_^Hw_^Hw_^Hw_^H._^Hm_^Hu_^Ht_^Ht_^H._^Ho_^Hr_^Hg_^H! Of course, this is not what I want. I don't really understand what does introduce this magic. Anyone does? The second form of the URL looks like it contains ansi-escape sequences to control text attributes like bold text. Mutt can properly render this kind of text so the URL looks normal. What you see in the editor is what it really looks like. If you got such URLs, there's nothing you can do about it. Just out of curiosity, who sends ansi-escaped URLs? Does this always happen (I hope not)? Aah! That makes sense. Recently I have made quite a few changes to the configuration of mutt. Amongst them, fixing character set issues, change from local spool mailboxes to mailboxes accessed over imap and change the prefered order of rendered attachment types. I now suspect that last change to be the originator of this particular issue. For more details, see the thread not all attachments shown in pager of some time ago [1]. What has changed, is that I now prefer html over plain text attachments as some mailers (like Apple's Mail.app) do not include the same information in the plain text version as they do in the html version. As for now, let me experiment with this. I will definately respond to this thread if the workaroudns mentioned in other postings do work for me. [1] http://thread.gmane.org/gmane.mail.mutt.user/31766 -- Rejo Zenger . r...@zenger.nl . 0x75FC50F3 . https://rejo.zenger.nl GPG encrypted e-mail prefered. signature.asc Description: Digital signature
Re: does mutt splitting large messages?
++ 11/02/09 13:18 +0300 - Andrey Zhidenkov: Can mutt split a large messages and send it with a several messages? I need to send a big file, but gmail doesn't allow it. No, it can't. If you need to send large, you better use a protocol that is designed for it. E-mail is in-efficient for sending large files. An example of a protocol that is designed for it, would be FTP. You may want to use an online service like yousendit.com - allthough I would qever use such a service myself. -- Rejo Zenger . r...@zenger.nl . 0x75FC50F3 . https://rejo.zenger.nl GPG encrypted e-mail prefered. signature.asc Description: Digital signature
Re: quoting urls in replies
++ 10/02/09 10:58 -0600 - Kyle Wheeler: Well, it depends on the original email, obviously. But keep in mind that mutt is juggling the rather herculean task of providing everybody with the character set it expects, to the best that mutt understands [...] I understand. Something else that can affect things is the fact that mutt is converting the email into *text* for replying to it. This doesn't sound like a big deal until you consider that you're converting from things like html. I use, I guess, lynx or elinks for rendering html message parts. I should tweak their configuration in order to have plain text fed into my editor, right? -- Rejo Zenger . r...@zenger.nl . 0x75FC50F3 . https://rejo.zenger.nl GPG encrypted e-mail prefered. signature.asc Description: Digital signature
quoting urls in replies
Hi there, Of course, mutt is doing fine. Just recently, I changed the locale to be used by mutt (I changed the charset setting) because the threads were incorrectly rendered in the message listing. Since that change, or just somewhere afterwards, replying to messages with URL's in the body has become somewhat cumbersome. The original message contains a line like: Please read the manual at http://www.mutt.org! Then, when I try to reply to that message, this line is quoted like: Please read the manual at h_^Ht_^Ht_^Hp_^H:_^H/_^H/_^Hw_^Hw_^Hw_^H._^Hm_^Hu_^Ht_^Ht_^H._^Ho_^Hr_^Hg_^H! Of course, this is not what I want. I don't really understand what does introduce this magic. Anyone does? Possibly relevant settings in my mutt configuration: set charset = utf-8 set escape = ~ set editor = 'vim -c set tw=72 fo+=aw smartindent +2' set indent_string = set use_8bitmime= no Anyone? Thanks in advance! -- Rejo Zenger . r...@zenger.nl . 0x75FC50F3 . https://rejo.zenger.nl GPG encrypted e-mail prefered. signature.asc Description: Digital signature
Re: quoting urls in replies
++ 10/02/09 08:55 -0600 - Kyle Wheeler: Possibly relevant settings in my mutt configuration: set charset = utf-8 Do not set this yourself (unless you really REALLY know what you're doing). I have removed this setting and I this doesn't change a thing in the way mutt shows the threads. So, this is no longer an issue (on itself). What does remain is the original problem: why is it that in replies the URI's are mangled? -- Rejo Zenger . r...@zenger.nl . 0x75FC50F3 . https://rejo.zenger.nl GPG encrypted e-mail prefered. signature.asc Description: Digital signature
Re: imap, maildir, folders with both subfolders and messages
++ 19/01/09 08:46 -0600 - Kyle Wheeler: end of the folder name than it is to overlook that plus symbol. Also, the character at the end of the folder name varies based on your IMAP server's settings and the value of $imap_delim_chars in your muttrc. The + mark is consistent. Just to make sure I have a correct understanding of your explanation and the documentation: the $imap_delim_chars variable just tells mutt what it should take as folder delimiter and it doesn't influence it's rendering in the folder browser. Right? -- Rejo Zenger . r...@zenger.nl . 0x75FC50F3 . https://rejo.zenger.nl GPG encrypted e-mail prefered. signature.asc Description: Digital signature
Re: Record
++ 26/12/08 09:30 +0200 - Tolga: I am connecting to a remote imap server. How can I set record to this server's Sent? I set record to imap://mtoz...@mail.sabanciuniv.edu/Sent then to =Sent but I got No route to host. The error, No route to host, sounds more like a network problem than a problem with mutt itself. Can you make sure mail.sabanciuniv.edu is the correct hostname and is reachable for you (outside of mutt, try doing a traceroute to the server and/or manually connect on the imap port)? -- Rejo Zenger . r...@zenger.nl . 0x75FC50F3 . https://rejo.zenger.nl GPG encrypted e-mail prefered. signature.asc Description: Digital signature
Re: not all attachments shown in pager
++ 25/12/08 12:10 -0600 - Kyle Wheeler: of the message. Now, one last question, is it possible to have mutt show all attachments in the pager, regardless of alternatives? No. Mutt follows the MIME decoding guidelines pretty strictly, and the message you've outlined above has *explicitly* marked the text/plain component as completely and fully equivalent to the subsequent multipart/mixed component. Mutt considers the message's structure to be essentially gospel for the purposes of rendering: if it's [...] Point taken. Clear explanation. Thanks a lot. -- Rejo Zenger . r...@zenger.nl . 0x75FC50F3 . https://rejo.zenger.nl GPG encrypted e-mail prefered. signature.asc Description: Digital signature
Re: not all attachments shown in pager
Hi there, I seem to be unable to find a solution myself (or to make sure it's not possible), so any help would be appreciated. Is there someone that can help me with the following? | Aah. That makes sense. In a more simplified rendering: | | 1 multipart mixed | 2 ├─ textplain | 3 └─ message rfc822 | 4 └─ multipart alternative | 5 ├─ textplain | 6 └─ multipart mixed | 7 ├─ texthtml | 8 ├─ multipart appledoubl | 9 │ ├─ application applefile | 10 │ └─ application msword | 11 └─ texthtml | | So, at level 4 the multipart/alternative is shown and mutt's pager | will show either level 5 or level 6, not both. As I have set | | alternative_order text/plain text/html | | it will prefer level 5 attachment to level 6 as level 5 is text/plain. | | That seems to work reliable. Setting multipart/alternative as the first | possibility to alternative_order makes it show the other part of the | message. Now, one last question, is it possible to have mutt show all | attachments in the pager, regardless of alternatives? | | I don't need all of them to be rendered, but to know other parts of the | message contain more content is usefull. Right now, by looking at the | text/plain alternative (5), I missed the inclusion of a Word docment | (10) in the other alternative (6). Thanks a lot in advance! -- Rejo Zenger . r...@zenger.nl . 0x75FC50F3 . https://rejo.zenger.nl GPG encrypted e-mail prefered. signature.asc Description: Digital signature
Re: not all attachments shown in pager
++ 18/12/08 10:20 +0800 - bill lam: On Wed, 17 Dec 2008, Rejo Zenger wrote: |I 1 no description [multipa/alternativ, 7bit, 178K] |I 2 AAno description [text/plain, 7bit, us-ascii, 1.8K] |I 3 AAno description[multipa/mixed, 7bit, 176K] |I 4 AAno description [text/html, quoted, us-ascii, 3.6K] |I 5 AAabcdefghijklmnopq.pdf [applica/pdf, base64, 170K] |I 6 AAno description [text/html, quoted, us-ascii, 2.1K] I don't know the exact answer, but I can see the email contained alternative meaning that only one of the alternatives is sufficient for viewing purpose. You may use alternative_order in muttrc to set your own preference. Please search for alternative_order in mutt documentation for detail. Aah. That makes sense. In a more simplified rendering: 1 multipart mixed 2 ├─ textplain 3 └─ message rfc822 4 └─ multipart alternative 5 ├─ textplain 6 └─ multipart mixed 7 ├─ texthtml 8 ├─ multipart appledoubl 9 │ ├─ application applefile 10 │ └─ application msword 11 └─ texthtml So, at level 4 the multipart/alternative is shown and mutt's pager will show either level 5 or level 6, not both. As I have set alternative_order text/plain text/html it will prefer level 5 attachment to level 6 as level 5 is text/plain. Right? -- Rejo Zenger . r...@zenger.nl . 0x75FC50F3 . https://rejo.zenger.nl GPG encrypted e-mail prefered. signature.asc Description: Digital signature
Re: not all attachments shown in pager
++ 18/12/08 10:11 +0100 - Rejo Zenger: Aah. That makes sense. In a more simplified rendering: 1multipart mixed 2 ├─textplain 3 └─message rfc822 4 └─ multipart alternative 5 ├─textplain 6 └─multipart mixed 7 ├─ texthtml 8 ├─ multipart appledoubl 9 │ ├─application applefile 10 │ └─application msword 11 └─ texthtml So, at level 4 the multipart/alternative is shown and mutt's pager will show either level 5 or level 6, not both. As I have set alternative_order text/plain text/html it will prefer level 5 attachment to level 6 as level 5 is text/plain. That seems to work reliable. Setting multipart/alternative as the first possibility to alternative_order makes it show the other part of the message. Now, one last question, is it possible to have mutt show all attachments in the pager, regardless of alternatives? I don't need all of them to be rendered, but to know other parts of the message contain more content is usefull. Right now, by looking at the text/plain alternative (5), I missed the inclusion of a Word docment (10) in the other alternative (6). Thanks for your help. -- Rejo Zenger . r...@zenger.nl . 0x75FC50F3 . https://rejo.zenger.nl GPG encrypted e-mail prefered. signature.asc Description: Digital signature
not all attachments shown in pager
Hi there, In the pager I see the following: | [-- PGP output follows (current time: Wed Dec 17 09:22:29 2008) --] | [...] | [-- End of PGP output --] | | [-- The following data is signed --] | | [-- Attachment #1 --] | [-- Type: text/plain, Encoding: quoted-printable, Size: 0.1K --] | [...] | | [-- Attachment #2 --] | [-- Type: message/rfc822, Encoding: 7bit, Size: 52K --] | | [-- End of signed data --] That's all. Then, when I press v to see all message parts, I get to this: |I 1 no description[multipa/mixed, 7bit, 52K] |I 2 AAno description [text/plain, quoted, us-ascii, 0.1K] |I 3 AAublad [message/rfc822, 7bit, 52K] |I 4 AAno description [multipa/alternativ, 7bit, 50K] |I 5 AAno description [text/plain, quoted, utf-8, 0.4K] |I 6 AAno description [multipa/mixed, 7bit, 49K] |I 7 AAno description[text/html, 7bit, us-ascii, 0.4K] |A 8 AAno description [multipa/appledoubl, 7bit, 47K] |A 9 3 AAabcdefghijklmno.doc [applica/applefile, base64, 0.1K] |A10 3 AAabcdefghijklmno.doc [applica/msword, base64, 47K] |I11 AAno description [text/html, quoted, us-ascii, 1.1K] |I12 no description [applica/pgp-signat, 7bit, 0.2K] The part that is missing in the pager, is the Word document. The User-Agent header was: User-Agent: Mutt/1.5.18 (2008-05-17) The question is, of course, why didn't list mutt the Word attachment in the pager view? I have had a similar problem a while ago. The pager showed the text/plain part only and didn't mention any other (relevant) attachments. When pressed v to show a list of message parts. I see: |I 1 no description [multipa/alternativ, 7bit, 178K] |I 2 AAno description [text/plain, 7bit, us-ascii, 1.8K] |I 3 AAno description[multipa/mixed, 7bit, 176K] |I 4 AAno description [text/html, quoted, us-ascii, 3.6K] |I 5 AAabcdefghijklmnopq.pdf [applica/pdf, base64, 170K] |I 6 AAno description [text/html, quoted, us-ascii, 2.1K] I would have expected mutt to tell me there was another attachment, the applica/pdf part, in the message. The sender was using: X-Mailer: Apple Mail (2.929.2) Now, the question is the same, why didn't I see the attachment in the pager? I am running mutt 1.5.17+20080114, from Debian Etch. -- Rejo Zenger . r...@zenger.nl . 0x75FC50F3 . https://rejo.zenger.nl GPG encrypted e-mail prefered. signature.asc Description: Digital signature
Re: synchronization of two maildirs
++ 28/10/08 14:53 -0700 - [EMAIL PROTECTED]: I am going to a different place for couple months where the network bandwidth is very poor. Ssh+mutt will not be very responsive. So I am looking at programs that would synchronize two maildirs. Looked at isync (mbsync) but that seems to need an IMAP (am I right?). Any other programs that can work for me. If not, I may end up writing my own! I am not sure whether it suits your situation, but you may want to have a look at imapsync, see http://www.linux-france.org/prj/imapsync/. -- Rejo Zenger . [EMAIL PROTECTED] . 0x75FC50F3 . https://rejo.zenger.nl GPG encrypted e-mail prefered. signature.asc Description: Digital signature
Re: tag pattern
++ 02/10/08 21:45 +0800 - bill lam: I often need to tag the same pattern. Instead of typing each time, how can I save the following and bind it shortcut key? tag pattern T\[.*patch.*\] return You would need to use a macro. Untested: macro pager,index \ca T\[.*patch.*\]enter # tag using pattern See: - http://www.mutt.org/doc/manual/manual-3.html#ss3.6 - http://wiki.mutt.org/?MuttGuide/Macros -- Rejo Zenger . [EMAIL PROTECTED] . 0x75FC50F3 . https://rejo.zenger.nl GPG encrypted e-mail prefered. signature.asc Description: Digital signature
Re: Wild Cards not working with mutt ?
++ 01/10/08 05:43 -0600 - Maruvada, Suryakiran: 1. I need to send multiples files as attachment to a single mail. mutt -a *.csv -s Testing [EMAIL PROTECTED] /dev/null Error sending message, child exited 100 (). Segmentation fault From man page I understand that, -a file [...] Attach a file to your message using MIME. To attach multiple files, separating filenames and recipient addresses with -- is mandatory, e.g. mutt -a img.jpg *.png -- addr1 addr2 [...] You are missing one essential note in the man page: [...] To attach multiple files, separating filenames and recipient addresses with -- is mandatory [...] So, if you change your command line to something like this it should work: mutt -s testing -a *.csv -- [EMAIL PROTECTED] /dev/null 2. Do we have any restriction on the length of the file name to be sent.? As I have very long file names. I don't know about that. -- Rejo Zenger . [EMAIL PROTECTED] . 0x75FC50F3 . https://rejo.zenger.nl GPG encrypted e-mail prefered. signature.asc Description: Digital signature
urls longer than terminal width in iterm
Hi, I have this minor but annoying issue. I seem to be unable to fix it... Currently, I am using mutt with a fairly basic configuration on a server running Debian to which I am connected using iTerm under OSX 10.5. When someone sends me an URL in an e-mail, I can click (using command key and left mouse button) it and it'll open the link in my browser. So far so good. The annoyance is with overly long addresses, that are wider than my terminal. These addresses are wrapped to the next line(s) and it's continuation lines are marked with the + sign. Now, when I click these addresses the newline and plus sign are replaced by + , resulting in an invalid URL. Is there a way to circumvent this? -- Rejo Zenger . [EMAIL PROTECTED] . 0x75FC50F3 . https://rejo.zenger.nl GPG encrypted e-mail prefered. signature.asc Description: Digital signature
Re: Mutt problem, probably with procmail
++ 13/09/08 09:20 -0400 - Patrick Shanahan: Well, your procmail recipe will not work as the matches begin at the start of the recipe, ie: ^TO and your recipe will not match a normal To: Header. and will not deliver to Maildir type mailboxes, needs trailing /. :0: * ^TO_.*lugola-info-center $MAILDIR/lugola/ If this would be the recipe you settle with, you should remove the second colon on the first line. The second colon tells procmail to lock the mailbox it wants to write to. This is required for mbox mailboxes, but for maildir mailboxes it is useless (as you never have two processes writing to the same file). -- Rejo Zenger . [EMAIL PROTECTED] . 0x75FC50F3 . https://rejo.zenger.nl GPG encrypted e-mail prefered. signature.asc Description: Digital signature
Re: send-hook not working
++ 13/04/08 22:36 +0200 - Kirill Miazine: With the first one, it doesn't work. Without the first line, it does. Yes, that does make sense and actually behaves the way I would expect. To me it seems that your send-hooks will be flushed immediately after you enter a folder. What is the first line supposed to do? Yes, of course. I am not sure why I had that particular line there. I didn't realise this was the problem, but of course, your explanation makes a lot of sense. I am still *first* setting the default and have that default overruled by more specific situations. Yes. First . is matched, and then ~C. Yup. -- Rejo Zenger . [EMAIL PROTECTED] . 0x75FC50F3 . https://rejo.zenger.nl signature.asc Description: Digital signature
Re: send-hook not working
++ 12/04/08 23:19 +0200 - Sander Smeenk: That's weird. I nailed down the problem. As one of the first hooks I have: folder-hook . unhook send-hook If this one is removed, it works. I am wondering why I put that line there in the first place. So, now running without this line and see what else is broken. :) Thanks a lot for the help. -- Rejo Zenger . [EMAIL PROTECTED] . 0x75FC50F3 . https://rejo.zenger.nl signature.asc Description: Digital signature
send-hook not working
Hi, I have the following hook: send-hook . unset pgp_autoencrypt send-hook '~t [EMAIL PROTECTED]' set pgp_autoencrypt=yes This is in a separate file, and is included from .muttrc as the last line in a row of files with all kinds of hooks (mostly folder-hooks's, but not send-hook's). Everything works the way I want it, but just this doesn't. I have, of course, checked the docs, the wiki and the FAQ's. Still I can't figure out why this hook doesn't work. So, what is the most likely thing I am overlooking? -- Rejo Zenger . [EMAIL PROTECTED] . 0x75FC50F3 . https://rejo.zenger.nl signature.asc Description: Digital signature
Re: send-hook not working
Hey Sander. Small world, isn't it? ++ 12/04/08 19:53 +0200 - Sander Smeenk: I have the following hook: send-hook . unset pgp_autoencrypt send-hook '~t [EMAIL PROTECTED]' set pgp_autoencrypt=yes Still I can't figure out why this hook doesn't work. So, what is the most likely thing I am overlooking? This only seems to work with edit_hdrs turned off. I do not have enabled this option. According to the manual it's no by default and I do not get to see the headers when editting a message. So, I presume, the problem is somewhere else. -- Rejo Zenger . [EMAIL PROTECTED] . 0x75FC50F3 . https://rejo.zenger.nl signature.asc Description: Digital signature
Re: OT: column 72 in mutt with xterm vim
++ 12/03/08 10:12 +0100 - Matthias Apitz: Well, is there some way to draw a magic vertical line in the xterm or 'vim' in column 72? I am using in my .muttrc: set editor = 'vim -c set tw=72 +2' This tells vim the textwidth is maximum at 72 characters. When typing text normaly, it will wrap text at that boundary. Whenever I am editing text (adding a few words), this will no longer work automagicaly. I can then use gqap to reformat the paragraph and it't will rewrap again to that boundary. Works nicely - although it could be optimized probably. -- Rejo Zenger . [EMAIL PROTECTED] . 0x75FC50F3 . https://rejo.zenger.nl signature.asc Description: Digital signature
macro to unset flags and save to folder
Hi there, I have this small annoyance and I seem to be unable to figure out how to solve it. At this moment I have this in my .muttrc: macro index,pager \Ca s^.2008\n This works perfect. But to make it even more perfectly, I want to have it to clear any new or old message flags. I am aware this should be possible with the clear-flag commands. However, when doing something like the following, it doesn't do the things I want: macro index \Ca enter-commandset resolve=noenter\ clear-flagN\ clear-flagO\ save-message^.2008enter\ enter-commandset resolve=yesenter In one way or another it will clear flags on messages and archive the messages which I do not intend to clear the flags and to archive. I presume this is influenced by the resolve variable, but even when disabling that variable it doesn't do what I want. Does anyone have any idea? -- Rejo Zenger [EMAIL PROTECTED] https://rejo.zenger.nl signature.asc Description: Digital signature
Re: macro to unset flags and save to folder
++ 21/02/08 13:39 +0100 - Peter Münster: In one way or another it will clear flags on messages and archive the messages which I do not intend to clear the flags and to archive. I presume this is influenced by the resolve variable, but even when disabling that variable it doesn't do what I want. Does anyone have any idea? It seems, that the reason for your problem is the white-space at the beginning of the continued lines. This works for me: That did the trick. I now have... macro index \Ca enter-commandset resolve=noenterclear-flagNclear-flagOsave-message^.2008enternext-entryenter-commandset resolve=yesenter ... and it seems to work like a charm. Cool. Thanks a lot for the input. -- Rejo Zenger [EMAIL PROTECTED] https://rejo.zenger.nl signature.asc Description: Digital signature
Mail-Followup-To header, where defined?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Does anyone of you know which documents describes / defines this Mail-Followup-To header? Thanks in advance, -R. - -- # [EMAIL PROTECTED] (pgp: see headers) - http://www.sisterray.nl -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE64TocHa9Q5nX8UPMRAm3sAKCFdWh1Akbh50i4biyJdkJ6FaMgJgCgidPA pPgWwUmygN1HbACltLSNYjw= =zRXu -END PGP SIGNATURE-
Re: removing duplicate messages + changing mailbox
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 ++ 12/02/01 08:04 + - Nelson D. Guerrero: Roel, the answer to that question is making a rule on your .procmailrc to delete themThis is what I have. :0 Whc: .msgid.lock | formail -D 16384 .msgid.cache :0 a: /dev/null The ":" on the second recipe can be removed. There's no need for locking when writing a message to /dev/null. -R. - -- # [EMAIL PROTECTED] (pgp: see headers) - http://www.sisterray.nl -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE60VclHa9Q5nX8UPMRAktbAKDMA5cLC+lWqeEa073cU80fUmNQxgCgxrlC uwQrdt9fxLJHtSpBNEwgkFE= =IKlM -END PGP SIGNATURE-
Problem with PGP linebreaks
Hi,
I'm using Mutt 1.2.5i and GPG 1.0.4 on a Linux 2.2.16.
I have been told the encrypted email I'm sending does not have the
correct linebreaks.
This is a hexdump of a part of a message I have sent to him. Linebreaks
are platform-specific ("0A"; Unix style) instead of the platform-
independent ("0D0A", Internet-style).
[...]
0030: 2C 20 61 61 6E 67 65 28 70 7C 74 29 61 73 74 2E , aange(p|t)ast.
0040: 20 41 6C 73 20 68 65 74 0A 67 6F 65 64 20 69 73Als hetgoed is
0050: 20 7A 6F 75 64 65 6E 20 6D 69 6A 6E 20 65 6D 61zouden mijn ema
0060: 69 6C 73 20 6E 75 20 61 6C 6C 65 65 6E 20 6E 6F ils nu alleen no
0070: 67 20 6D 61 61 72 20 6F 6C 64 2D 73 74 79 6C 65 g maar old-style
0080: 20 73 69 67 6E 65 64 20 65 6E 0A 65 6E 63 72 79signed enencry
0090: 70 74 65 64 20 6D 6F 65 74 65 6E 20 7A 69 6A 6E pted moeten zijn
00A0: 2E 0A 0A 5A 6F 75 64 65 6E 20 6A 75 6C 6C 69 65 .Zouden jullie
[...]
This is what i have been told.
As I'm lacking knowledge at this point:
- Is this an issue at all?
- If it is, is it one caused by Mutt, GPG or something else?
- If it is, what is the best thing i can do solve this?
Relevant detail maybe, the command mutt uses when I sign and encrypt
email is (all on one line):
set pgp_encrypt_sign_command="pgpewrap gpg --passphrase-fd 0 -v --batch
--output - --encrypt --sign %?a?-u %a? --armor --always-trust -- -r %r
-- %f"
So, what is the next thing I can do best?
-R.
--
# [EMAIL PROTECTED] (pgp: see headers) - http://www.sisterray.nl
Re: header problems?
++ 13/01/01 07:03 -0600 - ktb: send to. I receive but can't send. Also some of my personal friends have reported that they send to me and the mail is bounced back to them. I'm using exim (debian) My isp is Most likely those problems are not related to mutt. I guess you have some mistakes in the configuration of Exim or in your DNS. What would help is to know if (and if so, which) error messages you get when you try to send your message to that list. If there are no error messages, do you get a bounce? If so, what does it say? The same goes for the second problem (mail to you is bounced), it is most likely not a problem with mutt. What does the bounce say? hopes that it would clear up my problem. I notice "Received:" is set to my localhost "debian.local" is that a problem? I'm struggling to understand these headers. I notice if I send from [...] Received: from kent by debian.local with local (Exim 3.12 #1 (Debian)) id 14HPP3-00018i-00 for [EMAIL PROTECTED]; Sat, 13 Jan 2001 06:03:25 -0600 from femail6.sdc1.sfba.home.com (24.0.95.86) by smtp.c002.snv.cp.net (209.228.32.161) with SMTP; 13 Jan 2001 04:03:44 -0800 from debian.local ([my.ip.address]) by femail6.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id [EMAIL PROTECTED] for [EMAIL PROTECTED]; Sat, 13 Jan 2001 04:03:44 -0800 from kent by debian.local with local (Exim 3.12 #1 (Debian)) id 14HPP3-00018i-00 for [EMAIL PROTECTED]; Sat, 13 Jan 2001 06:03:25 -0600 These are, i guess, *four* Received lines, but only the first one is starting with that field name. Try to post the full lines, without munging. -R. -- # [EMAIL PROTECTED] (pgp: see headers) - http://www.sisterray.nl PGP signature
Re: what hook to use when setting headers depending on current folder?
++ 26/06/00 21:05 +0200 - Virginie [ ML ]: When using a send-hook i don't know how to tell Mutt it should use the settings depending on the folder i'm in. When using a folder-hook it seems that the settings get overwritten by send-hooks when actually writing the message. I had the same problems (conflicts between send-hook and folder-hook) and it worked with something like that : [...] folder-hook =IN.mutt-users my_hdr From: Virginie [ML][EMAIL PROTECTED]; X-URL: http://members.gopenguin.com/virginie This doesn't work for me. It seems to me that folder-hooks are overwritten by the send-hooks. I have a number of send-hooks followed by a few folder-hooks. The folder-hooks do not work as expected. The send-hooks do. Any idea how to solve this? -Rejo. -- = Rejo Zenger [EMAIL PROTECTED] = http://mediaport.org/~sister (and my_urls.html) PGP: see headers PGP signature
PGP oldstyle signatures [2]
... and i forgot to attach the parts of my muttrc where things get loaded for GPG and PGP. -Rejo. -- = Rejo Zenger [EMAIL PROTECTED] = http://mediaport.org/~sister (and my_urls.html) PGP: see headers # decode application/pgp set pgp_decode_command="gpg %?p?--passphrase-fd 0? --no-verbose --batch -o - %f" # verify a pgp/mime signature set pgp_verify_command="gpg --no-verbose --batch -o - --verify %s %f" # decrypt a pgp/mime attachment set pgp_decrypt_command="gpg --passphrase-fd 0 --no-verbose --batch -o - %f" # create a pgp/mime signed attachment # set pgp_sign_command="gpg-2comp --no-verbose --batch -o - --passphrase-fd 0 --armor --detach-sign --textmode %?a?-u %a? %f" set pgp_sign_command="gpg --no-verbose --batch -o - --passphrase-fd 0 --armor --detach-sign --textmode %?a?-u %a? %f" # create a application/pgp signed (old-style) message # set pgp_clearsign_command="gpg-2comp --no-verbose --batch -o - --passphrase-fd 0 --armor --textmode --clearsign %?a?-u %a? %f" set pgp_clearsign_command="gpg --no-verbose --batch -o - --passphrase-fd 0 --armor --textmode --clearsign %?a?-u %a? %f" # create a pgp/mime encrypted attachment # set pgp_encrypt_only_command="pgpewrap gpg-2comp -v --batch -o - --encrypt --textmode --armor --always-trust -- -r %r -- %f" set pgp_encrypt_only_command="pgpewrap gpg -v --batch -o - --encrypt --textmode --armor --always-trust -- -r %r -- %f" # create a pgp/mime encrypted and signed attachment # set pgp_encrypt_sign_command="pgpewrap gpg-2comp --passphrase-fd 0 -v --batch -o - --encrypt --sign %?a?-u %a? --armor --always-trust -- -r %r -- %f" set pgp_encrypt_sign_command="pgpewrap gpg --passphrase-fd 0 -v --batch -o - --encrypt --sign %?a?-u %a? --armor --always-trust -- -r %r -- %f" # import a key into the public key ring set pgp_import_command="gpg --no-verbose --import -v %f" # export a key from the public key ring set pgp_export_command="gpg --no-verbose --export --armor %r" # verify a key set pgp_verify_key_command="gpg --no-verbose --batch --fingerprint --check-sigs %r" # read in the public key ring set pgp_list_pubring_command="gpg --no-verbose --batch --with-colons --list-keys %r" # read in the secret key ring set pgp_list_secring_command="gpg --no-verbose --batch --with-colons --list-secret-keys %r" # receive key from keyserver: #set pgp_getkeys_command="wrap.sh -g %r" set pgp_getkeys_command="" # Do not sign and/ or encrypt messages by default. unset pgp_autoencrypt unset pgp_autosign # Use this key by default. set pgp_sign_as=0x75FC50F3 # Set the algorithm to use. set pgp_sign_micalg=pgp-sha1 # Forget passphrase after n seconds. set pgp_timeout=1800 # Always verify signatures. set pgp_verify_sig=yes # Do not create old style signatures, if needed it'll be overruled by hand or by send-hook. set pgp_create_traditional=no # Make sure that if i reply to a message that is signed or encrypted i both # sign and encrypt that message. set pgp_replyencrypt set pgp_replysign set pgp_replysignencrypted # decode application/pgp set pgp_decode_command="%?p?PGPPASSFD=0; export PGPPASSFD;? cat %?p?-? %f | pgp +verbose=0 +batchmode -f" # verify a pgp/mime signature set pgp_verify_command="pgp +verbose=0 +batchmode -t %s %f" # decrypt a pgp/mime attachment set pgp_decrypt_command="PGPPASSFD=0; export PGPPASSFD; cat - %f | pgp +verbose=0 +batchmode -f" # create a pgp/mime signed attachment set pgp_sign_command="PGPPASSFD=0; export PGPPASSFD; cat - %f | pgp +verbose=0 +batchmode -abfst %?a? -u %a?" # create a pgp/mime encrypted attachment set pgp_encrypt_only_command="pgp +verbose=0 +encrypttoself +batchmode -aeft %r %f" # create a pgp/mime encrypted and signed attachment set pgp_encrypt_sign_command="PGPPASSFD=0; export PGPPASSFD; cat - %f | pgp +encrypttoself +verbose=0 +batchmode -aefts %?a?-u %a? %r" # import a key into the public key ring set pgp_import_command="pgp -ka %f" # export a key from the public key ring set pgp_export_command="pgp -kxaf %r" # verify a key set pgp_verify_key_command="pgp -kcc %r" # read in the public key ring set pgp_list_pubring_command="pgpring -2 %r" # read in the secret key ring set pgp_list_secring_command="pgpring -s -2 %r" # Do not sign and/ or encrypt messages by default. unset pgp_autoencrypt unset pgp_autosign # Use this key by default. set pgp_sign_as=0xFAE40065 # Set the algorithm to use. set pgp_sign_micalg=pgp-md5 # Forget passphrase after n seconds. set pgp_timeout=1800 # Always verify signatures. set pgp_verify_sig=yes # Do create old style signatures. set pgp_create_traditional=yes # Make sure that if i reply to a message that is signed or encrypted i both # sign and encrypt that message. set pgp_replyencrypt set pgp_replysign set pgp_replysignencrypted PGP signature
send-hook changing from address?
Hi, I have two questions, maybe someone can help me. [1] I have set this alternates stuff and my From address is now the same as the address to which the message was sent i'm replying to, unless overruled by a send-hook. This works ok, except for one point. In some cases, if the addresses matches a regular expression, i would like to have it changed: The From address (that is used because of the alternates setting) should change if it matches a specific regexp regardless to whom the message is addressed. So, i tried this (wrapped): send-hook '~f 2[0-9]*[rfma]?(\.trap)?(NOSPAM)?(+rejo)?@sisterray.xs4all.nl' 'my_hdr From: Rejo Zenger [EMAIL PROTECTED]' to change From: Rejo Zenger [EMAIL PROTECTED] to From: Rejo Zenger [EMAIL PROTECTED] This does not work. Any idea why? [2] Another things. Is it possible to have a unique From address if Subject matches a pattern? I don't really care what it makes unique, but i was thinking of a something like _ctime or a number which is updates with one each time. Is this possible? Thanks in advance... -Rejo. -- = Rejo Zenger [EMAIL PROTECTED] = http://mediaport.org/~sister (and my_urls.html) PGP: see headers PGP signature
Re: [1.0.1i] slow opening of mailboxes
++ 28/03/00 15:35 +0200 - Thomas Roessler: [slow opening of mailboxes] Do you use NFS? Nope. I'm running on a standard P3 with Linux as OS. Just the regular stuff... -Rejo. -- = Rejo Zenger [EMAIL PROTECTED] = http://mediaport.org/~sister (and my_urls.html) PGP: see headers PGP signature
[1.0.1i] slow opening of mailboxes
Hi, This have been on the list before recently but has i have had some config problems with my mailserver (causing mail to be bounced) i may have missed a few relevant postings. When re-confuguring my machine this weekend i have upgraded mutt from version 1.0i to 1.0.1i. I have noticed opening of mailboxes of 5 Mb in size have slowed down noticeably. If i'm not able to solve this, i will move back to the older version. Mutt runs on a P3/500/128 running SuSE 6.2 [2.2.10] as OS. The output of mutt -v is: $ mutt -v Mutt 1.0.1i (2000-01-18) System: Linux 2.2.10 [using ncurses 4.2] Compile options: -DOMAIN -HOMESPOOL -USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK -USE_IMAP -USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP2 +HAVE_GPG -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/spool/mail" SHAREDIR="/usr/local/share/mutt" SYSCONFDIR="/usr/local/etc" -ISPELL _PGPPATH="/usr/bin/pgp" _PGPV2PATH="/usr/bin/pgp" _PGPGPGPATH="/usr/bin/gpg" Any idea what the problem is? -Rejo. -- = Rejo Zenger [EMAIL PROTECTED] = http://mediaport.org/~sister (and my_urls.html) PGP: see headers PGP signature
one mailboxes, no new mail found
Hi, I have several folders, but in two of them no new mail is noticed (when browsing thru folders with new mail or looking for folders marked with N in the folderlist). One of them is /home/rejo/mail/spam-usenet, although i seem to have set up everything correct: $ la mail/spam* -rw--- 1 rejo users 2583240 Mar 13 20:34 mail/spam -rw--- 1 rejo users 1659461 Mar 14 20:34 mail/spam-usenet $ grep folder= .muttrc set folder=$HOME/mail $ grep =spam-usenet .muttrc mailboxes =spam-usenet Any idea? -Rejo. -- = Rejo Zenger [Sister Ray Crisiscentrum] [EMAIL PROTECTED] = http://mediaport.org/~sister (and my_urls.html) PGP: see headers Destroy a spamhaus! http://www.xs4all.nl/~sister/mirror/sengir/spam_sites.html
Re: Extra space in Subject
++ 05/03/00 16:13 +0100 - Roland Rosenfeld:
Looks like you have a bad reply_regexp setting. If this only matches
"Re:", it will only remove "Re:" and not "Re: " and after removing
"Re:" and adding "Re: " after this, you will note the mentioned
effect. The default reply_regexp ("^(re|aw):[ \t]*") should not show
this behavior.
Mmm... let me see:
$ grep reply_regexp .muttrc
set reply_regexp="^(re|aw):[\t]*"
Looks like i'm using the default, but with a space left out. I will add
the space and see what will happen.
Thanks for your help,
-Rejo.
--
= Rejo Zenger [Sister Ray Crisiscentrum] [EMAIL PROTECTED]
= http://mediaport.org/~sister (and my_urls.html) PGP: see headers
Destroy a spamhaus! http://www.xs4all.nl/~sister/mirror/sengir/spam_sites.html
Re: macros - is there any logic about when they work or not?
++ 30/11/99 09:13 + - Chris Green: 2 - The manual is wrong about using ^ to indicate control characters. I guess it depends from system to system (and possibly the way of quoting). Could people on different systems try this? -Rejo. -- = Rejo Zenger [Sister Ray Crisiscentrum] [EMAIL PROTECTED] = http://mediaport.org/~sister PGP: see headers
Re: my_hdr question.
++ 27/11/99 09:58 +0200 - Mikko Hänninen: Rejo Zenger [EMAIL PROTECTED] wrote on Fri, 26 Nov 1999: send-hook [EMAIL PROTECTED] 'my_hdr From: Rejo Zenger [EMAIL PROTECTED]' send-hook [EMAIL PROTECTED] 'my_hdr Reply-To: Rejo Zenger [EMAIL PROTECTED]' send-hook [EMAIL PROTECTED] 'my_hdr Cc: Foo Bar [EMAIL PROTECTED]' I think the issue here is that you can't add a recipient from a send-hook, because the hooks are already matching against the To/Cc/Bcc headers. Yes, that could be an explanation. The reason i need this is because i'm the co-moderator for some lists. Everytime i accept or reject a RFS i have to write to listserv, but also Cc the other co-mods. Normally i did this by hand (with a macro), but as i'm using mutt i was thinking i could do this automagically... -Rejo. -- = Rejo Zenger [Sister Ray Crisiscentrum] [EMAIL PROTECTED] = http://mediaport.org/~sister PGP: see headers
Re: error
++ 25/11/99 00:57 +0100 - Marco Giardini:
Error detected while processing BufReadPost Auto commands for
"mutt[^.]*":
This ('BufReadPost Auto commands') is from Vim's syntax files which are
used for things like colorization. I suggest you check your suntax
files. Usually located in /usr/share/vim/syntax/.
-Rejo.
--
= Rejo Zenger [Sister Ray Crisiscentrum] [EMAIL PROTECTED]
= http://mediaport.org/~sister PGP: see headers
Re: How to deal with duplicate messages
Hi, i wrote: ++ 13/11/99 21:01 +0100 - Rejo Zenger: :0 Wh: msgid.lock -^ | formail -D 8192 msgid.cache There shouldn't be a space there. You'd better change this to :0 Wh :msgid.lock :0 Wh:msgid.lock [...] This is incorrect. Procmail will ignore all the space and it's correct syntax as well. I was mistaken here. Sorry. -Rejo. -- = Rejo Zenger [Sister Ray Crisiscentrum] [EMAIL PROTECTED] = http://mediaport.org/~sister PGP: see headers
Re: Colors
++ 13/11/99 11:37 -0500 - Subba Rao: Each time I start mutt, I get the following errors. Error in /home/subb3/.muttrc, line 65: default: no such color Change default to black (or whatever your background is or should be) and i guess your problem is gone. -Rejo. -- = Rejo Zenger [Sister Ray Crisiscentrum] [EMAIL PROTECTED] = http://mediaport.org/~sister PGP: see headers
Re: Alternates, Groups, Lists, and Work
++ 11/11/99 22:11 + - Sean Rima: My mail filter detects spam, but instead of deleting it, it inserts the header 'X-Status: D'. Thus, when I enter my mailbox, all the spam is Any chance of seeing your filter, sounds good. I have same kind of setup. I have procmail check for a some things that may point to spam. Other, similar, checks are also done. The filter checks for spammers that use insecure systems or messages without RFC822 and RFC1123 valid Message-Id or Date fields. It checks to see if the mail was addressed to a spamtrap. It checks to see if the used mail servers are in the ORBS, RSS or RBL. If it finds a thing that does not look correct, it'll add a X-Note field with the problem found. In Mutt i have these X-Note headers light up in bright white (while other header fields are in green), so i can eassily not if something is, possibly, wrong. Some of them are derived from the Spamdunk filters, but have been changed and extended over the course of time. See my procmailrc at http://www.mediaport.org/~sister/personal/procmailrc for more info. -Rejo. -- = Rejo Zenger [Sister Ray Crisiscentrum] [EMAIL PROTECTED] = http://mediaport.org/~sister PGP: see headers
Re: pronounce
++ 08/11/99 18:23 -0600 - Jeremy Blosser:
A "mutt" is a dog that is such a mix of breeds, there is no real pedigree
for it anymore. ME called his mailer mutt because it took lots of features
from lots of other mailers.
So, a dutch translations of mutt would be titled "bastaard". :-)
-Rejo.
--
= Rejo Zenger [Sister Ray Crisiscentrum] [EMAIL PROTECTED]
= http://mediaport.org/~sister PGP: see headers
Re: pronounce
++ 08/11/99 07:27 -0500 - Fairlight: how to pronounce "mutt"? Mutt is pronounced as "mutt". Can it be more simple? *snicker* But perhaps his first language isn't english? It could read as "moot"... For the record, it's "m - short u - t". An additional question... what does it mean or where does it comes from? -Rejo. -- = Rejo Zenger [Sister Ray Crisiscentrum] [EMAIL PROTECTED] = http://mediaport.org/~sister PGP: see headers
Re: auto_view application/pgp-signature
++ 02/11/99 13:13 -0500 - Russell Hoover: I have this in my .mailcap: application/pgp; cat; copiousoutput application/pgp-keys; pgp -f %s ; copiousoutput application/pgp-signature; cat; copiousoutput and this in my .muttrc: auto_view applicatiion/pgp and I see the signature attachments with no problems. I can see signature attachments with no problems as well, but what i would like to have is to see them without going to the attachment window to select them. So, this is what i have in my mailcap now: rejo:~$ grep pgp .mutt/mailcap application/pgp; cat; copiousoutput application/pgp-keys; pgp -f %s ; copiousoutput application/pgp-signature; cat; copiousoutput And in my .muttrc i have: auto_view application/pgp The only way to see the signature is to with 'v' and '2' (keystrokes). How can i have it shown in the pager immediatelly? Thanks for the help, -Rejo. -- = Rejo Zenger [Sister Ray Crisiscentrum] [EMAIL PROTECTED] = http://mediaport.org/~sister PGP: see headers
Re: read only /var/spool/mail/(user)
++ 27/10/99 15:08 +0100 - [EMAIL PROTECTED]: drwxrwsr-x 2 root mail 1024 Oct 23 12:16 mail -rw-rw 1 paul mail 422603 Oct 23 12:16 /var/spool/mail/paul -^^-- Eeeuh... i'm not sure, but those persissions don't look that good at all. Now any user in the group mail could read and write to this mailbox and i guess only user paul is supposed do so. My permissions: rejo:~$ la /var/spool/mail/rejo -rw--- 1 rejo users 0 Oct 29 19:31 /var/spool/mail/rejo Hope this helps, -Rejo. -- = Rejo Zenger [Sister Ray Crisiscentrum] [EMAIL PROTECTED] = http://mediaport.org/~sister PGP: see headers
Regexps for catching [-- PGP output...
Hi, I just cannot figure out how to color the lines that surrounds PGP and GPG messages like, -- PGP output follows and [-- End of PGP output... There are two problems. First of all, they don't seem to be part of the object called body. Which i should use instead is not clear to me (and yes, i did RTFM). Second, how to catch a literal '[' and ']'. Any idea's? -Rejo. -- = Rejo Zenger [Sister Ray Crisiscentrum] [EMAIL PROTECTED] = http://mediaport.org/~sister PGP: see headers
What does gpg 'no secret key for decryption available' say?
Hi,
When receiving a message that is both signed and encrypted i get the
message "gpg: no secret key for decryption available". Message can be
decrypted and the signature can be checked without a problem, both are
ok. Any idea's?
-Rejo.
--
= Rejo Zenger [Sister Ray Crisiscentrum] [EMAIL PROTECTED]
= http://mediaport.org/~sister PGP: see headers
Re: my_hdr From vs set use_from
++ 08/10/99 11:37 +0200 - Thomas Roessler: First of all -- in which version is this? I've been using 1.0pre2, but that lacked the variable, so I got and compiled pre3. But that didn't appear to have a $from variable either. So is this only in the developement version or something? A patch? The $from variable is present only in the unstable branch. With 1.0i, is it still not included? I couldn't find it in the manual, which means it is not included? It would be a pity as it seems to do what i need. -Rejo. -- = Rejo Zenger [Sister Ray Crisiscentrum] [EMAIL PROTECTED] = http://mediaport.org/~sister PGP: see headers
auto_view application/pgp-signature
Hi, Another thing i have tried myself for a long time but which i don't seem to be able to fix is that i want to have PGP signatures displayed on the screen as well. Plain text is shown, and, with the correct settings, HTML and vcard encoded stuff will also do. Now i just want application/pgp-signature to be shown as well, but i can't get it to work. From my .muttrc: auto_view application/pgp-signature And in my mailcap file: application/pgp-signature; cat %s; copiousoutput The mailcap file is in $HOME/.mutt/mailcap and is sourced from .muttrc: set mailcap_path=$HOME/.mutt/mailcap Any idea's how to do this? -Rejo. -- = Rejo Zenger [Sister Ray Crisiscentrum] [EMAIL PROTECTED] = http://mediaport.org/~sister PGP: see headers
Re: configurable?
Hi.
Sorry for the late reply, but i guess that one answer wasn't given to
this question of Mark.
++ 25/08/99 11:48 -0400 - Fairlight:
Seriously...there's one thing that I -can't- seem to find to reconfigure,
ant that's the "-- Forwarded message by" ...or however it reads, when you
forward a message.
As other pointed out already, there's no option to re-define this. I
don't like the fact that the orginal From address is included in that
line as well, so i change it myself also. Therefor i change the file
send.c in the source (somewhere around line 330) to this:
fputs ("--[begin forwarded message]--\n", out);
if (option (OPTFORWDECODE))
{
cmflags |= M_CM_DECODE | M_CM_CHARCONV;
if (option (OPTFORWWEEDHEADER))
{
chflags |= CH_WEED;
cmflags |= M_CM_WEED;
}
}
if (option (OPTFORWQUOTE))
cmflags |= M_CM_PREFIX;
mutt_parse_mime_message (ctx, cur);
mutt_copy_message (out, ctx, cur, cmflags, chflags);
fputs ("--[end forwarded message]--\n", out);
return 0;
}
This is probably not the most perfect way to change things (i don't have
an experience with changing the source (hi Winfried), but i tried this
on good luck and it seems to work for me)...
-Rejo.
--
= Rejo Zenger [Sister Ray Crisiscentrum] [EMAIL PROTECTED]
= http://mediaport.org/~sister PGP: see headers
seg-faults with 1.0pre3i
ing for limits.h... yes checking for locale.h... yes checking for nl_types.h... yes checking for malloc.h... yes checking for string.h... yes checking for unistd.h... (cached) yes checking for sys/param.h... yes checking for getcwd... yes checking for munmap... yes checking for putenv... yes checking for setenv... yes checking for setlocale... yes checking for strchr... yes checking for strcasecmp... (cached) yes checking for strdup... (cached) yes checking for __argz_count... yes checking for __argz_stringify... yes checking for __argz_next... yes checking for stpcpy... yes checking for LC_MESSAGES... yes checking whether NLS is requested... yes checking whether included gettext is requested... no checking for libintl.h... yes checking for gettext in libc... yes checking for msgfmt... no checking whether catgets can be used... no checking for msgfmt... (cached) no checking for gmsgfmt... no checking for xgettext... : checking for catalogs to be installed... de ru it es uk fr pl nl cs id sk ko el zh_TW.Big5 updating cache ./config.cache creating ./config.status creating Makefile creating intl/Makefile creating m4/Makefile creating po/Makefile.in creating Muttrc creating doc/Makefile creating doc/manual.sgml creating doc/dotlock.man creating doc/mutt.man creating charsets/Makefile creating contrib/Makefile creating config.h linking ./intl/libgettext.h to intl/libintl.h Doesn't look too bad i think. And i don't see errors while making either. If you need more info, feel free to email me. Additional info could possibly provided by Heinz Diehl hd at elfie.rhein-neckar.de, who has tried to help already a lot. Thanks a lot in advance. I need a running Mutt. -Rejo. -- = Rejo Zenger [Sister Ray Crisiscentrum] [EMAIL PROTECTED] = http://mediaport.org/~sisterPGP: RSA FAE40065, DSS/DH 2C8059B5
Re: segmentation fault
++ 05/10/99 12:45 -0400 - Daniel Eisenbud: It would help if you could both give us the output of "mutt -v" and a stack trace from the core file that the crashed mutt produces. So, all the info in one email: I have recently updated my system with a SuSE-6.1 system (all packages but two are updated, python and bzip are newer versions) running Linux kernel 2.2.7. The gcc version is egcs-2.91.66 19990314 (egcs-1.1.2 release). Version of binutils is 2.9.1.0.22b, slang is 1.2.2-49. All except for mutt are from this SuSE 6.1 disc. I have re-installed all of them this afternoon in order to avoid any problems. Version of Mutt and compile options: root:/usr/src/mutt-1.0pre3# mutt -v Mutt 1.0pre3i (1999-09-25) System: Linux 2.2.7 [using ncurses 4.2] Compile options: -DOMAIN -HOMESPOOL -USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK -USE_IMAP -USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP5 +HAVE_PGP2 +HAVE_GPG -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/spool/mail" SHAREDIR="/usr/local/share/mutt" SYSCONFDIR="/usr/local/etc" -ISPELL _PGPPATH="/usr/local/bin/pgp" _PGPV2PATH="/usr/local/bin/pgp" _PGPV3PATH="/usr/local/bin/pgp" _PGPGPGPATH="/usr/local/bin/gpg" As for the output of gdb, that will take a little longer as i don't have gdb installed. And about 9-11 Mb will take a lot of time to download on a slow connection... :-) So, i hope you can tell me what to do with the info above. If no solution is found, i'll post the output of gdb as soon as possible. -Rejo. -- = Rejo Zenger [Sister Ray Crisiscentrum] [EMAIL PROTECTED] = http://mediaport.org/~sisterPGP: RSA FAE40065, DSS/DH 2C8059B5
Re: mailboxes
++ 24/06/99 16:48 -0700 - Terry Reid:
A similar wildcard solution (Michael Elkin's .muttrc distributed with
0.92.5) does not need a specific ("inbox") pattern:
mailboxes `echo $HOME/Mail/*`
This is nice, but it will not work for me. This solution will order the
mailboxes on alphabetic order, not priority. When browsing thru the
various mailboxes with 'c' (and sometimes additionally 'space') they are
ordered in a special order. You can do this by putting the mailboxes in
the order of priority in your .muttrc:
# mailboxes
mailboxes =inbox
mailboxes =special-attn
mailboxes =admin
mailboxes =announce
[...]
When browsing the list, it'll first check inbox for new mail, then
special-attn, then admin, then announce, etc. Some mailinglist have low
priority, others have a higher. Mail send to me personally and things i
need to respond to quickly (special cases of spam etc) have higher
priority.
-Rejo.
--
= Rejo [Sister Ray Crisiscentrum] [EMAIL PROTECTED]
= http://mediaport.org/~sisterPGP: RSA FAE40065, DSS/DH 2C8059B5
Re: reverse_name combined with send-hook
++ 01/07/99 01:50 -0500 - David DeSimone: set reverse_name # reply as the user to whom the mail was sent to #send-hook . my_hdr From: Andy Spiegl [EMAIL PROTECTED] send-hook '~C mutt-' 'my_hdr From: Andy Spiegl [EMAIL PROTECTED]' "my_hdr From" and "reverse_name" do not work together. The former will override the latter. It's a design "feature" of Mutt. I don't understand completely. Are you saying you cannot have this reverse_name when you have alos defined 'my_hdr From:' somewhere? I have the following in my muttrc: set alternates=(([SNIP]|(.*|liveandlocal)@sisterray.xs4all.nl|[SNIP]) set reverse_name [...] send-hook . 'my_hdr From: Rejo [EMAIL PROTECTED]' send-hook . 'my_hdr Reply-To: Rejo [EMAIL PROTECTED]' send-hook . 'set signature=~/.signature' [...] send-hook '~C liveandlocal' 'my_hdr From: Live Local [EMAIL PROTECTED]' send-hook '~C liveandlocal' 'my_hdr Reply-To: Live Local [EMAIL PROTECTED]' I know there's some doubling in the regexp in that alternates line. All the address within @sisterray.xs4all.nl are mine, but when i tried to use '.*@sisterray.xs4all.nl' only it didn't work. It still doesn't work, even when i mention this single name. So, normally i want to reply with "Rejo [EMAIL PROTECTED]", regardless of anything. Then i have some send-hooks for special things. On top of these i would like to reply to all mail send to the address [EMAIL PROTECTED] as "Live Local [EMAIL PROTECTED]". Can't this be done? -Rejo. -- = Rejo [Sister Ray Crisiscentrum] [EMAIL PROTECTED] = http://mediaport.org/~sisterPGP: RSA FAE40065, DSS/DH 2C8059B5
