best practice for blocking fake local domain senders

anges. I have a few ideas on how to do this but but wondered if anybody could quickly point me in the direction of best practices for this. Is there a simple way or is it best to use smtpd_restriction_classes? thanks -- John Baker Network Administrator Marlboro College Phone: 451-7551 Cell: 490-0066

gmail headaches

stfix setting with this for years and it all seems to be with google. alt1 and al2 servers. Just wondering if there is anything I can do to mitigate it or if the problem is them. -- John Baker Network Administrator Marlboro College Phone: 451-7551 Cell: 490-0066

mini-mailbomb service problems

olicy Rejection- Abuse. Go away. In: QUIT Out: 221 2.0.0 Bye I'm also getting a bunch that just time out and have to resend. Is there anything I can do to alleviate the load on my ldap server? It's coming from so many IP's it's not going to do any good to just start firewalli

ldap calls for sender_access/recipient?

documentation appears to be just for rewrites. -- John Baker Network Administrator Marlboro College Phone: 451-7551 Cell: 490-0066

bypassing alias lookups when from another local smtp

mail servers since it will already have been done there. Is there a way to do this? -- John Baker Network Administrator Marlboro College Phone: 451-7551 Cell: 490-0066

alleviating Temporary lookup failures

r_host and switched from names to ip's in the definition just in case dns was causing it. The problem seemed to get less frequent after that but didn't go away. Would anybody have any suggestions for further diagnosing and solving this problem? Thanks -- John Baker Network Administra

best practices for "received from" header removal?

our server from authenticated users because their ISP's ip range shows up somewhere in the headers. So what is the best practice in postfix for removing headers before they relay back out into Internet? -- John Baker Network Administrator Marlboro College Phone: 451-7551 Cell: 451-6748

Re: ldap transport lookups: any holes in my solution?

On 04/25/2011 10:59 AM, Victor Duchovni wrote: On Thu, Apr 21, 2011 at 02:59:27PM -0400, John Baker wrote: There are several ways to make this work right including virtual aliases but the cleanest way seemed to me to be a per user transport map lookups for cloud users. I think that per-user

ldap transport lookups: any holes in my solution?

le and uses an ldap attribute that can be multipurpose and the same for every cloud user or mail server. But as this seemed like an unintended use of result_format I wanted to be sure that it won't cause any side effects before I put it into production. Could it cause any unexpected behavior

Re: "legacy" SSL and postfix smtp

it? Noel Jones wrote: John Baker wrote: We have a few people using programs (mostly MS crap) that insist on older versions of SSL rather than tls. Internally this works okay but externally ssl gets bounced by my grey listing. This seems to indicate that it is not actually authenticating right bu

"legacy" SSL and postfix smtp

, reject_unlisted_recipient check_policy_service inet:127.0.0.1:10031 permit smtpd_data_restrictions = reject_unauth_pipelining, permit -- John Baker Network Systems Administrator Marlboro College Phone: 451-7551 off campus; 551 on campus

Why is this hostname failing?

mail.cwf.org returns a valid result from a dns check. What am I missing here? -- John Baker Network Systems Administrator Marlboro College Phone: 451-7551 off campus; 551 on campus