Re: getting bbdb3 to work with mh-e

I am doing much better with bbdb now.
A bunch of emails that have DKIM/DMARC/ARC headers cause confusion.
I expect that it is the MH-E routine that is in charge of extracting a
header, it is not properly anchored to ^ when it looks, as it gets confused
by the line:

 h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;

which is part of this header:

ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none;
 b=b7Ib3BPjPDSu28kz1Za8SVFCh5ZFJmAZvL1+p8mb5mFGiB+04GPaVrKKo6WfXG6l4EYt5a62ssaDErzLjUueGJij3G4d10Lu8iPNn7LTa7amH9MVAaTCO+dwW7wavflFvX/zVjCgvzO9S5vdqhEgMTC5GqOmmGtO7ZPU4f8meCNXD2n2FceHCvstrRrQDlZIJBZ+5Es4/HZKSLewNv9L9uOplzV5Nc8bAFsIw6Pe9olbMaHxo5wRs5C6Ccu/2cLx/uH3CaMEkYVMQvEqV8ToipaZ5NBfVl9DRT6ahlKt2pcA8b8i7BTDkHkbYy8Hm8L6XWZVqwJVj6ZE2bhejzYnoQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;
 s=arcselector9901;
 h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
 bh=X1vpEiPPqdLZGI0eXI4Rn12OFFQ1v0Vtcyu5RKnqRms=;
 b=X8dFFe8XWgdeo0VEpdWHGEmaVmJ/SwOB0Zcw2OhlW8xzuY5Jtzd9KiJdz09JNTRRMa15D4fkkTHZyzEOLcJEkjGbaGw/oSOn+X04bPNWy4Pv5hYpRCxxmniBe1+TF0iLSQxPlJ/ql5Z6TC9GrLktY3BZKnId3OO+gnkpJ+OoVJabhQfx9aQjdEZfeIkMxLvGmPqUu8Kt8URArwwvnzrn3TjSU47YlZk2DHLiKrVyc88BWmXrtdxqi+4NGfsW3cARLAsXlexd9ipaNJ6mqBdkdjCbJnS8cs5VKg/nqYZg0XWCZ9x2K19Dqy+v5wrD7l5RshkupjWDaNE4Md/hX/S64g==

You can see the From: in there. Ick.

I am looking into this, but haven't found a solution, and just thought I'd
share the problem.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     [email protected]  http://www.sandelman.ca/        |   ruby on rails    [