Jump to content

MarkA

Members
  • Content Count

    6
  • Joined

  • Last visited

Everything posted by MarkA

  1. Thanks @gnarlymarley, that does seem to work if I modify and dump the bad record. Interesting though... Now MailChannels has replaced the 0.0.0.0 initial IP with another IANA reserved/shared IP (at least it looks like maybe they're trying to make it a bit better). I can add the updated mailhost to my account successfully now, but if I don't still modify that first record, it now wants to report to devnull with the IANA IP: Re: 100.96.6.15 (Administrator of network where email originates) To: abuse#iana.org@devnull.spamcop.net Anyway, some progress and I'm not dead in the water any more at least. Thanks again.
  2. Well, nobody gives a hoot about this. I've spent several hours on it but can't do any more. SpamCop admin won't state which RFCs are not compliant in the sending configuration headers, if any, and DreamHost doesn't think it's an issue after working with them. So here we are. It's broken some place but nobody wants to take ownership, see it through and fix it. SpamCop doesn't work any more with DreamHost. Glad I didn't renew my paid account here. Done.
  3. Still not resolved, but an update for anybody still following this... I sent a request to spamcop admin and got a response from SpamCop/Richard. It looks like the 0.0.0.0 IP is the cause of the issue as I had guessed, but also Richard identified IANA-reserved shared IPs (100.96.84.23, 100.97.13.101) being used on the MailChannels hops which may be contributing to it. Responses from Richard, referring to headers from some subsequent tests with this same host: And then: So... It looks like MailChannels needs to do some configuration changes on their side. Hopefully Ken Simpson from above is still monitoring. I will also be opening tickets at DreamHost and if I can, at MailChannels.
  4. Already done that. I have several other mail hosts for other providers that have been working fine here for many years, and when one changes or I get a new one, I add/update/delete without issue. This issue seems to be unique to the current mailchannels servers setup, and there's really not much more detail I can lay out here. Lots of previous detail above that I've provided that's not been commented on. So my questions remain: Is there anything in the current headers, host server, etc. that appears to be invalid or actually traversing domains as listed in the spamcop validation message, etc. Is spamcop having issues with the 0.0.0.0 initial hop IP address? If there are obvious issues with the headers, it seems that the mail provider needs to fix. If everything looks valid, either there's a spamcop bug here, or I'm still doing something wrong, which unless something has changed here, doesn't seem likely or at least obvious at this point. And simply following the spamcop provided "proceed here" URL during validation after the "traversing multiple domains" error, which results in an HTTP 500 server error that I detailed above would seem to indicate at least some issues exist on the spamcop side of things.
  5. Sorry, but it's not clear here why I would want to delete my mailhost entry to solve for this? All of the above server names I listed are for a single mail host entry. Just to validate though, I did dump that mail host and attempted to resubmit a spam entry. It failed as I expected with the "system not associated" error, plus the original "internal IP as source" errors: Possible forgery. Supposed receiving system not associated with any of your mailhosts Will not trust this Received line. Mailhost configuration problem, identified internal IP as source Mailhost: Please correct this situation - register every email address where you receive spam No source IP address found, cannot proceed. And now when I attempt to re-add the missing host I'm getting the error: Host pdx1-sub0-mail-mx1.g.dreamhost.com (checking ip) = 64.90.62.163 Sorry, SpamCop has encountered errors: The email sample you submitted for <x> appears to traverse more than one domain. Please ensure that you configure each mailhost individually and in order. The error also had the "Proceed here:" URL, which then resulted in a subsequent 500 error. The host-add validation email headers which generated the above validation error look like this (less email addresses removed): Return-Path: <x@admin.spamcop.net> X-Original-To: <x> Delivered-To: x21240582@pdx1-sub0-mail-mx1.g.dreamhost.com Received: from inbound-egress-6.mailchannels.net (inbound-egress-6.mailchannels.net [199.10.31.238]) by pdx1-sub0-mail-mx1.g.dreamhost.com (Postfix) with ESMTP id 0717CABF45 for <x>; Mon, 4 Jan 2021 20:09:29 -0800 (PST) Received: from postfix-inbound-1.inbound.mailchannels.net (localhost [127.0.0.1]) by postfix-inbound-1.inbound.mailchannels.net (Postfix) with ESMTP id BDE04C0199 for <x>; Tue, 5 Jan 2021 04:09:29 +0000 (UTC) Received: from inbound-trex-0 (100-97-252-78.inbound-trex.inbound.svc.cluster.local [100.97.252.78]) by postfix-inbound-1.inbound.mailchannels.net (Postfix) with ESMTP id 99C89C0156 for <x>; Tue, 5 Jan 2021 04:09:29 +0000 (UTC) Received: from prod-sc-www01.spamcop.net (vmx.spamcop.net [184.94.240.112]) by 0.0.0.0:2500 (trex/5.18.11); Tue, 05 Jan 2021 04:09:29 +0000 It's not clear here what constitutes traversing more than one domain, unless it's having issues with either the 0.0.0.0 IP or the handoff from mailchannels to dreamhost, and then my final email address in those headers is neither of those, being a hosted domain at Dreamhost. So from bad to worse now. I don't have any forwarding between email accounts as part of this. Thanks.
  6. Any update for Dreamhost and Mailchannels here yet? I'm a long time spamcop user but new to the forums for this issue and am having similar recent issues with my Dreamhost reporting. And though I'm not experiencing a parser hang, the parser simply now says my mailhost is not configured correctly: Hostname verified: inbound-egress-5.mailchannels.net Possible forgery. Supposed receiving system not associated with any of your mailhosts Will not trust this Received line. Mailhost configuration problem, identified internal IP as source Mailhost: Please correct this situation - register every email address where you receive spam No source IP address found, cannot proceed. ...with headers like this sample, which also has the 0.0.0.0:2500 IP/port as the first receiving host as reported previously here for mailchannels. It kind of seems like the the 0.0.0.0 IP IS the issue, as it's NOT in the mailhosts list obviously: Return-Path: <web.kws@www.kenwoodstore.it> X-Original-To: x Delivered-To: x Received: from postfix-inbound-0.inbound.mailchannels.net (inbound-egress-5.mailchannels.net [199.10.31.237]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pdx1-sub0-mail-mx66.g.dreamhost.com (Postfix) with ESMTPS id 5C266A66AB for <x>; Sat, 2 Jan 2021 16:23:22 -0800 (PST) Received: from postfix-inbound-0.inbound.mailchannels.net (localhost [127.0.0.1]) by postfix-inbound-0.inbound.mailchannels.net (Postfix) with ESMTP id 13523C0201 for <x>; Sun, 3 Jan 2021 00:23:22 +0000 (UTC) Received: from inbound-trex-0 (100-97-252-78.inbound-trex.inbound.svc.cluster.local [100.97.252.78]) by postfix-inbound-0.inbound.mailchannels.net (Postfix) with ESMTP id ABE37C01CC for <x>; Sun, 3 Jan 2021 00:23:21 +0000 (UTC) Received: from www.kenwoodstore.it (www.kenwoodstore.it [46.183.234.170]) by 0.0.0.0:2500 (trex/5.18.11); Sun, 03 Jan 2021 00:23:21 +0000 X-Message-ID: MMk7naTgSUkn2DtiwRHLscNL Authentication-Results: inbound.mailchannels.net; spf=none smtp.mailfrom=web.kws@www.kenwoodstore.it; dkim=none; dmarc=none Received-SPF: none (inbound-dmarc-755b7f964d-wl2d2: domain of www.kenwoodstore.it does not provide an SPF record) client-ip=46.183.234.170; envelope-from=web.kws@www.kenwoodstore.it; helo=www.kenwoodstore.it; Received: by www.kenwoodstore.it (Postfix, from userid 504) id 5EF7B22445; Sun, 3 Jan 2021 01:23:16 +0100 (CET) To: <x> Subject: <x> X-PHP-Originating-scri_pt: 504:Sendmail.php From: JVCStore Customer Care <info@jvcstore.it> Date: Sun, 03 Jan 2021 00:23:16 +0000 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline MIME-Version: 1.0 I had a different original mailhost configuration that worked for a year or so at Dreamhost but started showing a bunch of spam sourced from networking@carbon60.com (mailchannels) as the reporting address (I was unaware of the apparent Dreamhost change). I started getting enough of these, unaware that Dreamhost was now associated with mailchannels, that I actually setup a filter at Dreamhost looking for the mailchannels IP addresses in the headers and auto-forwarded to spamcop for reporting. This resulted in a nasty loop with what was probably thousands of reports being submitted, and upon an error during parsing, spamcop sent me an email response which also had those same mailchannels IP addresses in them, which reported again. It used up all of my spamcop fuel/credits I had and after three days of no emails making to my inbox, I realized the mistake and unwound it all. It was then that I reconfigured the Dreamhost mailhosts to current, which doesnt work at all now due to the above. My current updated mailhosts config list now includes: inbound.mailchannels.net postfix-inbound-0.inbound.mailchannels.net postfix-inbound-1.inbound.mailchannels.net postfix-inbound-2.inbound.mailchannels.net postfix-inbound-3.inbound.mailchannels.net postfix-inbound-4.inbound.mailchannels.net postfix-inbound-5.inbound.mailchannels.net postfix-inbound-6.inbound.mailchannels.net postfix-inbound-7.inbound.mailchannels.net postfix-inbound-9.inbound.mailchannels.net postfix-inbound-11.inbound.mailchannels.net Thanks
×