Antw: Re: From adress must match the smtp clients DNS domain
G.Rappenecker at hs-offenburg.de
Thu Jun 23 12:20:49 CEST 2016
In fact, its an unusual environment: In our university there are some hosts in our dmz managed by students and reachable from the internet for testing. I look at those hosts as "untrusted smtp clients" because sometimes they are compromised and try to deliver spam using my MTA. Instead of blocking all messages I'd like to permit administrative messages coming from some services like cron or www. Those messages have to use from adresses with the clients domain and are forwarded on my MTA only to the postfix mynetworks.
These policy should be used for all IPs in the dmz except some whitelisted IPs which should be handled in normal way. Is there any better idea to manage this?
>>> Gregory Sloop <gregs at sloop.net> schrieb am Mittwoch, 22. Juni 2016 um 16:48 in
Nachricht <218269559.20160622074832 at sloop.net>:
> GR> Hi Curtis,
> GR> thanks for your suggestion but it seems not to realize my idea. I'll try
> to describe it better:
> GR> When a smtp client with the IP address 220.127.116.11 and the DNS
> GR> hostname host1.mydomain delivers messages to my postfix/amavis MTA
> GR> with tcp/25, all the messages must have from-headers and
> GR> envelope-from-addresses of the form any_user at host1.mydomain. I
> GR> want to configure my MTA to apply this policy only to the IP 18.104.22.168 or
> the subnet 22.214.171.124/24
> GR> Is there any other advice?
> GR> Best regards
> GR> Gerhard Rappenecker
> You do realize that this will cause you a LOT of pain, unless your inbound
> mail is incredibly unusual, right?
> For example - the reverse on my VPS server is, say, mail.xyz.com. But I host
> mail for many domains - like abc.com, def.com ghi.com etc. [Not to mention,
> the mail server will likely identify as mail.xyz.com - but my mail will be
> from the 2nd level domain, xyz.com - and you'd block that too!]
> So, if you implement [at least what I think I understand] what you're trying
> to do you'll block all mail that isn't from xyz.com coming from my VPS, even
> though there could be many, many legitimate other domains.
> If you don't care about blocking mail in those conditions, or if you don't
> get mail from most of the real world, then I suppose what you want works. But
> I suspect that's not the case - and implementing your design will break email
> for your entire server. [And I'm not aware of any way any MTA would implement
> this "out-of-the-box" anyway.]
> What I think you want is more likely to be accomplished with SPF. SPF
> certainly isn't universally used, so it's of limited utility. But it's the
> closest workable concept to what you put forward above that's likely to not
> break/cripple your mail server.
> But to reiterate - what you've described above [at least how I read it] is so
> completely unworkable, if you accept mail from the rest of the world, it's
> simply going to block a vast amount of legitimate mail.
More information about the amavis-users