Post by thread:[OT]: with 2 leading spaces. A test for OE users.

If this appears on the [OT]: forum with extra whitespace, then OE users simple need to add a blank in front of a tag when initially posting. If NO extra whitespace between [PICLIST] and [OT]: then they'll have to add it when replying to keep the [tag]: from being eaten by an OE feature (see earlier post on tag problem). http://support.microsoft.com/default.aspx?scid=kb;en-us;245199 I'm hoping the former works, and we don't have to do -anything- to the PICLIST to accommodate this OE 'feature'. Robert -- http://www.piclist.com hint: PICList Posts must start with ONE topic: [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads

The only way extra spaces would work is if everybody used them. If only OE users added a leading space, then whenever responding to posts by users of other mail clients, the tag will still be removed. Anyway, I didn't see any leading spaces in the copy of the mail I got, either in OE's display or looking at the headers. One way to fix the problem without placing an undue burden on users of other clients and without changing the listserv's behavior is to have OE users add the tag back in after "Re:." There are two problems with this though. First, people can easily forget to put the tag back in. The second one is more easily solved, and that is that people new to the list probably won't know about OE's abnormal subject handling. Of course, a few lines of text on the PIClist website can fix this second problem. A better way is to send a command to the listserv so that it will prepend [PICLIST] to all the posts you receive. Someone mentioned this earlier. For those who don't know how to do this, send SET PICLIST SUBJECTHDR in the body of an email to spam_OUTlistservTakeThisOuTmitvma.mit.edu. According to the PICLIST welcome email, the listserv should filter [PICLIST] out in replies for people who don't have this setting enabled, thus allowing everything to work as it should. Daniel Imfeld {Original Message removed}

I am a member of some other groups too, and they have [listname] too. But, this does not get eaten??? Only Piclist tags ? Some piclist tags don't get eaten either... There must be something in the header of the messages. This one get's eaten: ----------------------------- MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-ID: <002001c2d52c$fc951060$b64aa40a@a7m7h6> Date: Sat, 15 Feb 2003 16:01:10 -0400 Subject: [EE]: Inverter DC-AC ----------------------------- This one don't: ----------------------------- MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <.....20030216021150.48196.qmailKILLspam@spam@web40016.mail.yahoo.com>> Date: Sat, 15 Feb 2003 18:11:50 -0800 Subject: [PIC]: making certain pins inputs and outputs on portb in hitech c ----------------------------- I cut out all the address info at start, and other fields that were 100% equal. The problem must be content type or something. This don't get eaten either, and it's from another list: ----------------------------- X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 MIME-Version: 1.0 Date: Mon, 10 Feb 2003 15:15:41 +0100 Subject: [flaskmpeg] 30 day Content-Type: multipart/alternative; boundary="----=_NextPart_000_0027_01C2D117.4688D220" ----------------------------- Something is afoot in the MS world... KreAture {Original Message removed}

It's just the 2 letter tags. OE removes up to 4 letters and the colon, so [EE] and [OT] are removed, while [PIC] has 5 characters, so it isn't removed. Daniel Imfeld {Original Message removed}

