Facebook
TwitterHello,
all in all greylisting sounds like a good antispam protection. it get's rid of a huge amount of spam with very little server resources...
however, there are several problems I would like to know if parallels is going to address or anyone could help.
1) lack of control GUI. greylisting customization has either to be done via shell or 3rd party product (GLM2 from haggybear.de). Is parallels going to make a GUI for this?
2) since i am on 11.5.30 (currently MU16) i think there might be a problem with greylisting rejecting emails with a 5.7.1 error instead the suposed to be temporal 4xx error.
I vaguely remember that I manually fixed that a couple of years ago on my old plesk 9.5.4 server, but I can't find any notes about it. Does this sound familiar to anyone?
3) multiple subnet MX senders. if a sender tries first with 200.x.x.x and the second try comes from 199.x.x.x the mail usually ends up rejected after several tries from different IPs. I've been reading about it and somebody suggested that greylisting should actually only work vs. IPs that are in blackhole lists. I don't want to use the already implemented blackhole lists feature as many of my customers have dinamic IPs and I had problems in the past, but if the greylisting would work only vs. blackhole list and not vs. the whole world, that would be awesome. is there any way to achieve something like this?
all in all greylisting sounds like a good antispam protection. it get's rid of a huge amount of spam with very little server resources...
however, there are several problems I would like to know if parallels is going to address or anyone could help.
1) lack of control GUI. greylisting customization has either to be done via shell or 3rd party product (GLM2 from haggybear.de). Is parallels going to make a GUI for this?
2) since i am on 11.5.30 (currently MU16) i think there might be a problem with greylisting rejecting emails with a 5.7.1 error instead the suposed to be temporal 4xx error.
I vaguely remember that I manually fixed that a couple of years ago on my old plesk 9.5.4 server, but I can't find any notes about it. Does this sound familiar to anyone?
3) multiple subnet MX senders. if a sender tries first with 200.x.x.x and the second try comes from 199.x.x.x the mail usually ends up rejected after several tries from different IPs. I've been reading about it and somebody suggested that greylisting should actually only work vs. IPs that are in blackhole lists. I don't want to use the already implemented blackhole lists feature as many of my customers have dinamic IPs and I had problems in the past, but if the greylisting would work only vs. blackhole list and not vs. the whole world, that would be awesome. is there any way to achieve something like this?
