Upgrading from vqME to vqNOW and catchall addresses ** HELP

czyler · Joined: 26 Apr 2006 Posts: 69 Location: Shropshire, UK

It seems there was some confusion over terminology on my part. Catchall is simple the destination account one aliases to receive email that otherwise fails to match any accounts.

There is no "catchall" address by definition of course.

The ad hoc addresses I define do not have accounts associated with them therefore they will be caught by the catchall arrangements.

For my domain, as it is personal and not a business and hence all comes to me I have NO addresses defined at all and hence everything falls into the catchall trap.

This is now being setup on vqNOW.

Stuart

czyler · Joined: 26 Apr 2006 Posts: 69 Location: Shropshire, UK

All resolved now, I did not need to upgrade to vqNOW afterall although may well still do so at some point.

For some reason, my account was popping email from the source servers again even though all mail for my domains is forwarded to vqME.com. Perhaps one slipped through the net or on a recovery some time this was turned on again by accident. Also, there was one very odd profile address that I would not have created that was trying to pop from another profile address! Whatever the cause, it is all history...

The Vanquish team came through again and re-created my accounts from scratch, keep all lists (subects, allows, blocks, etc) and everything works well.

Obviously it would have been better if the problem could have been identified earlier but some things always mystify us even when they seem obvious with hindsight. No doubt the team has learnt something that will benefit others.

Thanks to the team.

Stuart

--VQ-- · Site Admin Joined: 06 Jan 2003 Posts: 590

Thanks for the updates, Stuart. Indeed, we learn a little each time we diagnose and correct a problem. Our senior engineer has just developed a tool to more rapidly determine if an account exhibits any of the oddities that were affecting your original account.

When we have a bit more time, we will be more proactive by implementing at least the first item below (To deal with legacy accounts, we may need to do both):

prevent a settings conflict at the time of configuration (entry parsing) - or at least...
create an agent that periodically sweeps through the user accounts looking for conflicts and illegal entries.

Finally, we are creating a tool that will inform us of any particular account that is suddenly using an unusual level of resources or alternatively has recently begun a dramatic increase in resource consumption. This will help us to quickly determine if a new problem is brewing - perhaps long before it becomes a problem for our customer.