From: Bob Newell <bobnewell@bobnewell.net>
To: ding@gnus.org
Subject: Re: BBDB Integration
Date: Tue, 07 Dec 2021 07:33:32 -1000 [thread overview]
Message-ID: <87wnkguxoz.fsf@emailmessageidheader.nil> (raw)
In-Reply-To: <871r2qhs9n.fsf@hillenius.net> (=?utf-8?Q?=22G=C4=B3s?= Hillenius"'s message of "Mon, 06 Dec 2021 12:44:36 +0100")
Aloha,
This might more properly go in the BBDB mailing list but I'm
continuing this thread.
Here are some variables that I set when capturing mail
addresses from gnus to BBDB.
(setq bbdb-mua-auto-update-p 'bbdb-select-message)
;;; We also need to change the default update behavior.
(setq bbdb-mua-update-interactive-p '(t . query))
(setq bbdb-update-records-p 'create)
;;; This causes trouble. But setting to nil causes more trouble as too
;;; many spurious dups are found.
(setq bbdb-allow-duplicates t)
;;; Auto-extend and auto-update names and emails.
(setq bbdb-add-mails t)
;;; BUT don't change primary names and bug about AKA, new mails, etc.
(setq bbdb-add-name nil)
(setq bbdb-add-aka t)
(setq bbdb-new-mails-primary nil)
(setq bbdb-ignore-redundant-emails t)
;;; Updates are silent.
(setq bbdb-mua-pop-up nil)
Also something to look into is bbdb-accept-message-alist and
bbdb-ignore-message-alist. I use these to avoid capturing
addresses from some sources, for instance, I don't want to
capture every single address on every single mailing list. I
especially don't want a zillion "donotreply" addresses in the
database.
--
Bob Newell
Honolulu, Hawai`i
- Via GNU/Linux/Emacs/Gnus/BBDB
next prev parent reply other threads:[~2021-12-07 17:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 10:51 Daniel Fleischer
2021-12-06 10:58 ` Emanuel Berg
2021-12-06 11:44 ` Gijs Hillenius
2021-12-07 17:33 ` Bob Newell [this message]
2021-12-06 12:46 ` Eric S Fraga
2021-12-06 13:44 ` Daniel Fleischer
2021-12-06 14:00 ` Eric S Fraga
2021-12-06 16:09 ` Daniel Fleischer
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=87wnkguxoz.fsf@emailmessageidheader.nil \
--to=bobnewell@bobnewell.net \
--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).