Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I have a Postfix instance using SASL with Dovecot for authentication. I am using virtual_alias_maps for some address rewriting, but I'm unable to use a catch all definition (@domain newaddress) as Postfix matches that before doing any sort of authentication with Dovecot.

Dovecot and Postfix are using my AD server as a backend for users/groups/etc.

I've been through all of the relevant Postfix documentation for virtual aliases, maps, etc. and I can't figure this out. Does anyone know how I can implement a catch-all address for emails sent to my domain for which I don't have an account/group in AD for Dovecot to match against?

EDIT:

CONFIGURATION EXCERPTS:

proxy_read_maps = $local_recipient_maps, $mydestination, $virtual_alias_maps, $virtual_mailbox_maps, $virtual_mailbox_domains, $relay_recipient_maps, $relay_domains, $canonical_maps, $sender_canonical_maps, $recipient_canonical_maps, $relocated_maps, $transport_maps, $my networks, $virtual_sender_maps, $admins_only, $protected_destinations
virtual_mailbox_maps = proxy:ldap:/etc/postfix/ad_virtual_mailbox_maps.cf
virtual_sender_maps = proxy:ldap:/etc/postfix/ad_sender_login_maps.cf
virtual_alias_maps = proxy:ldap:/etc/postfix/ad_virtual_group_maps.cf,hash:/etc/postfix/virtual

#SASL Stuff
smtpd_sasl_type = dovecot
smtpd_sasl_path = private/auth
smtpd_sasl_auth_enable = yes
smtpd_sasl_security_options = noanonymous
smtpd_sasl_local_domain = DOMAIN.COM
smtpd_client_restrictions = permit_mynetworks,permit
smtpd_recipient_restrictions = check_recipient_access $protected_destinations permit_mynetworks permit_auth_destination permit_sasl_authenticated reject_unauth_destination
smtpd_sender_login_maps = $virtual_sender_maps

I guess what I want to know, is there either 1) an accepted way of doing this, or 2) a way to change the order in which postfix checks the maps?

share|improve this question
    
(1) What is the error or problem you seeing with the method you use? (2) Can you post some related configuration? –  John Siu Jan 11 '13 at 18:22
    
No errors, the problem is that as soon as postfix hits the @domain entry in the virtual_alias_maps file, it rewrites the address. I need that match to happen AFTER it checks to see if its a user in the system. Basically, the rule ends up matching all addresses whether they exist as users or not and I need it to not do that. –  Matt Jan 11 '13 at 21:09
    
Oh, well, catchall is actually what you are seeing and working correctly then. You need something similar but with condition, properly a custom rules. –  John Siu Jan 11 '13 at 21:19

1 Answer 1

1) An acceptable way to implement a spam-catcher: there isn't one.

Accepting spam (with the large likelihood that it will later be bounced and hence make you a backscatter producer) is not acceptable, period.
Instead, configure your system to accept the right messages only, by using valid recipient lists, such as those you have in LDAP.

If you absolutely must accept invalid recipients, make sure you never bounce anything sent to invalid addresses.
The onus is on you to make sure no backscatter spam gets out; additionally, this may cause your system to be blacklisted and hence curtail your ability to send mail at all.

2) Changing the order postfix processes maps: no, this is not possible, since each map has a specific (and different) purpose.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.