I had my domain hosted with DirectNIC, and they forwarded all email unless it met some filter criterion of username or subject. In which case, it would be forwarded elsewhere or deleted. This worked well for years, but email is getting bad so I was keeping my eyes open for alternatives.

I recently switched my web hosting to , who handles mail through servers. LOTS more features here, but they don't always work the way I'd like.

For example, there is no way to apply the Spam Assassin score machine or the Box Trapper email verification system to non-specified usernames at my domain. After exchanging a few emails with tech support, it turns out the main email account is really an email accout in the domain one level up. They can change it's processing rules, but I cannot. For unrecognized emails inbound to the domain, all I can do is forward or delete them. Higher level functions work only on specifically created usernames. Ugghh...

My goal was to force people using any unknown username to reply to a verification email unless they are on my white list. My problem is that I have many domain email address out there (each different through the years so I could identify the source). I can't remember them all to create individual usernames. Even if I could, it would be dozens of email addresses I'd have to create and configure each for the extra mail handling services beyond "forward or dump".

One last idea... I'll forward all the unrecognized addresses to 345obscure-email3%$, and then do the "confirmation required" kickback from there. I wonder if that will work?

Created by admin. Last Modification: Thursday 23 of February, 2006 17:24:57 CST by brian.