From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 739650830336 X-Google-Groups: supmua X-Google-Thread: 3030fda1bf,545a92579e5dbaca,start X-Google-Attributes: gid3030fda1bf,domainid0,public,googlegroup X-Google-NewGroupId: yes X-Received: by 10.182.24.170 with SMTP id v10mr20547920obf.25.1431366641710; Mon, 11 May 2015 10:50:41 -0700 (PDT) X-BeenThere: supmua@googlegroups.com Received: by 10.182.158.72 with SMTP id ws8ls948469obb.31.gmail; Mon, 11 May 2015 10:50:41 -0700 (PDT) X-Received: by 10.182.138.9 with SMTP id qm9mr64726obb.34.1431366641377; Mon, 11 May 2015 10:50:41 -0700 (PDT) X-Google-Doc-Id: 215b088c8d4e5e2c X-Google-Web-Client: true Date: Mon, 11 May 2015 10:50:40 -0700 (PDT) From: Michael Parks To: supmua@googlegroups.com Message-Id: <1743381a-df32-477b-82fb-266f3bed8099@googlegroups.com> Subject: Editing names before they're indexed MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_2156_989298884.1431366640861" X-Google-Token: EPDXw6oF_tIjBKbrWDk0 X-Google-IP: 8.7.94.151 ------=_Part_2156_989298884.1431366640861 Content-Type: multipart/alternative; boundary="----=_Part_2157_1327948314.1431366640861" ------=_Part_2157_1327948314.1431366640861 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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" , #Engineering , "Medhurst, Louisa" , "Koss, Lucius" , "Mufeeda-Nazari, Judi" , "Tranter, Lilian" , "Kingsmill, Jeremy" , "Rowan, Mary" , "Abdullahi, Abraham" , "McMinn, Matthew" 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 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? ------=_Part_2157_1327948314.1431366640861 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Me again - thanks for the previous help on that indexing t= hing. Hooks are definitely the way to go!

I've got anoth= er 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 exchang= e 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 applica= tions of newline characters. What this means is that Sup sees people's name= s 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"
  &nbs= p; <Louisa.Medhurst@company.com>, "Koss, Lucius"
    <Lucius.Koss@company.co= m>, "Mufeeda-Nazari, Judi"
    <Judi.Mufeedanazari@company.com>, "Tranter, L= ilian"
   = <Lilian.Tranter@company.com>, "Kingsmill, Jeremy" <Jeremy.Kingsmi= ll@company.com>, "Rowan,
 Mary" <Mary.Rowan@company.com>, "Abdullahi, Abraham"
    <Abra= ham.Abdullahi@company.com>, "McMinn,
 Matthew" <Matthew.Mcminn@company.com>


In this case, Mary Rowan and Matthew McMinn's names wo= uld 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 proce= ssed and broken down into its component people. I've got a regex which I ca= n use with String#split to rewrite the names into a more sane format (and b= y "more sane", I mean "with newlines after each name<email> pair").

=
However, it looks like all of S= up'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?
------=_Part_2157_1327948314.1431366640861-- ------=_Part_2156_989298884.1431366640861--