On 1/13/2010 8:33 AM, Alexandru Florescu wrote: > > Hello everybody. > > I have a issue with postfix. > > Consider the following scenario: > > I telnet to my web server from *another location (bar.com)* and I > start executing commands. > > Connected to */foo.com/.* > > Escape character is '^]'. > > 220 smtp1.foo.com ESMTP Postfix (GNU/Linux) > > *HELO /bar.com/* > > 250 smtp1.foo.com > > *MAIL FROM:/ [email protected] <mailto:[email protected]>/* (mail must > be valid) > > 250 2.1.0 Ok > > *RCPT TO: [email protected] <mailto:[email protected]>* > > > Notes: > > In this scenario, _foo.com_ is my “real” mail server, _bar.com_ is my > “real” testing server, [email protected] <mailto:[email protected]>_ > is an example of an “existing” and valid mail account and > [email protected] <mailto:[email protected]>_ is my “real” mail address. > > > Is some option missing? What can I do to prevent this? I found it > because I received spam in this way. > > Using postfix 2.3.3 on Centos 5.4. > >
Unless you wish to stop getting all email from the wild internet, Postfix is doing just what it is supposed to do. Various MTAs in the world will not know how to bypass any security you set to deliver mail to you. This scenario is a really job for a policy service, such as policyd or policyd-weight, and/or spamassassin, via milter or amavis or other content filter mechanism. The policy services can score and accept or reject based on criteria such as matching sender domain to IP records then comparing to the connected IP. Spamassassin can be tuned to quarantine mail or do what ever you like with it.
