Thanks and everyone for the contribution. I could block traffic via firewall on those unused at the moment but can this cause bad scoring (eg.: if a recipient's MTA check alternative smtp's)?ĭoes anybody advice potential problems? or do you know better alternatives? What strategies have you put in place in the event of blacklisting? 17 POST-INSTALLATION TASKS DNS Configuration After installing hmailserver, make sure you configure your DNS server correctly. The downside is that I have to expose the server to 4 ip's. For what it is worth, I get debug logging saying DNS Query failure for each of the Blacklist lookups too, if there is no match. one month it seems to be that SPAM are no more proper detected as bevore and also I see no more entries from DNS blacklist score in the logfile, in hmail status screen there are 0 SPAM messages registered. This way, if I switch from ip1 to ip2, all domains will be aligned with MX and SPF (think that DMARC and DKIM are not affected if i change hostname & IP in hmailserver). Since now I'm used to see DNS Blacklist score in the logfile, but since aprox. In case of IP1 blacklisting I can quickly swap hostname and IP in hmailserver.Įvery domain sending emails through hmailserver are configured like this: IP1: DNS A / reverse to IP1 (currently used as hostname in hmailserver / IP1 bind in hmailserver) DNS Blacklist Grey Listing Relay And many other settings and features. Re: Spam DNS Blacklists seem to have stopped working. Just in case, my hmailserver version is 5.6.4-B2283 under Windows Server 2008 R2 (64bit) & MySQL 5.16.15 (64bit) Top. However i am trying to configure the dns blacklist but i cant seem to find what the individual lists will reply with if the mail is classed as spam. The DNS Blacklists are showing as TCPIP logging, as is the SURBL lookups. I have dedicated 4 static public IPs (they are all in different subnets because some blacklists can block the whole subnet) hMailServer comes with a set of built-in anti spam features such as SPF. Hello, i am new to hmail having used mailenable for around 2 years. So, it is better to be foresight and prepare everything. In these cases it is necessary to be ready and have "clean" IPs to use as an alternative until the main IP is delisted (and it could take a long time) Even implementing outbound limits, SSL / TLS, DKIM, DMARC, SPF etc. Automatic: 48 Hours after the last Attack. Automatic: over honeypots and with over 515 users and 630 servers from via Fail2Ban or own scripts. AntiSpam Edit Host based DNS Blacklisting (DNSBL) URL based DNS blacklisting (SURBL) Greylisting (must retry sending for the message to succeed) SPF Built. Getting on a blacklist is a problem that affects everyone who uses mailservers. IP addresses used to in attacks over SSH, IMAP, SMTP, FTP, or HTTP, or for attacks involving remote file inclusion, SQL injection, or DDOS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |