Messaging Gateway

HI

I can't use IP based blacklisting lists because of the following from this post of mine.

Symantec recommends that the SMG be installed on the gateway before all other MTAs and people at my work place decided to go aganist that for some reason.

As a result we are always under spam fire.

I am considering using third party RBLs now for further blocking SPAM right at the gateway, and needed an explanation as to whether the SMG deployed after the MTA would still be able to detect the incoming blacklisted IP address.

As of now the message audit logs shows that all our email comes from just 2-3 IPs which are the IPs belonging to our SMTP providers IP.

If I cannot use IP based RBLs then is there anyway on the SMG to use domain based DNSBLs? Which will check the incoming doman name and not the SMTP connection IP.

Because the domain name check is still done after the incoming SMTP connection has been accepted as per my understanding, so will this work?

Hi,

As i know smg only checks dnsbl only against the connecting ip and not the ips within the "received" headers.

Only a few products and dnsbl give you the possibility to activate this feature, eg spamhaus tells you not to use it - https://www.spamhaus.org/zen

DNSBL (or RBL, same just other name) is based on ips. By activating dnsbl your server askes a dns service for an ip. There's an ip behind a domain, too. So no difference ...

What do you mean by "Because the domain name check is still done after ..."?

You dont have the possibility to activate dnsbl there. Or did i just missed something?

Sorry, but (from my prospective) you have to think about the architecture or adding dnsbl at the first tier.

Thomas