Rusty, Since you have the most complete set of questions... :^) Rusty Carruth wrote: > > Pierre Fortin <[EMAIL PROTECTED]> wrote: > > I have analyzed just over 250 messages from Cooker and Expert lists. Of those, > > there were 20 duplicated and 3 triplicated messages. > > I'm impressed! I quit after 2 or 4 ;-) I just finally got tired to seeing all the "why am I getting duplicates...?" posts; asking the same question over and over does not solve the problem... you gotta dig deep[er]... :> > > From my short sampling, these are the causes of message replication I came up > > with... > > Did you happen to attach a count to each of these causes? That might be very > enlightening. I didn't feel the count mattered 'cuz a computer can make the same mistake forever without complaining; fix the cause and it'll behave regardless of counts... > > CAUSE 1: "user 500"@yavin.mandrax.org: > > I am of the opinion that user 500 is the 'expert list' expander/forwarder/whatever_ > you_want_to_call_it. Yes; just pointing out that it was at the core of the issues. > > CAUSE 2a: sender is using M$ Outlook Express configured to send an > > "Envelope-To:" header. ... > > > > CAUSE 2b: sender is using "Internet Mail Service (5.5.2650.21)" with a > > "Reply-To:" header. See cause 2a for solution. > > But aren't these just triggers to the problem in user 500? Unless I've > missed something, it seems that the right solution is to fix whatever > user 500 is doing... Correct; though if we can reduce the problems in the meantime... However, the following ones require a smarter set of rules... > > CAUSE 3a: sending to more than one addressee. > > Examples: > > To: [EMAIL PROTECTED], <self>, [EMAIL PROTECTED] > > To: [EMAIL PROTECTED], <self>, [EMAIL PROTECTED] > > So expert@mandrax == [EMAIL PROTECTED], eh? Wow, learn something > new every day ;-) Does the '<self>' entry seem to have anything to do > with it? <self> was just to indicate that the sender was mailing a copy back to themselves to push a copy of their posts through their filters for filing. > > CAUSE 3b: sending to both "To:" and "Cc:" This is where my post got caught... though in my case, I sent: To: cooker... Cc: expert... Which means that when you think you are cross-posting, the list server simply sends both copies to the "To:" list; I missed this variation in my original post. > > CAUSE 3c: sending with BCC: which is not detectable from the messages we get. > > Actually, I have another theory. [snip] > Perhaps, in bad weather, the number of errors increases and we start > getting disconnects AFTER the email has actually been queued on the > remote machine, but the list sender thinks not. > > Just a wild stab in the dark (OUCH!). This *might* explain those that had no apparent reason for replication... :? > Finally - I'd be willing to set up a userid (on my home machine, [snip] I'd be surprised if we need to go there... I've gotten a response from Denis, the maintainer of the rules and have already replied to him... Hopefully we can get to the bottom of this RSN (real soon now)... Pierre > (yikes, I may have to buy a new hard drive to hold it all!, and I'm sure > my 44k dialin will get overloaded - oh, well, its all for the cause ;-) > (and I hope we won't need it for TOO long, also!) > > rusty > > Rusty Carruth Email: [EMAIL PROTECTED] or [EMAIL PROTECTED] > Voice: (480) 345-3621 SnailMail: Schlumberger ATE > FAX: (480) 345-8793 7855 S. River Parkway, Suite 116 > Ham: N7IKQ @ 146.82+,pl 162.2 Tempe, AZ 85284-1825
Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
