From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: getting bbdb to use gnus/gcc
Date: 20 Aug 2000 23:17:46 +0200 [thread overview]
Message-ID: <vafn1i7vdhh.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: "G. Todd"'s message of "19 Aug 2000 19:27:48 -0400"
On 19 Aug 2000, G. Todd wrote:
> It's not possible to set bbdb-send-mail-style to a self defined
> function so asking bbdd to use (send-mail) results in an error.
>
> Has anyone figured out how to get bbdb to use gnus more fully to
> send mail?
What you want to do is to create a new user-mail-agent. I have
discussed with the BBDB maintainers about modifying the code such that
compose-mail is used to compose a message (and thus the
user-mail-agent setting is honored). I'm not sure about the result,
though. Maybe you would like to take that up on the BBDB mailing
list.
The archive of this list (the Gnus mailing list) should have something
if you search for `define-mail-user-agent' and `gnus-user-agent'.
kai
--
I like BOTH kinds of music.
prev parent reply other threads:[~2000-08-20 21:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-19 23:27 G. Todd
2000-08-20 21:17 ` Kai Großjohann [this message]
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=vafn1i7vdhh.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--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).