Search the Archives

RFC 2505: I haven't seen reference to my application of SMTP, so I am...

Reader comments:

Comment by no buzz words
Submitted on 4/13/2004
Related RFC: RFC 2505
Rating:	Rate this comment:
I haven't seen reference to my application of SMTP, so I am asking.* World_server.mynet.com SHOULD accept all email destined for anyuser@mynet.com* World_server.mynet.com MUST then relay all email to internal_server.mynet.com* World_server .mynet.com SHOULD refuse any inbound email with the "from: anyuser@mynet.com" ( IMHO: since email should start at home, with VPN or the like )* Internal_server.mynet.com SHOULD only accept inbound email from world_server.mynet.com and anyhost.mynet.com.* Internal_server .mynet.com SHOULD NOT accept connections from world* Internal_server.mynet.com MAY relay email from anyhost.mynet.com ( pray they are nullhosts)* Both internal_server.mynet.com and world_server.mynet.com MUST only relay email from anyhost.mynet.com containing "from: anyuser@mynet.com". Does it not make sense to force mail through a world_server ( no user accounts ) that merely accepts and relays to a hidden internal internal_server ( with accounts ) to avoid visits from Rumplestiltskin?This kind of attack would require a valid return address, since world_server will accept everything and internal_server will deliver the bounce.Further to my modelDMZ ( demilitarized zone) problem: If user in DMZ forges an email address and send to forged@mynet.com, world_server should refuse any inbound email from *@mynet.com ( if not from internal_server.mynet.com ). Thus `yourboss@mynet.com` can not be generated from elsewhere.PS: My practical application is in a multi sub domain network with, what I would like to be, one set of world servers and many departmental server.Do you see flaw in my logic?

FAQS.ORG makes no guarantees as to the accuracy of the posts. Each post is the personal opinion of the poster. These posts are not intended to substitute for medical, tax, legal, investment, accounting, or other professional advice. FAQS.ORG does not endorse any opinion or any product or service mentioned mentioned in these posts.

<< Back to: RFC 2505