The catchall (as I see it) is similar in nature to the alias problem I was talking about before.

I see both the alias & the catch all problems I am dealing with to be a limitation of spamfilter.

As you mention the catch all can be done with exchange (and most other email systems).  Any unknown address automatically would forward to a single specific mailbox.

The problem with putting spamfilter in front (and doing billing control with the allowed list) is it takes away the ability.  I know I can put *@domain.com in the allowed list and it would pass all email through, those who want the catchall could then process it on their server as you mention.

Problem is spamfilter does not have a way to re-write the recipient address so again someone can have 1000 email addresses, enable the catchall and they get past the billing system (allowed list).

Getting rid of the allowed list would also cause a massive amount of email to pass through our server to clients that should not be.  It is excellent to have both for billing and the ability to stop invalid addresses from passing through the server.

Then I run into the customers who want the catchall and I'm in a catch 22 not being able to offer it to those who want it.

I want to see if anyone has a work around or if anyone else has the same need as we do; it can't be that we are the only group with this requirement.

 

I understand whta you want is the following steps to apply.

1. Email comes in to spamfilter

2. Email recipient is checked against allowed receivers.

   2a. If passes recipient test then continue as normal

   2b. If fails recipient test then change the recipient to mailto:%7bcatchall@recipientdomain.com - {catchall@recipientdomain.com ] and process as normal. (also probably require subject, or body to be modified to note who the original recipient should have been.)

3. Process email as normal.

 

Currently there is no option to do this, and i dont know of any product that does have this.

 

Actually, what I want to do with the aliases and catch-all are very mainstream

among hosted solutions.  I can't believe more are not interested in the ability 

to have these things:

Google Apps - http://www.google.com/support/a/bin/answer.py?answer=33962 - Catch-all address

Google Apps - http://www.google.com/support/a/bin/answer.py?answer=33327 - Email aliases  

GFI MailProtection - http://kbase.gfi.com/showarticle.asp?id=KBID003750 - Email aliases  

Spam Hero - http://www.spamhero.com/support/78469/Should_I_turn_off_the_catch-all_feature.php - Catch-all address  

CudaMail - http://www.cudamail.com/Default.aspx - Domain aliases  

I am not a user of these other services, but doing a search reveals what we want to offer is being offered by others and based on the number of queries from customers we receive these features are wanted by the end users.

We never get requests for mail archiving or TLS support, but catch-all and aliases are requested often.

We are currently trying to come up with a solution so we can remain competitive with others in the market, despite spamfilter not offering these things.  One idea we have is to setup a Linux server, any customer who enables alias or catch-all will have their email routed to the Linux box after spamfilter processes and we can do it from there, but what a hassle.

Google Apps - http://www.google.com/support/a/bin/answer.py?answer=33962 -

I don't think there are many real enterprise systems using spamfilter, or this issue would come up more often.

Access the Theme Editor from the Administration > Appearance > Editor menu.

Click on the header.php file, make the changes and save.

this should work for you. If you have problems let me know.

This was a genuine mistake with posting to the wrong forum. 

I have been a paid user of spamfilter for over 6 years, and am disgusted that you think I post in order to get backlinks.

I was going to comment to you about the problem you described above, and kindly provide you with the scripts I wrote in order to resolve it in the quarantine area.

I guess I won't be providing you with the scripts.

The solution is very simple

in your quarantine area (whatever scripts you use to access it) you need to create an alias for the user that logs in. your SQL query will then pick up all the spam for that users and it's aliases.

As far as I am aware SpamFilter was designed to be as seemless as possible to the mail process (Roberto can correct me if that has changed). So the less mail logic there is in SF the better it is. What you're requesting above is a mail server feature, which will most likely make SF more cumbersome.

Now, if you want to know anything about virtual offices, feel free to ask me!