Re: Double messages problem

Hi Michael,

   Thank you for the explanation. This has solved the problem for us.

Thanks,
Alex

On Tue, 03 Nov 2009 06:07:01 -0800, Michael Yount wrote
> Alex,
> 
> Addresses that are probed due to the bounce_probe_pattern and 
> bounce_probe_frequency settings have a unique VERP (variable envelope 
> return path) during the SMTP conversation that identifies the message 
> number and the individual recipient of the message.  This sense of 
> "probe" has nothing to do with "probe" messages sent due to the 
> bounce_rules setting.
> 
> Michael
> 
> Alex Teslik wrote:
> > Hi Michael,
> >
> >     I've read the docs and still don't have a clear idea of what the bounce probes do/are. From
> > reading and re-reading all the probe documentation it seems like users who are flagged to be probed
> > receive a specially crafted message instead of the normal list message. If the message comes back,
> > then MJ knows that specific user is having a bounce problem. But I'm not clear on how that knowledge
> > will help, since I already know the messages are not bouncing to these duplicate recipients. I'm
> > also wary to send them more messages than they are already receiving.
> >
> >     Sorry for my confusion :/
> >
> > Thanks,
> > Alex
> >
> > On Thu, 29 Oct 2009 18:47:56 -0700, Michael Yount wrote
> >   
> >> Try using the "bounce_probe_pattern" setting to probe one or more of the 
> >> addresses in question, then check the sendmail logs to see if that 
> >> changes the outcome.
> >>
> >> For the subscribers in question, is every message being duplicated?
> >>
> >> Michael
> >>
> >> Alex Teslik wrote:
> >>     
> >>> Hello,
> >>>
> >>>    Subscribers have recently started complaining that they are receiving multiple messages
from the
> >>> mailing list, even though a check reveals that they are only subscribed once and have the same
> >>> subscriber settings as everyone else.
> >>>    
> >>>    Logs reveal that indeed some messages get sent to some subscribers twice - different SMTP ids,
> >>> but same MJ message id.
> >>>
> >>>    I suspect something in MJ2 has become tripped up. Any suggestions or regular maintenence
routine
> >>> that I may be missing that might fix this issue?
> >>>
> >>> Thanks,
> >>> Alex
> >>>
> >>>
> >>>       
> >
> >
> >