From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: DSig + gnus-posting-styles?
Date: Tue, 22 Jul 2008 08:12:28 -0500 [thread overview]
Message-ID: <86ej5mf4g3.fsf@lifelogs.com> (raw)
In-Reply-To: <m24p6jpbws.fsf@nwalsh.com>
On Mon, 21 Jul 2008 10:08:51 -0400 Norman Walsh <ndw@nwalsh.com> wrote:
NW> / Norman Walsh <ndw@nwalsh.com> was heard to say:
NW> | I've just discovered that my signed messages don't make it through to
NW> | my colleagues crackberries. Apparently something in the gateway drops
NW> | messages with attachments, or something.
NW> |
NW> | Can EPG be configured via gnus-posting-styles so that I can turn it on
NW> | and off on a per-group basis?
NW> I gather from the lack of replies that the answer is "no". Anyone want
NW> to wack me with a clue-by-four about how to get this behavior?
Not with gnus-posting-styles AFAIK but you can try a hook on summary
entry that sets things up appropriately based on the group name.
Ted
next prev parent reply other threads:[~2008-07-22 13:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 17:12 Norman Walsh
2008-07-16 17:19 ` Adam Sjøgren
2008-07-21 14:08 ` Norman Walsh
2008-07-22 13:12 ` Ted Zlatanov [this message]
2008-07-23 2:43 ` Rob Weir
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86ej5mf4g3.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).