View Single Post
  #5  
Old 25th August 2009, 03:09
MrM MrM is offline
Member
 
Join Date: Oct 2008
Location: Ljubljana, Slovenia
Posts: 58
Thanks: 6
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by bajodel View Post
Take a look at postfix restrictions parameters .. expecially at "reject_unknown_recipient_domain"

Requirements: the dns (mx or a) records of that provider domain must no longer exist.
In this case, the MX record still exists, but the SMTP server is no longer responding, so I guess this option will not help.

The provider in question is actually email.si:
Code:
$ dig email.si IN MX
...
;; ANSWER SECTION:
email.si.		3421	IN	MX	20 mx5.email.si.


$ telnet mx5.email.si 25
Trying 81.24.97.24...
telnet: Unable to connect to remote host: Connection timed out
Quote:
Originally Posted by bajodel View Post
If it suits your needs you will able ( modding your /etc/postfix/main.cf ) to do the trick in a better way ..you can avoid to receive the entire messages before dropping them (blocking them at smtp first dialog level) .. saving bandwith :-)
Heh, bandwidth actually isn't a problem in this case, since the postfix server is only being used by the websites running on the same server. I was only hoping to get rid of the log entries and bounced messages, but as I said before, it's just a minor annoyance, not a serious issue. The bulk of the problem has already been solved with till's suggestion.
Reply With Quote