Setting up a bunch of test mailboxes is not an option; i test an application that requires unique email addresses for users. A typical test involves uploading tens of thousands of test users.
Now, if i’m running email launch tests, i uses email addresses that ultimately send the mail to dev/null on our own internal system. But if i need to test a user-interaction with our application, i need a box that will actually receive system-generated emails (and be external to my own system, hence a dreamhost-ed site), and i need fresh email addresses because i need fresh test users.
So the very best solution for me is a catch-all mailbox for my test domain “foo.com” such that every email sent to that domain goes into one bucket, so i can use a pop reader to quickly count recieved emails and to read as needed.
I can’t do that because of freakin’ spam.
So the next best thing is a mechanism that allows me to 1.) verify that incoming mail is valid and b.) put that email into a single bucket. Now, the complexifying factor here is that i have several testers, so i need to use several buckets based on the tester, because i want the test mail kept seperate.
It looks like procmail is the solution, since it supports regexing on the address. thanks for that suggestion.
So my questions now are:
a. will this work with filtering; apparently i can’t use the admin UI to add filters, but i should be able to hook up spamassassin via procmail, right?
b. with the scenario i have described, does it make more sense to apply spamassassin before or after i run my bucket-izing calls?