Quote:
Originally Posted by Ragunboneman
Quote....A message that you sent has not yet been delivered to one or more of its
recipients after more than 48 hours on the queue on serenity.mcc.ac.uk.
Yes It is Serenity that is my problem too It is on and off the blocklist every day, current listing,
Query bl.spamcop.net - 130.88.200.93
( Help) ( Trace IP) ( Senderbase lookup)
130.88.200.93 listed in bl.spamcop.net (127.0.0.2)
If there are no reports of ongoing objectionable email from this system it will be delisted automatically in approximately 17 hours.
Listing History
In the past 93.0 days, it has been listed 43 times for a total of 23.8 days
Great isnt it !! |
Right, checked senderbase.
If the person ( or is it you, I lost the thread ) trying to contact your from within that University changes their outbound SMT server to either:
130.88.203.23 yearning.mcc.ac.uk
or
130.88.203.16 xenial.mcc.ac.uk
Then they may be able to get email to ntlworld, as neither of these servers are currently listed in bl.spamcop.net. Assuming of course that these servers can be explicitly used as smtp servers in the email client settings.
You have to remember that there is a specific reason why the servers are listed in spamcop....they are being used to send spam.
Of course, ntl does not have to use such lists, but having been on the receiving end of ntl's lack of proper mail filtering, and having to delete between 30 - 50 junk emails per day, I for one are glad they are doing this.
---------- Post added at 19:01 ---------- Previous post was at 18:53 ----------
Quote:
Originally Posted by hatedbythemail
wonder if we could coordinate a response to ntl on this? unless theres collective anger theyre just going to keep on keeping on
|
Why bother? The servers are listed because of spam reports, and a listing happens when there are mutliple reports. sure, ntl COULD decide not to use those lists, then we would see the complaints creep up about the spam problem on the ntl network.
At its peak, up to 30M emails were being blocked daily from hitting the ntl network from known spam allowing networks thanks to these block lists.
I know its frustrating, but there is a collective responsibility here. Where ntl have been listed, they have worked with the listing organization to identify the rogue client or clients and take action to prevent listing again. When they demonstrate this they get de-listed. The same should be for those currently on the block lists, work with the listing network, sort out the problem, get removed from the list.