On Wednesday 06 May 2009, Barbara Duprey wrote: >Gene Heskett wrote: >> On Wednesday 06 May 2009, McLauchlan, Kevin wrote: >>> HOWEVER, less than two years ago, on this list, we had examples of >>> people not receiving the message footer parts. In fact I recall >>> receiving posts from _some_ posters (who posted only to the list, not to >>> individual members) where the incoming message did not contain the >>> unsubscribe administrivia at the bottom. I forget what was the source >>> of that situation, but it might be relevant to some of the people having >>> trouble. >> >> Such examples are endemic Kevin. So lets take a poll here. >> >> How many receivers of this list can see a quote by sci-fi author Ed >> Howdershelt at the bottom of this message? if you can, your email agent >> is good. If its stripped, your email agent is broken. It really is that >> simple. >> >> Many email agents think they are doing the user a favor when they strip >> the useless (to them) sigs from the bottom of a message before they show >> it to the reader, and since the convention in email formatting places a >> 'newline dash dash space' as the sig separator, this is very easy for them >> to do. But it is not correct to strip it until one hits the reply keys, >> then it actually becomes wasted space cuz most will add their own. Until >> that reply key is hit, it should show you this stuff, which is appended by >> the server as the last 2 lines or so of the message it forwards to the >> subscribers. Below my sig. > >Your sig came through, but I don't think that is the cause of the >missing unsubscribe trailer -- it has a long string of dashes, not the >standard two, so it would not follow the rules for sig stripping. My >best guess is that those who use gmail addresses for posting do not get >the trailer on their posts, while others do (sometimes grayed out below >a user sig, as for yur post, and therefore not repeated in replies). I >haven't really investigated that, though. Anybody else figured out >what's happening here?
The long chain of dashes should not trigger that, unless the author of that particular email agent is a blithering idiot. I am not going to apply that label unless I have seen the proof with my own eyes. More important in my logical (generally how I think) reasoning is that my \n-- \n sig delimiter is always above that advisory in any event, so if the display stops there in that particular email agents display, then those instructions will never be seen by the user who is so handicapped. I can't tell folks not to use OE, but ISTR the last time I was forced to use it on somebody else's machine about 5 years ago, that was one of the agents that was busted in that regard. Whether it is today I have no clue. I only touch a windows box when under duress, like out on the job, or being plied with an endless supply of hand coolers. :-) Perhaps changing the mail server to look for the sig delimiter, and add those two lines into the relayed message so that they are above it? That can't be more than 10 lines of bash to do that. Probably much less if done by a truly competent bash script writer. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) A gleekzorp without a tornpee is like a quop without a fertsneet (sort of). --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
