Are you talking about whitelisting the sender address or sender's IP address?
The e-mail address.
T.
--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers
Then surely the system makes sense?
Seeing that the email address can be forged, it could come from any
server... Therefor it should be dampened based on server ip address...
What I think you mean is (1) server is blacklisted, (2) damping
switched on (3) whitelisted address received (4)
These are the problems of using large ISP mail servers..
We simetimes have similar problems, because our IP is in a blacklisted
subnet It's nit that out IP is (currently) blacklisted, but the
subnet is, because other IP's in the range are blacklisted. The subnet
owner won't do anything
I think your sender will need to look at something similar...
That's what I was thinking. Problem is that this will not happen, because the
sender's ISP is the country's largest telephone provider
End users like this will never change their ISP. Depressing, but true. :-/
T.
On 2/1/2010 11:21 AM, Paul Houlbrooke wrote:
The following email got picked up by several RBL services. But when I
check the IP address myself, it's not listed in any RBL services.
I take it no one else is having this issue?
ASSP development mailing list assp-test@lists.sourceforge.net
schreibt:
This becomes a problem in the case I have. The server (a very big
ISP) has sent spam, but it has legitimate senders, one of whom I have
whitelisted.
I need to find a way to set up so that this sender from this
(sometimes
What problem is damping in this case?
Mail does not get through:
Feb-03-10 10:40:38 id-11637-00252 [Worker_1] 207.236.237.40
sue.opr...@bellnet.ca to: m...@trevorjacques.com Message-Score: added -10 for
Home Country Bonus CA (Bell Canada), total score for this message is now -10
:
:
:
ASSP development mailing list assp-test@lists.sourceforge.net
schreibt:
What problem is damping in this case?
Mail does not get through:
Feb-03-10 10:40:38 id-11637-00252 [Worker_1] 207.236.237.40
sue.opr...@bellnet.ca to: m...@trevorjacques.com Message-Score: added
-10 for Home Country Bonus
The reason, that the mail was blocked is written clearly in the log:
[spam found] (DNSBL, 207.236.237.40 listed in dnsbl-1.uceprotect.net
dnsbl-2.uceprotect.net
I suspect that the implication of this is that there needs to be a change to
assp. Here's my logic for that:
1) large telephone
ASSP development mailing list assp-test@lists.sourceforge.net
schreibt:
Reluctantly, we (i.e. assp) have to deal with this. It's not up to us
(i.e. the receiving e-mail server admins) to remove these spamming
ISPs from the DNSBLs.
The default configuation of ASSP (V1/V2) would not have blocked
A bad switch on the LAN isolated the ASSP machine from the local DNS's.
Here is what was in the ASSP log:
Feb-03-10 17:18:23 Name Server 192.168.0.5: ResponseTime = 3 ms;
Feb-03-10 17:18:23 Name Server 192.168.0.1: ResponseTime = 3 ms;
Feb-03-10 17:18:23 AdminInfo: Name Server 192.168.0.5: does
The default configuation of ASSP (V1/V2) would not have blocked this
mail.
zen.spamhaus.org=1|bl.spamcop.net=1|psbl.surriel.com=2|ix.dnsbl.manitu.net=2|l2.apews.org=3|combined.njabl.org=1|safe.dnsbl.sorbs.net=1|dnsbl-1.uceprotect.net=2|blackholes.five-ten-sg.com=3
I've not even looked at this
1) large telephone company ISPs are the source of quite a lot of
spam, as well as being the source of legitimate e-mail;
2) in the real world, we'll never get these ISPs to react to requests
to:
ASSP handle this by the concept of content only;
- Put the IP-Range of the large ISP into -
I take it no one else is having this issue?
Did you check your DNSBL cache ? Not sure,
but I suspect it may be polluted
--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with
14 matches
Mail list logo
