dzekas Posted June 21, 2004 Share Posted June 21, 2004 one more problem. spamcop can find own address in received: headers. Received: from mail.domain.tld ([127.0.0.1]) by miranda.domain.tld (miranda [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 30101-10 for <user[at]somedomain.tld>; Mon, 21 Jun 2004 11:29:39 +0200 (CEST) Received: from spamcop.net (unknown [64.74.133.245]) by mail.domain.tld (Postfix) with SMTP id 24C2C17E4C for <user[at]somedomain.tld>; Mon, 21 Jun 2004 11:29:38 +0200 (CEST) "mail.domain.tld" is mail server name. same as in DNS MX records for somedomain.tld. "user[at]somedomain.tld" is email address I want to register. This is first and second Received: headers. If you need unmodified email headers - contact me in private email. If something is wrong with that email server, let me know. Link to comment Share on other sites More sharing options...
Wazoo Posted June 21, 2004 Share Posted June 21, 2004 There is no one here that can possibly help if all you are going to provide is a snippet of "modified" header lines. It seems more than a bit obvious that someone "here" would need to see the full and actual source to take a look at the issue. The Title you used for this Topic doesn't really make it clear what you are asking. (I'd already asked about your second post) .... I suspect a language barrier at work here, but .. have you tried looking at any of the Pinned postings? Link to comment Share on other sites More sharing options...
dzekas Posted June 21, 2004 Author Share Posted June 21, 2004 Spamcop mailhost registration scripts fail to parse confirmation email and return "Source IP not found" error. ------------------------------------ Subject: Spamcop account configuration: error From: "SpamCop robot" <spamcop[at]devnull.spamcop.net> Hello SpamCop user, Sorry, but SpamCop has encountered errors: Source IP not found. Your email host does not appear to correctly identify the sending IP of the email you receive. The last address identified by your mail host was 64.74.133.245 (). This does not appear to be a spamcop.net address. If you feel this is in error, please try again or seek help in the SpamCop help forum: <http://www.spamcop.net/help.shtml> ------------------------- Ok, I should have read pinned messages. what's the use of the forums, if all solutions are posted in private emails. I have't modified IP address, only names of my mail servers and email address. Link to comment Share on other sites More sharing options...
Wazoo Posted June 21, 2004 Share Posted June 21, 2004 The last address identified by your mail host was 64.74.133.245 (). This does not appear to be a spamcop.net address. Fallout of the relocation over his last week-end. Thanks for that data, I'll be kicking a note out to them as soon as I post this. Ok, I should have read pinned messages. what's the use of the forums, if all solutions are posted in private emails. That's a rough one. This mail-host thing is a creation by the SpamCop owner, program originator, program maintainer, etc., etc. .. Julian himself. He has pushed down the first-line level of support to the Deputies (though noting that it seems to be only Ellen that's involved with this) .... The other users here haven't the access or internal knowledge to look at anything, research anything, thus the only thing that can be done with this part of the SpamCop tool set is to pass the data to the few that have the needed access. I just had some dialog with Ellen about the conents of the Pinned items, lack of instructions as brought up by other recent postings, ... she agrees of course, but as there's only one of "her" <g> Link to comment Share on other sites More sharing options...
Wazoo Posted June 21, 2004 Share Posted June 21, 2004 Just added a new Pinned item ... hopefully this will help any others trying to register with the Mail-Host thing before all the internal stuff gets straightened out. Sorry you got caught in the bad-timing loop .... Link to comment Share on other sites More sharing options...
nanopowell Posted June 21, 2004 Share Posted June 21, 2004 Hello, I'm having the same issue - when I return the probes, I get either a "headers mangled" error, or the same error message that dzekas describes below: ______________________________________________________ Sorry, SpamCop has encountered errors: Source IP not found. Your email host does not appear to correctly identify the sending IP of the email you receive. The last address identified by your mail host was 64.74.133.243 (). This does not appear to be a spamcop.net address. If you feel this is in error, please try again or seek help in the SpamCop help forum: http://www.spamcop.net/help.shtml _______________________________________________________________ But - 64.74.133.243 apparently *is* a SpamCop address - ARIN WHOIS reports that is is part of the Ironport system. I'm using Eudora 6 on Windows ME - returning the probe via the web form that the probe directs you to, as the instructions specify. I've tried several combinations of cutting and pasting (a) full headers and body separately, ( full headers and body together in the top window, © full headers and body from "view source" from Eudora, (d) full headers and body pasted into Notepad and saved as text-only, then cut from text-only and pasted into the web form. I've tried submitting via Internet Explorer 6 and Netscape 7 in case the issue is browser-related. None of these seem to be accepted. I tried to set up mailhosts for addresses at our companies mail server (hosted as part of a web hosting package by Jumpline), Earthlink, and Hotmail. All encounter the same error. For the record, here's an example of the probe text (with headers) that I am pasiting into the form (iddentifying info replaced with x's). __________________________________________________________ Return-Path: <service[at]admin.spamcop.net> Delivered-To: spamcop-net-nanopowell[at]spamcop.net Received: (qmail 22968 invoked from network); 21 Jun 2004 16:04:05 -0000 Received: from unknown (192.168.1.101) by blade4.cesmail.net with QMQP; 21 Jun 2004 16:04:05 -0000 Received: from s126.n22.vds2000.com (HELO *********.com) (66.84.22.126) by mailgate.cesmail.net with SMTP; 21 Jun 2004 16:04:05 -0000 Received: from spamcop.net 64.74.133.243 by *********.com (8.12.9/8.11.2) with SMTP id i5LG43ep015078 for <*******[at]*********.com>; Mon, 21 Jun 2004 12:04:04 -0400 X-SpamCop-Conf: <xxxxxxxxxxxxxxxx> X-SpamCop-Test1: 1 2 3 4 5 6 7 8 9 0 a b c d e f g h i j k l m n o p q r s t u v w x y z A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Received: from [24.211.158.162] by spamcop.net with HTTP; Mon, 21 Jun 2004 16:03:58 GMT From: SpamCop robot <mhconf.ZSRKvzG3BzmwWkpc[at]cmds.spamcop.net> To: *******[at]*********.com Subject: SpamCop account configuration email Precedence: list Message-ID: <wh40d706eeg18440[at]msgid.spamcop.net> Date: Mon, 21 Jun 2004 16:03:58 GMT X-Mailer: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; Win 9x 4.90) via http://www.spamcop.net/ v1.346 X-spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on blade4 X-spam-Level: ** X-spam-Status: hits=2.7 tests=FORGED_MUA_MOZILLA version=2.63 X-SpamCop-Checked: 192.168.1.101 66.84.22.126 64.74.133.243 24.211.158.162 Hello SpamCop user, This email contains special codes and tracking information to help SpamCop figure out your specific email configuration. Do not post this email in public. It contains confidential information related to the security of your SpamCop account. Please return this complete email, preserving full headers and the special tracking codes below. Visit this address: http://www.spamcop.net/mcgi?action=mhreturn Alternately, you may submit via email. Forward the message as an attachment to this address. Or create a new message and paste this email into it. Either way, send it to to: mhconf.***************[at]cmds.spamcop.net Special codes follow: ################################################################ X-SpamCop-Mx: *********.com. X-SpamCop-Mx-Ip: **.**.**.*** X-SpamCop-Mh-Name: ********* X-SpamCop-Recip: *******[at]*********.com X-SpamCop-Unixtime: 1087833838 X-SpamCop-Conf: <xxxxxxxxxxxxxxxx> X-SpamCop-Randomness: <xxxxxxxxxxxxxxxx> X-SpamCop-Hash: <xxxxxxxxxxxxxxxx> ################################################################ ______________________________________________________________ Link to comment Share on other sites More sharing options...
nanopowell Posted June 21, 2004 Share Posted June 21, 2004 Thanks Wazoo... I added all my e-mail address and host info via the "Mailhosts" page before I became aware of the relocation issue. Now, do I have to wait until this is resolved to send the probes back, and in the meantime not report anything, and wait until the system is back up again and send back the probes I have already received? Or should I just continue reporting as before, then start over with Mailhosts once the system is back up? Link to comment Share on other sites More sharing options...
Wazoo Posted June 21, 2004 Share Posted June 21, 2004 OK, I just got a note back fro Ellen, am headed off to amend the Pinned post I recently put up. At this point, I can only suggest that if you can find the magic button to back out of the mailhost registration process, do this for now, continue reporting as in the past (as I recollect, reporting while mailhost registration is in limbo is a dangerous game <g>) ... when the DNS, rDNS, etc. issues get fixed (and propagated) then try to re-register with the mailhost thing. Link to comment Share on other sites More sharing options...
Ellen Posted June 22, 2004 Share Posted June 22, 2004 Thanks Wazoo... I added all my e-mail address and host info via the "Mailhosts" page before I became aware of the relocation issue. Now, do I have to wait until this is resolved to send the probes back, and in the meantime not report anything, and wait until the system is back up again and send back the probes I have already received? Or should I just continue reporting as before, then start over with Mailhosts once the system is back up? Log into the reporting webpage and click mailhosts. If you have no mailhosts in your configuration then throw the probes away and just continue on as you were. If you have some mailhosts in the configuration either 1) stop reporting until we get the rDNS setup properly or 2) delete those mailhosts that are already configured. When the rDNS is set up I will make an announcement about it. Sorry for the problems, this was a major move we made over the weekend and not last detail got handled perfectly however the vast majority of the tasks were completed successfully. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.