Well, I’m not sure what I did but I definitely can’t seem to get it back. Basically I was fooling with Exchange 2003 the other day trying to migrate my one NNTP group from the old IIS file system store to Exchange’s Public Folder store. Tried and failed at that, with the only semi suggestion from a MVP that I:

“Setup another Exchange box, pull the newsgroups into PFs on it, create a replica on the one you intend to use, turn off the FS based NNTP, turn on Exchange, break replica, remove temp server from organization. That’s what I’d do, at least.”

Sure I could do this since I’ve already got Exchange setup on a VPC but that seems like such a hassle. At any rate, I started messing with something else. I ended up getting it set up so that NewsGator would store my feeds on the server that way I could read them and such through OWA and maintain the state of them across the laptop and desktop. Quite cool really.

At this point I’m not sure what I did, I think I looked at and applied the Default Recipient Policy (Exchange System Manager – Recipients – Recipient Policies). I remember adding the removing the other property page as well as applying the default policy again. Other than that I honestly can’t remember doing anything else. I’m using a really awesome tool that Dominic wrote that allows me to just edit a nice little XML file and magically have catch-alls, forwards, and the like in Exchange (something I needed to have from MDaemon).

Anyway ever since that day I’ve been getting mail delivered to my account catch-all with a To line of PUBLIC FOLDER STORE (SERVER NAME). It’s really pissing me off since I’ve no idea how to undo whatever I did. I’m also trying to figure out how I allow myself to email one of the catch-all aliases that Dom’s tool handles from my cgouker@ account. So for example, email corey@ from cgouker@. Right now Exchange doesn’t like that, I get a lovely “The message reached the recipient’s e-mail system, but delivery was refused.  Attempt to resend the message.  If it still fails, contact your system administrator. <element.auroravisions.com #5.2.1>”. If anyone has any ideas on these 3 issues please comment!