From: Michael Parks <mparks@tkware.info>
To: supmua@googlegroups.com
Subject: Editing names before they're indexed
Date: Mon, 11 May 2015 10:50:40 -0700 (PDT) [thread overview]
Message-ID: <1743381a-df32-477b-82fb-266f3bed8099@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1985 bytes --]
Me again - thanks for the previous help on that indexing thing. Hooks are
definitely the way to go!
I've got another issue which I think i've tracked down the reason for. I
currently get my work email (hosted on an Exchange server) via Davmail,
which provides the IMAP port I use with offlineimap which pulls into sup.
Not at all confusing, right?
Horrible exchange server -> Davmail -> Offlineimap -> Sup
What's happening is somewhere along the line, the header lines containing
the from/to/cc/etc addresses are getting mangled. I'm not sure where in the
chain this is happening, but it manifests in the headers as random
applications of newline characters. What this means is that Sup sees
people's names as something like, for my name, 'Michael"'.
Here's one of the crocked headers (don't worry, these names are all bogus):
To: : "Lockman, Xavier" <Xavier.Lockman@company.com>, #Engineering
<Engineering@company.com>, "Medhurst, Louisa"
<Louisa.Medhurst@company.com>, "Koss, Lucius"
<Lucius.Koss@company.com>, "Mufeeda-Nazari, Judi"
<Judi.Mufeedanazari@company.com>, "Tranter, Lilian"
<Lilian.Tranter@company.com>, "Kingsmill, Jeremy"
<Jeremy.Kingsmill@company.com>, "Rowan,
Mary" <Mary.Rowan@company.com>, "Abdullahi, Abraham"
<Abraham.Abdullahi@company.com>, "McMinn,
Matthew" <Matthew.Mcminn@company.com>
In this case, Mary Rowan and Matthew McMinn's names would be indexed as
'Mary"' and 'Matthew"', with their last names being lost entirely.
What i'd like to be able to do is play with the message header before it's
processed and broken down into its component people. I've got a regex which
I can use with String#split to rewrite the names into a more sane format
(and by "more sane", I mean "with newlines after each name<email> pair").
However, it looks like all of Sup's hooks take effect after this processing
has already been completed.
Is there a supported way to tweak the incoming messages before they're
processed?
[-- Attachment #1.2: Type: text/html, Size: 3242 bytes --]
next reply other threads:[~2015-05-11 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 17:50 Michael Parks [this message]
2015-05-11 19:59 ` [sup] " Ruthard Baudach
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=1743381a-df32-477b-82fb-266f3bed8099@googlegroups.com \
--to=mparks@tkware.info \
--cc=supmua@googlegroups.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