It removes the [PICLIST] tag too, doesn't it ? This is wierd. KreAture ----- Original Message ----- From: "Daniel Imfeld" <dimfeldKILLspamSOFTHOME.NET> To: <.....PICLISTKILLspam.....MITVMA.MIT.EDU> Sent: Sunday, February 16, 2003 9:17 AM Subject: Re: [OT]: with 2 leading spaces. A test for OE users. {Quote hidden}> It's just the 2 letter tags. OE removes up to 4 letters and the colon, > so [EE] and [OT] are removed, while [PIC] has 5 characters, so it isn't > removed. > > Daniel Imfeld > > ----- Original Message ----- > From: "Kyrre Aalerud" <EraseMEkreaturespam_OUTTakeThisOuTC2I.NET> > To: <PICLISTspam_OUTMITVMA.MIT.EDU> > Sent: Saturday, February 15, 2003 10:37 PM > Subject: Re: [PICLIST] [OT]: with 2 leading spaces. A test for OE users. > > > > I am a member of some other groups too, and they have [listname] too. > But, > > this does not get eaten??? Only Piclist tags ? > > Some piclist tags don't get eaten either... There must be something > in the > > header of the messages. > > > > This one get's eaten: > > ----------------------------- > > MIME-Version: 1.0 > > X-Priority: 3 > > X-MSMail-Priority: Normal > > X-Mailer: Microsoft Outlook Express 5.50.4807.1700 > > X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 > > Content-Type: text/plain; charset="iso-8859-1" > > Content-Transfer-Encoding: quoted-printable > > Message-ID: <002001c2d52c$fc951060$b64aa40a@a7m7h6> > > Date: Sat, 15 Feb 2003 16:01:10 -0400 > > Subject: [EE]: Inverter DC-AC > > ----------------------------- > > > > This one don't: > > ----------------------------- > > MIME-Version: 1.0 > > Content-Type: text/plain; charset=us-ascii > > Message-ID: <@spam@20030216021150.48196.qmailKILLspamweb40016.mail.yahoo.com>> > > Date: Sat, 15 Feb 2003 18:11:50 -0800 > > Subject: [PIC]: making certain pins inputs and outputs on portb in > hitech c > > ----------------------------- > > > > I cut out all the address info at start, and other fields that were > 100% > > equal. > > The problem must be content type or something. > > > > This don't get eaten either, and it's from another list: > > ----------------------------- > > X-Priority: 3 > > X-MSMail-Priority: Normal > > X-Mailer: Microsoft Outlook Express 6.00.2600.0000 > > X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 > > MIME-Version: 1.0 > > Date: Mon, 10 Feb 2003 15:15:41 +0100 > > Subject: [flaskmpeg] 30 day > > Content-Type: multipart/alternative; > > boundary="----=_NextPart_000_0027_01C2D117.4688D220" > > ----------------------------- > > > > > > Something is afoot in the MS world... > > > > KreAture > > > > > > ----- Original Message ----- > > From: "Daniel Imfeld" <KILLspamdimfeldKILLspamSOFTHOME.NET> > > To: <RemoveMEPICLISTTakeThisOuTMITVMA.MIT.EDU> > > Sent: Sunday, February 16, 2003 7:10 AM > > Subject: Re: [OT]: with 2 leading spaces. A test for OE users. > > > > > > > The only way extra spaces would work is if everybody used them. If > only > > > OE users added a leading space, then whenever responding to posts by > > > users of other mail clients, the tag will still be removed. Anyway, > I > > > didn't see any leading spaces in the copy of the mail I got, either > in > > > OE's display or looking at the headers. > > > > > > One way to fix the problem without placing an undue burden on users > of > > > other clients and without changing the listserv's behavior is to > have OE > > > users add the tag back in after "Re:." There are two problems with > this > > > though. First, people can easily forget to put the tag back in. > The > > > second one is more easily solved, and that is that people new to the > > > list probably won't know about OE's abnormal subject handling. Of > > > course, a few lines of text on the PIClist website can fix this > second > > > problem. > > > > > > A better way is to send a command to the listserv so that it will > > > prepend [PICLIST] to all the posts you receive. Someone mentioned > this > > > earlier. For those who don't know how to do this, send SET PICLIST > > > SUBJECTHDR in the body of an email to spamBeGonelistservspamBeGonemitvma.mit.edu. > > > According to the PICLIST welcome email, the listserv should filter > > > [PICLIST] out in replies for people who don't have this setting > enabled, > > > thus allowing everything to work as it should. > > > > > > Daniel Imfeld > > > > > > ----- Original Message ----- > > > From: "Robert Rolf" <TakeThisOuTRobert.RolfEraseMEspam_OUTUALBERTA.CA> > > > To: <RemoveMEPICLISTTakeThisOuTMITVMA.MIT.EDU> > > > Sent: Saturday, February 15, 2003 9:04 PM > > > Subject: [OT]: with 2 leading spaces. A test for OE users. > > > > > > > > > > If this appears on the [OT]: forum with extra whitespace, then OE > > > > users simple need to add a blank in front of a tag when initially > > > posting. > > > > If NO extra whitespace between [PICLIST] and [OT]: then they'll > > > > have to add it when replying to keep the [tag]: from being eaten > > > > by an OE feature (see earlier post on tag problem). > > > > > > > > support.microsoft.com/default.aspx?scid=kb;en-us;245199 > > > > > > > > I'm hoping the former works, and we don't have to do -anything- to > > > > the PICLIST to accommodate this OE 'feature'. > > > > > > > > Robert > > > > > > > > -- > > > > http://www.piclist.com hint: PICList Posts must start with ONE > topic: > > > > [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other > [BUY]:,[AD]: ->Ads > > > > > > -- > > > http://www.piclist.com hint: PICList Posts must start with ONE > topic: > > > [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other > [BUY]:,[AD]: ->Ads > > > > -- > > http://www.piclist.com hint: PICList Posts must start with ONE topic: > > [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads > > -- > http://www.piclist.com hint: PICList Posts must start with ONE topic: > [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads -- http://www.piclist.com hint: PICList Posts must start with ONE topic: [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads

Not on my computer. It sees that [PICLIST][EE], for example, is 13 characters so it leaves the subject line intact when replying. I'm running OE 6.00.2800.1106 (why does MS use such long version numbers?). The listserv will remove [PICLIST] from any messsages that go to people who don't have the option on, but that's supposed to happen. Likewise, it inserts the tag for people with the option on. I'll test it again next time someone posts a new OT or EE post though, just to make sure. {Original Message removed}

> -----Original Message----- > From: Robert Rolf [SMTP:Robert.RolfEraseME.....UALBERTA.CA] > Sent: Sunday, February 16, 2003 5:05 AM > To: EraseMEPICLISTMITVMA.MIT.EDU > Subject: [OT]: with 2 leading spaces. A test for OE users. > > If this appears on the [OT]: forum with extra whitespace, then OE > users simple need to add a blank in front of a tag when initially posting. > If NO extra whitespace between [PICLIST] and [OT]: then they'll > have to add it when replying to keep the [tag]: from being eaten > by an OE feature (see earlier post on tag problem). > > http://support.microsoft.com/default.aspx?scid=kb;en-us;245199 > > I'm hoping the former works, and we don't have to do -anything- to > the PICLIST to accommodate this OE 'feature'. > > Robert > This seems like extreme laziness on the behalf of whoever added this "feature". If the idea is to stop a large number of 're:' or 'fw:' being added to the subject, then why not ensure that these characters actualy match the start of the subject line before removing them, rather than just looking for a ':' ? This iso obvious there must be a reason why they didn't do it. Mike -- http://www.piclist.com hint: The list server can filter out subtopics (like ads or off topics) for you. See http://www.piclist.com/#topics