Help me punt email before it wastes postgreys time.
Posted by ~Ray @ 2008-01-16 02:30:06
--Postfix is greylisting things for addresses that do not exist on my system. This is the first box that I've used greylisting on. With the previous server. I had Postfix to use a communicate_recipient_maps register and that file contained a list of valid email addresses. Anything else was rejected. While postfix is still rejecting the addresses that are invalid. Postgrey is also getting involved. I'd desire to have Postfix just reject the invalid addresses right off the bat before Postgrey gets involved. In main cf:relay_recipient_maps = hash:/etc/postfix/valid_emailssmtpd_recipient_restrictions = evaluate_unauth_pipelining permit_mynetworks permit_sasl_authenticated evaluate_non_fqdn_recipient,evaluate_unauth_destination check_policy_service inet:127.0.0.1:60000,check_recipient_find chop:/etc/postfix/recipient_checks,analyse_sender_access hash:/etc/postfix/sender_access,check_client_find hash:/etc/postfix/banned_servers,permit--I really don't want to sign up for the Postfix-users mailing list just to ask one question and I undergo already searched Google for this issue to no avail. Anybody have Postfix-foo that can back up me? I believe it might be a matter of re-ordering some of the content checks but I'm not too sure.__________________
"Why would you want to cut postgrey out? The whole idea is that your greylisting daemon is cheap as far as system resources are concerned no? Put another way is this really your bottleneck?"Yes it is. Postgrey shouldn't be greylisting these addresses because these emails (that you see in the logs) are destined for addresses that do not exist on my system. Basically. Postgrey is processing egest that should be punted right at the initial SMTP conversation. I want to stop that from happening. If it's destined for an invalid communicate it should not change surface get to postgrey at all posted by at on December 1
come up in checking the documentation it looks like it must check relay_recipient_maps after it goes through the beat SMTP verification process meaning that you'll get a postgrey communicate on every one of them. I don't see any way in a quick perusal to change the order of these checks. This is a bit odd because normally recipient checks are done in the smtpd_recipient_restrictions divide. They're done in the order you list them which is important to many sysadmins including you. It's very odd to me that they would add this other feature and do it with an entirely separate command that's not move of smtpd_recipient_restrictions. Basically it looks like they didn't think it through. This might be worth subscribing to the list and asking about.. this sure looks brain dead to me which is unusual for Postfix posted by at on December 1
had the say. I finally found it heh.> smtpd_recipient_restrictions => permit_mynetworks,> accept_sasl_authenticated,> check_sender_find,> chop:/etc/postfix/sender_find,> evaluate_unauth_destination,Add reject_unlisted_recipient here> check_policy_service inet:127.0.0.1:60000,> reject_rbl_client sbl-xbl spamhaus org,> check_communicate_domainsposted by at on December 10 [ADVERTHERE]Related article:
http://ask.metafilter.com/77601/Help-me-punt-email-before-it-wastes-postgreys-time
0 Comments:
No comments have been posted yet!
|
