ps Rhe reason I say there has been no status change is that there are no intervening entires “x is no longer bouncing.” Granted thst in itself could be a logging bug (I.e., the account did unbound but

#bug #fixed

John, I agree with you on the general principle of the log entry. But I think the problem is with the language of the entry. “X is bouncing” implies a change in status when there has been no change. S

#bug #fixed

Unless I am much mistaken (always possible!) the anomaly is that while the individual member's Email Delivery History appears to be correct the group - wide Activity log can show a contiguous list of

#bug #fixed

It is great that this has been set for a hard bounce. I hate going through the group one by one to inspect the mail history. I have to be honest, I'm still not clear on the anomaly you are referring t

#bug #fixed

Because the conditions back then for setting a member to "bouncing" were not satisfied. You need either a hard bounce, or at least one soft bounce within every consecutive four consecutive days after

#bug #fixed

I would just like to squeeze in some more data to this topic to show it is not just related to users with special-notice delivery, as well as other observations. For me, the bounce code seems to be wo

#bug #fixed

Exactly right. The bug (of multiple "is bouncing" log entries) pre-existed, but I only see it manifested now because of the fact that this special-notice member was finally noted as bouncing because o

#bug #fixed

Off - line activities completed (for now!) I have had a more detailed look and now think I have seen the anomalous Activity log entries mentioned; they only seem to arise for a very small number of bo

#bug #fixed

John, You are right. There's one 554 for the group guidelines, and three for bounce probes. So the log entries are not, as I formerly suspected, coming from other groups. They are coming from the boun

#bug #fixed

Yes Yes Exactly, and that's why this is showing up only now. The multiples are probably because it was the first of the month and group guidelines are sent out on that date, mostly as special notices,

#bug #fixed

Are these from Yahoo and does is say 554.30 This mailbox is disabled? Remember this bounce code from yahoo indicates that the yahoo account has not been used for at least 1 year. So any bounces previo

#bug #fixed

The group activity log. That’s where bouncing accounts are logged, even when they’ve bounced a messsge from another group. I’m thinking this bounce-handler bug is showing up now for the first time onl

#bug #fixed

I'm not currently aware of any "anomalies" but I'll have a closer look later; for the moment other off - line activities have to take precedence! In the meantime when you say "logged" do you mean in A

#bug #fixed

I wonder now whether the multiple log entries originated from other groups in which the member is *also* bouncing. The guidelines notice goes out on the 1st in every group every member is in. The syst

#bug #fixed

Actually I just checked and it's 554.

#bug #fixed

Chris noted the following: ""Our" Monthly Message goes out as a Special Notice on the 1st of every month and the outcome was that about 72 new bouncers have been listed. I haven't checked every one bu

#bug #fixed

Possibly. But coincidentally, (a) this has never happened in my group before; (b) the logging behavior occurred immediately after the bug fix; (c) the member is on special notices only; and (d) here w

#bug #fixed

I'd bet that none of them were 554 codes which is the one (#bug) described in this topic. My guess is that the first couple of bounces were either indeterminate hard bounces or soft bounces. That trig

#bug #fixed

It's the 4 log entries: Feb 1 at 5:30 a.m., 10:09 a.m., and 2:55 p.m., and today at 3:45 p.m. I'm expecting more tomorrow. :)

#bug #fixed

Not sure I understand. Did you not expect the person to be bouncing? Or was it the fact that there were 4 bouncing log entries? Thanks, Mark

#bug #fixed