So Pierre, why the hell are you posting twice? OOF. Bad joke, sorry! I'm sure everyone here greatly appreciates and *needs* your troubleshooting: we're suffering from some serious schizophrenia. A concensus might be that anyone posting from M$ Lookout! should be banned for life (at least). I was wondering what sort of delays people are getting in their posts. I'm in Montreal and, although I've only joined the list since the rather disastrous weather hit, my posts don't come back to me for 1 - 3 hours! I've become accustomed to 30 sec - 1 minute on other lists. Dave. On 19-Dec-2000 Pierre Fortin wrote: > I have analyzed just over 250 messages from Cooker and Expert lists. Of > those, > there were 20 duplicated and 3 triplicated messages. > > NOTE: If you are receiving this message from both the list and > DIRECTLY, you > should investigate your mailer, settings and/or habits for one or more > of causes >#2 and up since you were discovered in this sampling as being a possible > contributor to the problems. > >>From my short sampling, these are the causes of message replication I >>came up > with... > > CAUSE 1: "user 500"@yavin.mandrax.org: You should correct your parsing > to > distinguish between "To:", "Envelope-To:" or any other "*-To:" (anchor > regex to > line start, or stop processing headers) so as not to create more copies. > Also, > is there any chance your parsing is triggering on any other headers...? > Note: "*-To:" was added to the list at the last moment because as I > wrote this > message, a duplicate (see 2b) arrived containing "Reply-To:" as the only > discernable clue to the duplication. > > > CAUSE 2a: sender is using M$ Outlook Express configured to send an > "Envelope-To:" header. This is possibly one of the causes of the > duplicates; if > so, removing this header might help. Alternatively, lower-casing the > "T" in > this header might be another solution, if that's possible. The correct > solution > is most likely in Cause 1. Not every user of M$ Outlook Express sends > this > header, so it must be configurable. > > > CAUSE 2b: sender is using "Internet Mail Service (5.5.2650.21)" with a > "Reply-To:" header. See cause 2a for solution. > > > CAUSE 3a: sending to more than one addressee. > Examples: > To: [EMAIL PROTECTED], <self>, [EMAIL PROTECTED] > To: [EMAIL PROTECTED], <self>, [EMAIL PROTECTED] > > > CAUSE 3b: sending to both "To:" and "Cc:" > Example: > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > > CAUSE 3c: sending with BCC: which is not detectable from the messages > we get. > > > PLEASE, PLEASE, PRETTY PLEASE.... make the necessary corrections to > whatever > piece you control so that we can all maximize our enjoyment of these > lists. > > Hoping this makes a difference, > Pierre > > PS to yavin owner: any chance the above causes 2a-3c can also be > accounted for > in your "user 500" code...? >
Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
