It should be sorted well before then as we've someone whitelisting all over the weekend.

Bob, I know that you're trying to help and I genuinely do appreciate that but I really don't think there is any particular benefit in wasting effort going back over lots of historic stuff at this point in time. It's way too late now and it's all perhaps a bit academic in any case because the only apparent option I have left to resolve the issues I am now faced with is to try and find a more appropriate service provider so that the generally trouble-free e-mail service in particular (in terms of zero spam and zero random missing/lost messages but ignoring other known problems) that I have enjoyed for ~10 years up until 13th May this year is restored to it's former glory.

Regrettably, I cannot see this being a reality by leaving things as they currently are. Whilst I am 100% confident that I could have (and would have on the 6 month anniversary of spam day as I intended)  completely and reliably resolved the spam problem that PN kindly gave me, I cannot possibly begin to resolve the apparent problems with lost/missing genuine messages or the seemingly iffy e-mail service and the unreliable/inconsistent filtering in particular which is now mandatory. 

A quick look through a bunch of recent(ish) messages reveals there are a several which will no longer be received - some you are already aware of, some not. I simply cannot live with not reliably receiving mail in general but particularly not with losing purchase receipts, invoices, hotel reservations, travel ticket bookings and various other very important stuff through no fault of my own (*) and with no sensible way to resolve the problem myself even if I had the time to try beating my head against yet another brick wall. It's all well and good PN pointing the finger at the sender and telling me their server or DNS is badly configured but that doesn't resolve the problem and it certainly doesn't resolve any problems there may well be with other messages that I don't as yet know will go missing for similar reasons.

I'm open to realistic and sensible suggestions but right now, finding greener (or at least slightly less brown) grass appears to be the only appropriate option and certainly the only one worthy of expending any further time and effort on

(*) I have recent messages from various sources including well known and respected organisations who are obviously sufficiently incompetent to have a slightly cooky DNS set up and therefore I will no longer be able to receive messages from them unless this is fixed.


May well be the case, I don't know for certain or care TBH, but the simple fact is that I haven't to my knowledge ever randomly lost 100% genuine mail before over the last 10 years but now I am losing it with apparent regularity. In addition, messages with very blatant and serious DNS or other issues are getting through but some with much less blatant and serious issues are not. In fact the very same message from the very same source sometimes does get through but sometimes doesn't.  Needless to say, no shortage of spam that breaches virtually all of these new checks is delivered without problems. Unreliable and inconsistent - which hardly instils any confidence whatsoever.


I think not ... and probably best left at that 

Well if some spammers have cracked the system already, DNS lookup must be considered a failure.

ISTR reading somewhere that it was now possible to remove mx.last and mx.core from your MX records.

Regards .....

I think mikeb's post summarises the customers' problem well and I too, after 7 years of mostly enjoyable PN service, will have to see what else is available in the market. I cannot work on the basis that delivery of my personal and work email is subject to the roll of a dice.

Brian

Only for domains not for @username.plus.com

My email has stopped working completely because of this.

Reason is that I use a domain name for all my email address, it's hosted at Heart Internet. Emails are forwarded from Heart to my Plusnet email account.

Plusnet have decided that Heart Internet use a Dynamic IP therefore ALL my email is bounced. Their IP address is 82.109.15.3. I have forwarded bounced test messages to abuse@plus.net.

I rang support last night and the only advice was to forward my email somewhere other than Plusnet!!

The Dynamic IP blocking should be disabled until further notice.

There will be other users affected by this - but they might not know it yet. I like Plusnet, but this is (one of the) worst blunders yet, in my opinion.

I'm not sure if this is a similar issue, having failed to receive an email I'd sent via F9 Webmail from a friends PC, I sent a series of test messages from Webmail, to my 123-reg hotsted domain, which should then come back to my F9 hosted domain.

The following bounce email came back:-

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:

  xxx@yyy.co.uk [this is the 123-reg domain name]
    SMTP error from remote mailer after RCPT TO:<xxx@yyy.co.uk>:
    host mx0.123-reg.co.uk [195.224.48.118]: 550-Recipient callout failed for xxx@yyy.co.uk from
    550 ptb-cgirelay02.plus.net

------ This is a copy of the message, including all the headers. ------ [deleted]

Unfortunately I'm not clever enough to know if the fault lies with F9, 123-reg or both.  F9 support have returned my ticket with a 'it's not one of our domains' contact someone else.

Not helpful - at all, but they may be right so looking for some guidance please!

I've just checked 82.109.15.3 and there is no rDNS set up for that range which is very strange and it is this which will be causing the issue. If you've sent a message to the abuse mailbox this will be whitelisted, but it may be worth double checking with heart that this is their mail server IP address due to the lack of rDNS.

Phil

I have received no e-mails whatsoever for 3 days.

I have a domain name which is hosted by serve360.com

Apparaently, I must ask them to change their IP to a static address.

I will phone them on Monday.

