From: "Roland Winkler" <winkler@gnu.org>
To: Mitchel Humpherys <mitch.special@gmail.com>
Cc: ding@gnus.org, bbdb-info@lists.sourceforge.net
Subject: Re: bbdb-ignore-message-alist
Date: Sat, 8 Sep 2012 11:18:38 -0500 [thread overview]
Message-ID: <20555.28638.917822.416598@gargle.gargle.HOWL> (raw)
In-Reply-To: <CAOFALwJXyr0tzKch9zOLeOc+m_hgB9Jzo4p7BBVnyCxGAbFQrg@mail.gmail.com>
On Tue Aug 28 2012 Mitchel Humpherys wrote:
> I'd like to configure bbdb to not auto-notice addresses in mailing
> list mail. I'm trying to use the `X-Mailing-List' and
> `X-Mailman-Version' headers, since those seem to be consistently
> present on all the mailing lists I read, but it doesn't seem to be
> working (i.e. bbdb still offers to save email addresses from mails
> containing those headers)... What am I doing wrong?
>
> (setq bbdb-ignore-message-alist
> '((("X-Mailman-Version" "X-Mailing-List") . ".*")))
I am trying to crosspost this on the gnus mailing list, too, because
your problem has to do with some subtleties of Gnus that go beyond
my knowledge of Gnus.
Gnus has two functions for accessing headers of a message,
gnus-fetch-field and gnus-fetch-original-field. The latter uses
gnus-original-article-buffer. I do not know which buffer the former
function is using. Only gnus-original-article-buffer contains the
X-* headers you want to access. But BBDB currently uses
gnus-fetch-field to access the headers of a Gnus message. So that's
why BBDB believes the messages had no X-* headers.
So my question is: What should BBDB do to access the headers of a
Gnus message in a way that is both reliable and efficient?
Thanks,
Roland
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
bbdb-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/
next parent reply other threads:[~2012-09-08 16:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOFALwJXyr0tzKch9zOLeOc+m_hgB9Jzo4p7BBVnyCxGAbFQrg@mail.gmail.com>
2012-09-08 16:18 ` Roland Winkler [this message]
2012-09-08 19:20 ` [BBDB] ChangeLog 2012-09-8 (bbdb-ignore-message-alist) Roland Winkler
2012-09-10 17:20 ` Mitchel Humpherys
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=20555.28638.917822.416598@gargle.gargle.HOWL \
--to=winkler@gnu.org \
--cc=bbdb-info@lists.sourceforge.net \
--cc=ding@gnus.org \
--cc=mitch.special@gmail.com \
/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).