Re: download pgpwrap from where?
savanna [[EMAIL PROTECTED]] wrote: > Where do I download pgpewrap from? It's referred to in the sample > muttrc files, for encrypting mail with gpg, however I can't find it > anywhere on the web (though I've found hundreds of references to using > it in my .muttrc ;-) ). > > I've searched debian.org, rpmfind, and the archives of mutt-users. > > Here's one of the offending lines from my .muttrc: > > set pgp_encrypt_sign_command="pgpewrap gpg --passphrase-fd 0 -v --batch > --output - --encrypt --sign %?a?-u %a? --armor --always-trust -- -r %r > -- %f" I use it here, I can send it to you if you want. Email me if you still need. I only have the binary though (about 23k). -- Bruno Lustosa, aka Lofofora | Email: [EMAIL PROTECTED] Network Administrator/Web Programmer | ICQ UIN: 1406477 Rio de Janeiro - Brazil | msg31337/pgp0.pgp Description: PGP signature
Re: Weird bug/feature ?
Cedric Duval [[EMAIL PROTECTED]] wrote:
> 'a' attaches a file, not a message (of course, the message can be in one
> file like with the mbox format - but not with maildir).
>
> There is a more appropriate function for what you want to do:
> ('A').
Right, I didn't know about the attach-message command. Just thought that
as the message was in a file, I could go and select it as any other
file, but I guess when I select the maildir, mutt recognizes it as such
instead of seeing it as just a directory.
Many thanks!!
--
Bruno Lustosa, aka Lofofora | Email: [EMAIL PROTECTED]
Network Administrator/Web Programmer | ICQ UIN: 1406477
Rio de Janeiro - Brazil |
msg31080/pgp0.pgp
Description: PGP signature
Weird bug/feature ?
Hello. Today I was caught in the situation where I received a message from someone, and needed to forward a second message inside a reply to this one. Basically, something like this: - Someone sends me message 1 - I receive message 2 - I want to reply to 1, forwarding 2 What did I do? Saved message 2 somewhere (using maildir format), and replied normally to message 1. As soon as I finished editting, I pressed "a" to attach the message I saved to my mail. As usual, I pressed "?" to browse to the directory. But as soon as I entered the folder I had saved the message on (the maildir folder itself), mutt gave me an error saying it couldn't open that dir. However, attaching the file without using "?", and doing normal s worked just fine: Message was saved in /tmp/oi, so mutt made the maildir structure inside this directory. when I browse to /tmp and press enter on directory "oi", it gives me an error "Couldn't open //tmp/oi". Notice the extra slash on the beginning. Seems like a small bug, but a bug indeed (or a feature?? :)). -- Bruno Lustosa, aka Lofofora | Email: [EMAIL PROTECTED] Network Administrator/Web Programmer | ICQ UIN: 1406477 Rio de Janeiro - Brazil | msg31053/pgp0.pgp Description: PGP signature
Re: Changing attachment mime type
Thomas Roessler [[EMAIL PROTECTED]] wrote: > On 2002-09-10 10:40:46 -0300, Bruno Lustosa wrote: > > >I received a message from someone using outlook containing an > >email attached (*.eml). Unfortunately, outlook sends the > >attachment as "application/octet-stream", so mutt can't really > >recognize it automatically. Then I open the message in mutt, hit > >ctrl-e and change the type to "message/rfc822". > > What content-transfer-encoding was used for that body part? base64? > > In that case, the message which results from changing the > content-type would violate applicable standards and mutt's > expectations... Fixing this is, of course, possible, but would > considerably complicate some code. Text part (the message) is quoted-printable, attachment is base64, as you guessed. -- Bruno Lustosa, aka Lofofora | Email: [EMAIL PROTECTED] Network Administrator/Web Programmer | ICQ UIN: 1406477 Rio de Janeiro - Brazil | msg30866/pgp0.pgp Description: PGP signature
Changing attachment mime type
Hello, I found what seems to be a bug. Well, it IS a bug. Don't know if it is mutt's or LookOut's. I received a message from someone using outlook containing an email attached (*.eml). Unfortunately, outlook sends the attachment as "application/octet-stream", so mutt can't really recognize it automatically. Then I open the message in mutt, hit ctrl-e and change the type to "message/rfc822". After opening the message again, it displays its contents normally. Inside this attached message, there is an attached windows media movie (*.wmv). And AGAIN, it shows up wrongly, this time as a "text/plain". And there comes what I think might be a bug in mutt. In the pager, it displays the attachment as: [-- Type: video/x-ms-wmv, Encoding: base64, Size: 1.0M --] [-- video/x-ms-wmv is unsupported (use 'v' to view this part) --] However, hitting "v" to view the message's attachments shows the attachment as: I 3 [text/plain, 7bit, 1.4M] Apparently, mutt displays the message correctly in the pager display (correct type, correct size). In attachment menu, it shows up encoded (bigger size, text/plain). I tried hitting ctrl-e in attachment menu to change it's type to video/x-ms-wmv, but it stills shows the same (only thing that changes is the text/plain to video/x-ms-wmv, but content is still the same, encoded). I know I can just save it to a file and try to decode it manually using the usual mime tools, but I wanted people to know about it, and enlighten me if this is not a bug in mutt (of course, the brokeness of outlook could do anything!). -- Bruno Lustosa, aka Lofofora | Email: [EMAIL PROTECTED] Network Administrator/Web Programmer | ICQ UIN: 1406477 Rio de Janeiro - Brazil | msg30841/pgp0.pgp Description: PGP signature
Re: rtfm dammit
[EMAIL PROTECTED] [[EMAIL PROTECTED]] wrote: > Actually my sig is at least ELEVEN lines, but hey, whose counting ? > ( FYI - The last part of the sig has a word riddle in it) > //\ eLviintuaxbilse/\\ Linux is evitable? What's the sense on it? -- Bruno Lustosa, aka Lofofora | Email: [EMAIL PROTECTED] Network Administrator/Web Programmer | ICQ UIN: 1406477 Rio de Janeiro - Brazil | msg30812/pgp0.pgp Description: PGP signature
Re: flaming is art - dammit!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sven, are you a BOFH or what? Sven Guckes [[EMAIL PROTECTED]] wrote: > (...) > Sven [who knows only a few good flamers who actively post] > (...) - -- Bruno Lustosa, aka Lofofora | Email: [EMAIL PROTECTED] Network Administrator/Web Programmer | ICQ UIN: 1406477 Rio de Janeiro - Brazil | -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9c2r8iNfNvfQ8L5IRAnZgAJ0TD1RJSzNZWNexWX/7bbtcY/6YqACfXmR0 BRdRDop0VlGUnWHNjE4Bwv4= =PhTI -END PGP SIGNATURE-
Mutt and PGP v5
Hello, I'm having some problems on getting mutt to work (properly) with PGP 5.0. Does anyone here use it? I already compiled mutt 1.0i with support for PGP (had to hack the configure script though). I've set the proper variables and generated a key for me using pgpk -g. Now, for the questions: When I finish writing a message, I have the common PGP options available. If I do a -k, it should send my public (or another one I choose) key to the recipient, right? After I generated the key for me, there seems to have 2 keys, both selectable, but with some kind of different flags (one with a 's' and other with a 'e'). What is the difference between them? I can sign my messages normally, no problem, but it seems that with the -k mutt is not appending (sometimes it appends) the selected public key to the end of the message. Also, there appears some odd messages (no file, writting to stdin, no config file found), etc etc. Is there a way to suppress these messages? I've already read loads of documentation about mutt with pgp, but I think my questions deal more with pgp than with mutt (i think). Does anyone here use it, and would be willing to give me a hand? Thanks in advance, Bruno Lustosa
Re: one click save/sending?
Hello, I'm having some problems on getting mutt to work (properly) with PGP 5.0. Does anyone here use it? I already compiled mutt 1.0i with support for PGP (had to hack the configure script though). I've set the proper variables and generated a key for me using pgpk -g. Now, for the questions: When I finish writing a message, I have the common PGP options available. If I do a -k, it should send my public (or another one I choose) key to the recipient, right? After I generated the key for me, there seems to have 2 keys, both selectable, but with some kind of different flags (one with a 's' and other with a 'e'). What is the difference between them? I can sign my messages normally, no problem, but it seems that with the -k mutt is not appending (sometimes it appends) the selected public key to the end of the message. Also, there appears some odd messages (no file, writting to stdin, no config file found), etc etc. Is there a way to suppress these messages? I've already read loads of documentation about mutt with pgp, but I think my questions deal more with pgp than with mutt (i think). Does anyone here use it, and would be willing to give me a hand? THanks in advance, Bruno Lustosa