I have no idea whatsoever what all this means (and don't feel I need to).  I just open Outlook Express and click a button and my e-mail arrives.  How it all happens is a mystery - but it does - and everything has been working fine for years.

Now, suddenly, no e-mails at all.  I have only a basic user's knowledge and dread serve360.com asking me questions or throwing setting at me and asking me to make alterations - that I will not make any sense of.

Well dun PLusNet you have dun it to me.  I sent through the webmail 3 Test Messages.


Test 1) Test Sunday 23-09-2007 at 10:57 - Gone in to history.   
Test 2) Test Sunday 23-09-2007 at 11:46 - Gone in to history.   
Test 3) Test Sunday 23-09-2007 at 11:47 - Gone in to history.   

I sent by my NTL account 3 Test Messages.

Test 1) Test Sunday 23-09-2007 at 10:45 - Received back on my NTL & Hotmail account, But like the new site I am working on it has gone in to history.   
Test 2) Test Sunday 23-09-2007 at 11:12 - Received back on my NTL & Hotmail account, Gone in to history as well.   
Test 3) Test Sunday 23-09-2007 at 11:38 - Received back on my NTL & Hotmail account, Gone in to history as well.   


Return-Path: <****@dhea.org.uk>
Received: from aamtain08-winn.ispmail.ntl.com ([81.103.221.35])
          by mtain03-winn.ispmail.ntl.com with ESMTP
          id <20070923101056.IBRV4213.mtain03-winn.ispmail.ntl.com@aamtain08-winn.ispmail.ntl.com>
          for <********@ntlworld.com>; Sun, 23 Sep 2007 11:10:56 +0100
Received: from two.mx.123-reg.co.uk ([195.224.48.125])
          by aamtain08-winn.ispmail.ntl.com with ESMTP
          id <20070923101059.QMCT23160.aamtain08-winn.ispmail.ntl.com@two.mx.123-reg.co.uk>
          for <*******@ntlworld.com>; Sun, 23 Sep 2007 11:10:59 +0100
Received: from queueout01-winn.ispmail.ntl.com ([81.103.221.31])
   by two.mx.123-reg.co.uk with esmtp (Exim 4.43)
   id 1IZOQH-00025C-AT
   for info@goneintohistory.co.uk; Sun, 23 Sep 2007 11:10:45 +0100
Received: from aamtaout02-winn.ispmail.ntl.com ([81.103.221.35])
          by mtaout02-winn.ispmail.ntl.com with ESMTP
          id <20070923095012.GWJA4.mtaout02-winn.ispmail.ntl.com@aamtaout02-winn.ispmail.ntl.com>
          for <info@goneintohistory.co.uk>; Sun, 23 Sep 2007 10:50:12 +0100
Received: from user7fd3fe1743 ([82.17.151.19])
          by aamtaout02-winn.ispmail.ntl.com with SMTP
          id <20070923095005.QHZI17393.aamtaout02-winn.ispmail.ntl.com@user7fd3fe1743>
          for <info@goneintohistory.co.uk>; Sun, 23 Sep 2007 10:50:05 +0100
Message-ID: <004901c7fdc6$d87d22e0$6502a8c0@user7fd3fe1743>
From: "Dyslexia Health Education Association" <****@dhea.org.uk>
To: <info@goneintohistory.co.uk>
Subject: Test Sunday 23-09-2007 at 10:45
Date: Sun, 23 Sep 2007 10:48:05 +0100
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3028
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-Antivirus: AVG for E-mail 7.5.488 [269.13.28/1023]
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=iso-8859-1

Hi tdadyslexia,

I'm not entirely sure that your issue is the same as this thread is talking about.

If you sent messages through webmail and our system is blocking the message you would have received a bounce message into the account you sent the test from.

Have you seen any of these bounce messages and the information that they give suggesting that you can send an e-mail to abuse@plus.net with the sending IP address and have the address whitelisted?

Phil

No just went straight in to the black hole, or as I said gone in to history.

The eMail Forwarding points to my NTL, Hotmail & F9 account as well.   

[Edit]

Still no bounce message from the webmail at 13:55.

As I said I got all of the test messages back to NTL & Hotmail, but all blocked on F9 come PlusNet, and no bounce message.

Just to pickup on this point as I can't see it answered.  But it's not actually PlusNet that generate the bounce message.  When you send an email, your outgoing mail server attempts to contact PlusNets incoming mail server to deliver the email. 

As PlusNet's incoming mail server rejects it, the outgoing mail server (that you have sent the email through / from) then creates a rejection message which is sends back to the originator.  So all PlusNet do is reject the message.

Thanks for the response - and I have also had a reply stating the IP has been whitelisted (thanks!).

I will contact Heart Internet and put the rDNS question to them.

Cheers,

Support:

I have even tried sending e-mails to myself using your Webmail facility but they are rejected.

Please - can you not do something to allow me to receive all my mail from  serve360.com; or am I dependent on serve360.com doing something (just for my benefit) to allow you to allow me to receive e-mail.

Everything was working fine.  Now, it doesn't work at all - and it's nothing that I've done - it's what you have done!

I'm very unhappy with the situation in which I find myself.