I had some involvement in configuring the Salesforce Marketing Cloud (ExactTarget) list-ID header to work in that manner. I definitely understand wanting a more friendly, human-readable version of the header. Currently it has the identifier it does because that was the most stable per-client identifier we could easily put in there at the time we designed the feature. I'll log making it more human readable (maybe based on the visible from domain instead?) as a feature request / wish list item, though I can't make any guarantees on if/when that change would happen.
In the mean time, you might want to try using something like the from domain as the folder name, instead. It'll mostly correlate well enough. Some clients may have more than one of those numeric IDs, but if they're using the same from domain, it's the same client, so for your purposes routing them to the same folder makes sense. BTW, we were required to add list-ID support as a condition of joining the Certified Sender Alliance (CSA) in Europe. I also do like it as it provides a relatively stable sender identifier for filtering purposes in Gmail and elsewhere (like procmail). Cheers, Al Iverson On Thu, Feb 21, 2019 at 12:33 PM Steve Atkins <[email protected]> wrote: > > > > > On Feb 21, 2019, at 5:17 PM, Brandon Applegate <[email protected]> wrote: > > > > Hello all, > > > > I searched the archives and didn’t quite find the info I’m looking for. > > I’ll have to bore you with some details of some changes I recently made to > > get to my point… > > > > I had been using procmail $forever. I just recently kicked over to > > maildrop. So far so great. To that end - I have a pretty neat piece of > > config that autocreates and files mailing list messages based on List-ID > > header. To my surprise - some “marketing” types of mail (i.e. my bank, > > retailers, etc) were getting filed info folders like “1901173” and the > > like. Digging in - I see headers with a List-ID of NNNNNN.xt.local (I > > believe the xt is ExactTarget). I really want these to come to my inbox > > (so at least I can unsubscribe from them) - and I certainly don’t want the > > mess of cryptically named folders getting created. I know this is part of > > the tradeoff in trusting List-ID and creating folders, but for 99% of what > > I do - this is legitimate “good old fashioned” (technical) mailing lists. > > > > Has anyone dealt with this issue and would care to share ? For now I have > > a simple regex matching the NNNNNN.xt.local and short circuiting into my > > inbox. I suppose Ill come across any other outliers like this going > > forward - but was hoping perhaps someone on the list already had some good > > regex to catch more of these. > > > > PS: Mini-rant. I guess the List-ID header isn’t the sacred ground of only > > “real” mailing lists - but I was (naively perhaps) surprised that a “cloud > > marketing solution” would be using it in the manner than they are. > > > > Thanks in advance for any wise words on this. > > List-ID is widely used. To uniquely identify mailing lists, reasonably > enough. :) > > If you're naively using it to route mail to maiboxes, and automatically > creating those mailboxes based on the value in it you're going to catch a > fair bit of email that's not traditional discussion lists. Also some spam > with random-ish values in the header. > > I have a sieve rule for each mailing list that identifies it based on the > List-ID value and routes it to the right mailbox - you'll likely want to do > the same. It's a few seconds of work each time I sign up for a mailing list, > but that's not a terribly common thing. > > Cheers, > Steve > > > _______________________________________________ > mailop mailing list > [email protected] > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop -- al iverson // wombatmail // miami http://www.aliverson.com http://www.spamresource.com _______________________________________________ mailop mailing list [email protected] https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
