From: Moritz Wilhelmy <moritz+sup@wzff.de>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] best method for before-add-message.rb
Date: Sun, 13 Feb 2011 02:34:27 +0100 [thread overview]
Message-ID: <1297560324-sup-4333@niflheimr> (raw)
In-Reply-To: <1297375381-sup-2823@plc.intranet.plecavalier.com>
Hi,
what would be the best way to match - for instance - the List-Id-Header in case
it's present? I've been wondering about this for a long time, right now, I'm
matching the raw-header against some regex, but it breaks if the line I'm
matching contains a newline (i.e. the header field is longer than one line).
Is there any way around this? Right now I'm doing something along the lines of
this:
# Mailing lists
lids_re = {
/<foo\.lists\.foo\.com>/ => "foo",
/<dev\.something\.org>/ => ["something", "devel"]
}
def add_labels message, labels
labels.each do |l|
message.add_label l
end
end
if message.raw_header =~ /^List-I[dD]: ([^\n]+)/
#log "List ID: #{$1}"
message.add_label "list"
lids_re.keys.each do |re|
add_labels message lids_re[re] if $1 =~ re
end
end
Can I pull arbitrary, parsed headers directly out of the message object, or do
I have to do my own parsing?
Best regards,
Moritz
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2011-02-13 2:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 14:44 Philippe LeCavalier
2011-02-10 16:40 ` Mark Alexander
[not found] ` <1297356327-sup-9107@plc.intranet.plecavalier.com>
[not found] ` <1297357197-sup-5893@bloovis.org>
2011-02-10 19:19 ` Philippe LeCavalier
2011-02-10 22:09 ` Philippe LeCavalier
2011-02-13 1:34 ` Moritz Wilhelmy [this message]
2011-02-13 9:51 ` Tero Tilus
2011-02-13 13:00 ` [sup-talk] How to treat List-Id headers (Was: best method for before-add-message.rb) Moritz Wilhelmy
2011-02-13 17:45 ` [sup-talk] best method for before-add-message.rb Rich Lane
2011-02-13 17:12 ` Hamish D
2011-02-13 18:08 ` Philippe LeCavalier
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=1297560324-sup-4333@niflheimr \
--to=moritz+sup@wzff.de \
--cc=sup-talk@rubyforge.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