On Mon, Jun 20, 2016 at 07:52:24AM +0200, Voytek wrote: > I have a user who can not receive emails as his correspondent's > domain is currently on multiple rbls. > > As an interim measure, should I look at temporarily allowing this > domain?
I wouldn't. His correspondent is unable to reach a lot of other addresses on the Internet. Their problem is unlikely to be only with your site. But, business is business, and many times a competent site administrator has to work around another site's problems. That's between you and your boss/customer. > Or, is that a bad idea, shouldn't consider such temp workarounds? > > domain in question: > > ____________________________________ > > Checking ckchaiseree.com which resolves > to119.59.120.56 against 107 known blacklists... Listed 7 times. > > Blacklist Reason > LISTED CBL > 119.59.120.56 was listed > LISTED ivmSIP > 119.59.120.56 was listed > LISTED ivmSIP24 > 119.59.120.56 was listed > LISTED Protected Sky > 119.59.120.56 was listed > LISTED SORBS SPAM > 119.59.120.56 was listed > LISTED Spamhaus ZEN > 119.59.120.56 was listed > LISTED UCEPROTECTL2 > 119.59.120.56 was listed Some of these are responsible and safe lists. Personally I block based on Zen, but I'm also familiar with and think well of the Invaluement lists. It seems safe to say that 119.59.120.56 has a spam problem at this time. If you open up for 119.59.120.56 you might end up with a spam flood. Since you did flag the message as "ot", and you did not include configuration and logs, I presume you are not asking how to do your whitelisting. -- http://rob0.nodns4.us/ Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
