On a private PlusNet account, I have suddenly received 11 quarantine notifications all into the catchall account. All are addresed to different (madeup) names. I haven't had any notifications into this account for ages, thinking about it I haven't had any in our business accounts for a while either.

Looks like something has be changed in the Quarantine system. Is this related to this thread http://community.plus.net...ex.php/topic,73171.0.html

Wow, someones done something! Now up to 70+ in my home catchall, and also getting notifications for my business accounts as well (not just the catchall)

What happened?

http://community.plus.net....msg615351.html#msg615351

Jelv,

I've seen the other thread, but my question is mainly about the catchall account. AFAIK the catchall has previously only sent a single quarantine message for all the various addresses (see the thread linked from the first post). It seems this has suddenly been changed to send one for each address. Had our business account still had this enabled, I estimte we would have received several thousand quarantine notifications (which in itself could be regarded as SPAM!)

I've just checked the notifications I've received and would concur with your observations. I have multiple emails, each for a single address; previously I'm sure they would have all been in the same email with all the addresses in that horrible URL link to the quarantine server.

could be something to do with this http://usertools.plus.net...us/archive/1243008823.htm maintenence to fix a fault next Tues

Looks like I'm not the only one to have a problem with this (http://community.plus.net...ex.php/topic,76668.0.html)

No posts from PlusNet staff in eather thread, any chance someone can explain what they are going to do about this? They have gone from a position where Quarantine is unusable on catchall accounts to .... Quarantine is unusable on catchall accounts. Progress, I think not?

Would http://community.plus.net....msg616066.html#msg616066 work for you?

HI guys,

We've had a problem open on this for a few days now (ref: 57120). We're hoping to roll out a fix at some point on Monday. I'll give you a shout once this has been done...

Edit: the fix has since been rolled out.