/usr/share/doc/mutt/PGP-Notes.txt.gz
> I am using the same procmail filter and can say that it works
> perfectly for incoming pgp/gpg mails. However, this does not solve the
> problem with other mail clients that want to have inline PGP messages,
> and
> those are many.
> Is there a way to make m
/usr/share/doc/mutt/PGP-Notes.txt.gz
> I am using the same procmail filter and can say that it works
> perfectly for incoming pgp/gpg mails. However, this does not solve the
> problem with other mail clients that want to have inline PGP messages,
> and
> those are many.
> Is there a way to make
Hi Marc,
* Marc Leeman <[EMAIL PROTECTED]> [09-08-01 11:55]:
> Due to the flexibility of mutt, I would guess that I can solve the
> problem in my config, but as I said, I haven't found a solution quite
> yet.
I use the following procmail rules and a little script (attached)
to convert the conte
Hi Marc,
* Marc Leeman <[EMAIL PROTECTED]> [09-08-01 11:55]:
> Due to the flexibility of mutt, I would guess that I can solve the
> problem in my config, but as I said, I haven't found a solution quite
> yet.
I use the following procmail rules and a little script (attached)
to convert the cont
Your message, Re: Mutt and inline gpg,
was not delivered to the following recipient:
[EMAIL PROTECTED]
Reason: System error: Please re-send your message later.
Recipient: [EMAIL PROTECTED]
--- Begin Message ---
Hi Martin!
On Thu, 09 Aug 2001, Martin Domig wrote:
> Is there a way to make m
Hi Martin!
On Thu, 09 Aug 2001, Martin Domig wrote:
> Is there a way to make mutt send inline PGP messages instead of the
> MIME attachment form?
Although there is a way to tell mutt not to use PGP/MIME, Don't Do It. Mutt
will mistype the message as application/pgp and royally screw up the
readab
Your message, Re: Mutt and inline gpg,
was not delivered to the following recipient:
[EMAIL PROTECTED]
Reason: System error: Please re-send your message later.
Recipient: [EMAIL PROTECTED]
--- Begin Message ---
On Thu, Aug 09, 2001 at 03:51:14PM -0500, Rob VanFleet wrote:
> On Thu, Aug 09, 2
On Thu, Aug 09, 2001 at 03:51:14PM -0500, Rob VanFleet wrote:
> On Thu, Aug 09, 2001 at 05:26:50PM +0200, Christian Kurz wrote:
> > option "pgp_create_traditional". That option might help you very much,
> > but instead I would suggest that the other MUA's get fixed.
>
> Um, wouldn't that be every
Your message, Re: Mutt and inline gpg,
was not delivered to the following recipient:
[EMAIL PROTECTED]
Reason: System error: Please re-send your message later.
Recipient: [EMAIL PROTECTED]
Hi Martin!
On Thu, 09 Aug 2001, Martin Domig wrote:
> Is there a way to make mutt send inline PGP messages instead of the
> MIME attachment form?
Although there is a way to tell mutt not to use PGP/MIME, Don't Do It. Mutt
will mistype the message as application/pgp and royally screw up the
reada
Your message, Re: Mutt and inline gpg,
was not delivered to the following recipient:
[EMAIL PROTECTED]
Reason: System error: Please re-send your message later.
Recipient: [EMAIL PROTECTED]
On Thu, Aug 09, 2001 at 03:51:14PM -0500, Rob VanFleet wrote:
> On Thu, Aug 09, 2001 at 05:26:50PM +0200, Christian Kurz wrote:
> > option "pgp_create_traditional". That option might help you very much,
> > but instead I would suggest that the other MUA's get fixed.
>
> Um, wouldn't that be every
On Thu, Aug 09, 2001 at 05:26:50PM +0200, Christian Kurz wrote:
> option "pgp_create_traditional". That option might help you very much,
> but instead I would suggest that the other MUA's get fixed.
Um, wouldn't that be every other MUA asid from mutt and maybe one or two
others?
-Rob
Christian Kurz <[EMAIL PROTECTED]> writes:
> That option might help you very much, but instead I would suggest
> that the other MUA's get fixed.
I'd like to see all mailers complying with RFC2822 first.
--
Alan Shutko <[EMAIL PROTECTED]> - In a variety of flavors!
If at first you don't succeed,
On Thu, Aug 09, 2001 at 05:26:50PM +0200, Christian Kurz wrote:
> option "pgp_create_traditional". That option might help you very much,
> but instead I would suggest that the other MUA's get fixed.
Um, wouldn't that be every other MUA asid from mutt and maybe one or two
others?
-Rob
--
To U
On 01-08-09 Martin Domig wrote:
> On Thu, Aug 09, 2001 at 08:03:15PM +1000, Matt Hope wrote:
> [...]
> > : When my friends (2 differnt ones, one of which is planning to switch
> > : to mutt) get the mails, they get it in an attachment, have to save it
> > : and decode it manually (apparently kmail
On Thu, Aug 09, 2001 at 03:19:42PM +0200, Martin Domig wrote:
> Is there a way to make mutt send inline PGP messages instead of the
> MIME attachment form?
Well, this is a little kludgy, but it works. Put this in your .muttrc:
# Inline encryption
macro compose \CE "Fgpg -ea\ny"
# C
On Thu, Aug 09, 2001 at 11:55:49AM +0200, Marc Leeman wrote:
> kmail sends the gpg messages inline, and upon arrival decodes them
> immediately. In my config, mutt sends them as attachments.
> When I get a kmail message, I have to save it to file and manually
> decode it (not that difficult, but an
Christian Kurz <[EMAIL PROTECTED]> writes:
> That option might help you very much, but instead I would suggest
> that the other MUA's get fixed.
I'd like to see all mailers complying with RFC2822 first.
--
Alan Shutko <[EMAIL PROTECTED]> - In a variety of flavors!
If at first you don't succeed
It sounds like the real fix for this is to change kmail's behavior
If none of the involved parties is willing to, I volunteer to take
it to the kmail mailing list at:
subscribe:
mailto:[EMAIL PROTECTED]
archive:
http://lists.kde.org/?l=kmail&r=1&w=2
I did notice that there is a bu
On 01-08-09 Martin Domig wrote:
> On Thu, Aug 09, 2001 at 08:03:15PM +1000, Matt Hope wrote:
> [...]
> > : When my friends (2 differnt ones, one of which is planning to switch
> > : to mutt) get the mails, they get it in an attachment, have to save it
> > : and decode it manually (apparently kmail
On Thu, Aug 09, 2001 at 03:19:42PM +0200, Martin Domig wrote:
>
> I am using the same procmail filter and can say that it works
> perfectly for incoming pgp/gpg mails. However, this does not solve the
> problem with other mail clients that want to have inline PGP messages, and
> those are many.
>
On Thu, Aug 09, 2001 at 03:19:42PM +0200, Martin Domig wrote:
> Is there a way to make mutt send inline PGP messages instead of the
> MIME attachment form?
Well, this is a little kludgy, but it works. Put this in your .muttrc:
# Inline encryption
macro compose \CE "Fgpg -ea\ny"
#
On Thu, Aug 09, 2001 at 11:55:49AM +0200, Marc Leeman wrote:
> kmail sends the gpg messages inline, and upon arrival decodes them
> immediately. In my config, mutt sends them as attachments.
> When I get a kmail message, I have to save it to file and manually
> decode it (not that difficult, but a
It sounds like the real fix for this is to change kmail's behavior
If none of the involved parties is willing to, I volunteer to take
it to the kmail mailing list at:
subscribe:
mailto:[EMAIL PROTECTED]
archive:
http://lists.kde.org/?l=kmail&r=1&w=2
I did notice that there is a b
Hello list
On Thu, Aug 09, 2001 at 08:03:15PM +1000, Matt Hope wrote:
[...]
> : When my friends (2 differnt ones, one of which is planning to switch
> : to mutt) get the mails, they get it in an attachment, have to save it
> : and decode it manually (apparently kmail is expecting inline messages).
On Thu, Aug 09, 2001 at 03:19:42PM +0200, Martin Domig wrote:
>
> I am using the same procmail filter and can say that it works
> perfectly for incoming pgp/gpg mails. However, this does not solve the
> problem with other mail clients that want to have inline PGP messages, and
> those are many.
Hello list
On Thu, Aug 09, 2001 at 08:03:15PM +1000, Matt Hope wrote:
[...]
> : When my friends (2 differnt ones, one of which is planning to switch
> : to mutt) get the mails, they get it in an attachment, have to save it
> : and decode it manually (apparently kmail is expecting inline messages)
On Thu, 09 Aug 2001, Marc Leeman <[EMAIL PROTECTED]> wrote...
: kmail sends the gpg messages inline, and upon arrival decodes them
: immediately. In my config, mutt sends them as attachments.
: When I get a kmail message, I have to save it to file and manually
: decode it (not that difficult, but
This is about the 4th time in as many years that I changed my e-mail client
and every time I feel I have gained.
I'm now using mutt now and am still in the process of finetuning. However,
I have the following problem, of which I didn't find a solution yet.
I am using gpg and in communication with
On Thu, 09 Aug 2001, Marc Leeman <[EMAIL PROTECTED]> wrote...
: kmail sends the gpg messages inline, and upon arrival decodes them
: immediately. In my config, mutt sends them as attachments.
: When I get a kmail message, I have to save it to file and manually
: decode it (not that difficult, but
This is about the 4th time in as many years that I changed my e-mail client
and every time I feel I have gained.
I'm now using mutt now and am still in the process of finetuning. However,
I have the following problem, of which I didn't find a solution yet.
I am using gpg and in communication with
32 matches
Mail list logo
