Hi Art,
You are correct, the message was misfiled. The software couldn't determine whether it was brc-news or brc-discuss, and guessed incorrectly. Thank you very much -- I haven't had a misfile report for a long time. I'll fix it; technical details follow. One question -- your message had some fairly interesting custom headers like "X-Post:" Is that unique to your list, or am I likely to see similar headers on many other lists? Jeff ================================================ Normally, it decides by looking for matches in other headers, but despite many human understandable clues present we didn't pick it up: >Return-Path: [EMAIL PROTECTED] The "worker-" prefix prevented a match. >Received: (from lists@localhost) > by lists.tao.ca (8.9.3/TAO5) id TAA17381 > for brc-discuss-outgoing; Tue, 5 Sep 2000 19:46:00 -0400 Not close enough to match. >Sender: [EMAIL PROTECTED] Again, the worker prefix threw the software off off. >Reply-To: [EMAIL PROTECTED] We deliberately don't use reply-to when working on deciding a crosspost, as it is very often set to something weird (and likely to throw of the decision). Maybe I should revisit that. >X-Subscribe: <mailto:[EMAIL PROTECTED]?body=subscribe%20brc-discuss> >X-Unsubscribe: <mailto:[EMAIL PROTECTED]?body=unsubscribe%20brc-discuss> Don't look at these fields, also insufficient information for a match. >X-Help: <mailto:[EMAIL PROTECTED]?subject=brc-discuss> Don't look for this field, also has worker- prefix. >X-Archive1: <http://www.mail-archive.com/[email protected]> I'm honored. :) >X-Post: <mailto:[EMAIL PROTECTED]> This one we can easily match against, and I'll tell the software to look for it. _______________________________________________ Gossip mailing list [EMAIL PROTECTED] http://jab.org/cgi-bin/mailman/listinfo/gossip
