Jump to content

mavdo

Members
  • Posts

    7
  • Joined

  • Last visited

Everything posted by mavdo

  1. Understood, and thanks for the suggestion, but I really think that Mr_Wizard is experiencing exactly the same problem as me, and mailhosts isn't the answer. From a selfish point of view, and being the OP, mailhost reconfiguration doesn't resolve my issue, and I strongly suspect it doesn't resolve the issue for anyone who uses outlook.com. I also use spamcop for gmail and a personal webserver, and they work great, and I do occassionally reconfigure these too. It's just outlook.com that gives me problems, yet no one has suggested a solution (except for my workaround). So with me re-asking for a resolution to the outlook.com header issue, I don't think this a "spiral into never-never land". In fact I think it is exaclty the point of my original question.
  2. On the very second line of my first post I said I had re-run mailhosts. It doesn't fix it.
  3. "the configuration of your mailhost"??!! What mailhost? It is outlook.com, including hotmail.com and outlook.com plus others. There is no "configuration"; it is what it is. You click on the corner of the message and say "Show Original" and the output of that is what you paste into SpamCop. Outlook recently changed the contents of this, presumably because of the way mail routes through their internal systems, possibly between hotmail and outlook domains. Now, everything apparently comes "from" outlook, which is nonsense. Strip that part out, and it finally "sees" the correct source. Now, on that basis, what "configuration" do you think we should be "checking" or tweaking? Because when you say "check" I was kind of assuming you'd give some advice on what to check and what to change, because I wouldn't have a single clue what configuration could be changed to fix this. However, I'm assuming that as I don't have a mailhost, as outlook.com handles all that for me, we need spamcop to find the correct part of the headings for us without having to do some manual filtering all the time. Hotmail and outlook.com are pretty big and we won't change the way they configure things. So either spamcop adjusts for them, or spamcop can't help a large percentage of the webmail users out there.
  4. Hotmail has changed again. I now have to remove only the top two header "sections", which normally is about 7 lines, for it to work. The third section has changed or disappeared. But if you don't do this, it does indeed report it to hotmail which is useless. Surely spamcop are planning a workaround because without it, it Spamcop is incompatible with hotmail/Outlook/live mail and has been for months. Hello SpamCop?.
  5. I've found that by deleting all the "Received: from *outlook*" and "Received: from *hotmail*" lines, spamcop is once again able to process the headers correctly and send the spam report to the correct originating IP. This should only be a temporary workaround though. Spamcop should be able to cope with these headers, so I still need to know if I need to do anything for it to "learn" about these new headers. For example, without the strikethrough lines, the following report (somewhat shortened for brevity) is now sent to 5.186.115.108 (abuse@fibia.dk) Received: from VE1EUR03HT037.eop-EUR03.prod.protection.outlook.com (2603:10a6:203:51::31) by AM5P192MB0210.EURP192.PROD.OUTLOOK.COM... Received: from VE1EUR03FT010.eop-EUR03.prod.protection.outlook.com (10.152.18.58) by VE1EUR03HT037.eop-EUR03.prod.protection.outlook.com (10.152.19.102)... Authentication-Results: spf=none (sender IP is 5.186.115.108) smtp.mailfrom=preparationresources.io; hotmail.com; dkim=none (message not signed) header.d=none;hotmail.com; dmarc=none action=none header.from=preparationresources.io; Received-SPF: None (protection.outlook.com: preparationresources.io does not designate permitted sender hosts) Received: from SNT004-MC2F10.hotmail.com (10.152.18.53) by VE1EUR03FT010.mail.protection.outlook.com (10.152.18.113)... X-IncomingTopHeaderMarker: OriginalChecksum:E3D3E6A... Received: from preparationresources.io ([5.186.115.108]) by SNT004-MC2F10.hotmail.com... Received: from unknown (72.171.122.200) by smtp.endend.nl with LOCAL... Received: from group21.345mail.com ([76.122.78.195]) by smtp.endend.nl with LOCAL...
  6. Anyone got any more ideas on this? It is a big problem to me - I can no longer use spamcop to report originating email domains. Not at all. Every mail to my hotmail is being parsed as if it were coming from hotmail. I have also deleted and re-run mailhosts, but the problem remains. For each email it is using the *.prod.protection.outlook.com address (eg Received: from DB5EUR03HT094.eop-EUR03.prod.protection.outlook.com (2603:10a6:203:51::15) by AM5P192MB0210.EURP192.PROD.OUTLOOK.COM) and this IPv6 address links back to report_spam@hotmail. But further down the message source the real originating domain is revealed (eg Received: from unfructify.channelarea.com ([89.191.226.17]) by SNT004-MC4F23.hotmail.com). In this example I want to send my report to this "channelarea.com" address, but I can't. Could this be be something to do with them using an IPv6 "outlook" address instead of the IPv4 hotmail address to which mailhost is set? My email domain is Hotmail, so that's all I can do to run mailhosts. I've no doubt this is to do with a change Hotmail have put in place to protect their service and/or introduce IPv6 and/or merge more closely with Outlook. But what do I need to do to get spamcop to recognise the real source, and not the Outlook IPv6 through which the message has passed? Otherwise I can only use spamcop to report links within the emails, and not the source of those emails themselves. eg https://www.spamcop.net/sc?id=z6385911404zca09268f3113b1f740d7c4c4950a45a4z
×
×
  • Create New...