James M Galvin <[EMAIL PROTECTED]> writes: > Some vacation programs also ignore "precedence: bulk" and the like, > so maybe memail is counting on that? > Precedence is another one of those problematic headers. Popularized by > USENET, today it enjoys so many different uses that making your > statement out of context is specious. Popularized by Usenet? Huh? Precedence has never been a Usenet header that I've ever seen. The oldest use of precedence that I'm aware of is that Precedence: junk has been in the headers generated by the old-style Unix vacation program for eons, and sendmail.cf had handling of a few different types of precedence headers and they had some effect on queue prioritization. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
- Re: elist address or your add... Tim Pierce
- Re: elist address or your add... Chuq Von Rospach
- Re: elist address or your add... Tim Pierce
- Re: elist address or your add... David W. Tamkin
- Re: elist address or your add... Aaron Schrab
- Re: elist address or your add... Paul Hoffman / IMC
- Re: elist address or your add... Chuq Von Rospach
- PINE Filtering /& Subj... Paul K-
- Re: elist address or your address in message TO header SRE
- Re: elist address or your address in message TO he... James M Galvin
- Re: elist address or your address in message T... Russ Allbery
- Re: elist address or your address in message TO he... Chuq Von Rospach
- Re: elist address or your address in message TO header Rich Kulawiec
- Re: elist address or your address in message TO header Gerald Oskoboiny
- Re: elist address or your address in message TO header James M Galvin
- Re: elist address or your address in message TO he... Rich Kulawiec
- Re: elist address or your address in message TO header James M Galvin
- Re: elist address or your address in message TO he... Chuq Von Rospach
- Re: elist address or your address in message T... James M Galvin
- Re: elist address or your address in messa... Chuq Von Rospach
