Jump to content


  • Posts

  • Joined

  • Last visited

albert2's Achievements


Member (2/6)



  1. Hello, Because the extra complexity added to reporting spam thanks to Google Mail, where i had to remove lines from the headers before i could report making automatisation by forwarthing the spam messages to my reporting address impossible, a while back i finally gave up reporting. When i reported my settings at spamcop was to munge my reported messages to remove identifying information, so if the spammer gets a report send to him by his provider it should not trace back to me. At least this is what i hoped. Since i stopped sending reports my spam suddenly went down to a point where i can say atm i only receive 10% of the spam i used to receive when reporting. Can this be explained ? I can see only one explication myself which is that though the spam reports somehow my email address was confirmed to the spammer making him retaliate to me for the reporting or just send more spam in the hope i would click on the links anyway. However a lot of this spam didn't even contain links or financial scam, so where just send to annoy me which seems to confirm my thoughts. So Why does munged reports still allow to spammer to identify the reporter ?
  2. I did some testing after your reply. I tried removing my Mailhost config, but that didn't work. So after doing Mailhost config again it suddenly worked again. I do inde manually report on the website by pasting my spamsource & then removing Google's internal IPv6. Before i used to send spamcop a mail which contained multiple spam mails in source format but as i can't alter the source this way i had to go to manual reporting (thank spamcop for NOT providing a solution) Don't expect Google to bring a solution, Google seems to dislike if not hate spamcop & certainly isn't interested in providing support to spamcop users. Can you suggest me another lasting & trustworthy free email address supplier which will not try to irritate spamcop users ? PS: Thanks Google for being crappy , untrustworthy, unsupportive Mail service
  3. Hello, i posted earlier topic about this & so did others http://forum.spamcop.net/topic/26014-reporting-issues-reason-fake-headers/?tab=comments#comment-115138 http://forum.spamcop.net/topic/14536-mailhost-configuration-problem-identified-internal-ip-as-source/?tab=comments#comment-91162 http://forum.spamcop.net/topic/25761-gmail-how-to/?tab=comments#comment-114543 http://forum.spamcop.net/topic/25970-ongoing-mail-host-problems-with-gmail/?tab=comments#comment-114972 And there are probably more threads about this. However there seems to be another problem now with the headers from mails send to one's gmail address. After getting response to earlier threads which included a solution, being to remove the 2nd (& 3th) line(s) but now again it keeps saying : 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. I will include an example header, hope someone finds a problem that can be solved; The purple lines i have removed like i did before, however removing these lines alone is not working anymore, so there has to be something else wrong in the header. I also tried removing both the purple & orange lines as to me they show similarity in context, but this still gave the same reporting error. Delivered-To: Myemailadress@gmail.com Received: by 2002:a50:b7ca:0:0:0:0:0 with SMTP id i10csp5151139ede; Sat, 1 Dec 2018 17:15:24 -0800 (PST) X-Google-Smtp-Source: AFSGD/VI8tuKT3hgMGo/T6S9J8LV0TUxad03me5GvNAuGZejcdMuPXnBVRTwwBxZSUpM31Vdv/no X-Received: by 2002:a1c:dc86:: with SMTP id t128mr3835008wmg.42.1543713324132; Sat, 01 Dec 2018 17:15:24 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1543713324; cv=none; d=google.com; s=arc-20160816; b=ZjoExNwS/Cd42bU1MPTyvwhCBWrkmj21HosYpPuD8rKcK9nMIk/JRXVKS31x9svwCP uh17Wr6f81AKC8MMjI9OP2nJ+qb8GBr4ZNgxyNBGZ3e/8yKYMA0u0mdau4i3CrL1V4af qJcozrLFErbQgu5BlAi/WYM2P2wGIOq7sboKw9Z6mEBzJgQia1Vq4/9T7SU17h78Zrfp yhr9fd94O4C6O19s/lfU9pYDXnQ5uYb0o5ZEFmo74vM9zi82ICaIa+5idimdj7cW0W/F +JAN/c8OqmRu37yHu1tSuiM+T/mXh1D4euLhNvv1MDzrthhMBLxWspxhvQFRnW2OM35q QbOg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=reply-to:message-id:to:subject:date:from:list-unsubscribe; bh=tV2Z7qlInGr+tkIvDOpGOMUcaRSUGjKRdHuidxgCaZA=; b=iYLDu9LpQglGro+spovOEaVi9qcRniqP26ffMkI7d8gQlEdWkVd2Yl0/IRfv9g5qAM uGbj91gF4xAC3BqIZZxhd9BcqbjEbYNjs5727g6PZ2/dmW9qHgQkpiMYSL6qvgULqGSJ 9Ty9p3yEH3Y9ppqkKYVbEHr1iqTtIqO2pBNi96fO6NaZZOtUOC3tiDy4lSoal4fdu2Up HxuFivBndRbd9SXJwhqA+W1i2GWn0altEOAydB0FYnTxMr65OVVwXdpRGCcolGHNBKwk qGs46E4SzkGNl4/FP0clXdpXtdbR+ATOn61JdgAV2+pRKDs7HEUyPeCkaXLK/8RgpdLW jbQA== ARC-Authentication-Results: i=1; mx.google.com; spf=softfail (google.com: domain of transitioning bounceemail@google.com does not designate as permitted sender) smtp.mailfrom=BounceEmail@google.com Return-Path: <BounceEmail@google.com> Received: from damismanetry.com (damismanetry.com. []) by mx.google.com with ESMTP id r12si7335605wrm.207.2018. for <Myemailadress@gmail.com>; Sat, 01 Dec 2018 17:15:24 -0800 (PST) Received-SPF: softfail (google.com: domain of transitioning bounceemail@google.com does not designate as permitted sender) client-ip=; Authentication-Results: mx.google.com; spf=softfail (google.com: domain of transitioning bounceemail@google.com does not designate as permitted sender) smtp.mailfrom=BounceEmail@google.com Received: from damismanetry.com ( by damismanetry.com id h0cp2o16lt0h for <albert2@gmail.com>; Sat, 1 Dec 2018 20:15:23 -0500 (envelope-from <BounceEmail@google.com>) Received: from s.okazik.pl (s.okazik.pl. List-Unsubscribe: <HK-ewiufqtkol-__Random_nm[5,l]-b2ce6mg22ipujrjn74rz733ns747n3x4nt1by8hfgfnb9va6@damismanetry.com> From:Emma.<xipdr@IA1H.veronica.br> Date: Tue, 22 May 2018 17:39:47 -0400 (EDT) Subject: You sent me photos ? To: <YZZSWPO@pn6cmts.uk> Message-Id: <PWAYQA-RYUGVUDWDACIWGXOZZXAGGSNLWPCNP@cisco.com> X-EMMAIL: Myemailadress@gmail.com Content-Type: text/html Reply-To: sarah <info@4biancili.org.uk> Please stop sending me your pictures. Thanks, <img src="http://4biancili.org.uk/kTIl.php?nn=82itk__o22fakeCampaignNV_1ifn.snslfel1.A018trfize01f5v7rv_r3.1959c2c4cTgybzBqZjc00m4NPa" widht="1" height="1" >
  4. https://groups.google.com/a/googleproductforums.com/d/msgid/gmail/adfc2d75-34f4-47cd-8de5-2b47cbc97675%40googleproductforums.com?utm_medium=email&amp;utm_source=footer This is the post i made at Google Gmail forum, as a user suggested i also send feedback to Google Directly. I hope they take it a bit more seriously. However i think we need to hope Spamcop itself takes it seriously & come with a solution for their users. If they think it might open a security hole if they do that... , they might consider i do it manually now for each spam mail i report & if it opens a security hole then i open it manually & uncontrolled now. While if they come with a solution they can mark each spam they let trough tile ignoring these lines & use this mark to enable them to use different security rules for these spam reports or whatever they think is needed to close a security hole.
  5. I got this reply at the Gmail Forums ; I suggest that you complain to Spamcop if they are not accepting legitimate email headers. SpamCop.net - SpamCop FAQ: How can I contact a SpamCop ... So they are saying it's a legitimate header. It would be best, like i suggested before, that the spamcop processing scri_pt looks for these lines which are always the second (& third) line of the header & ignore them for processing but leave them otherwise untouched.
  6. I really think this is annoying. I can't automate my spam reporting anymore because now i need to do everything manually now for each spam mail. This process includes: In my mail app: Open each mail In the menu select to view the source Copy the source In my browser: Paste the source Copy the line that breaks reporting Delete the Line """"""""""" After Process spam Paste above line in comments This has to be done for every Mail, i think its best to create a work around the problem at Spamcops side until Google resolves this ( if they ever will)
  7. Lets hope they come with a solution quickly then !
  8. Thanks Petzl, Seems you have pinpointed the problem to the second header line. Do you or someone else knows what exactly is caused by this line & what this line tells ? Again maybe Spamcop systems can be altered to remove or ignore this line automatically when present so users won't need to take care of it anymore for each mail. If this line is specific to mailboxes from gmail, maybe spamcop could contact google and ask for a solution. Albert
  9. Hello, Since a while i have problems reporting spam while before i never had issue's. On my side nothing has changed so it's certainly not a mail host issue. This are the exact errors spamcop gives me: No unique hostname found for source: xxxxxxx 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. Nothing to do. I first ignored the spams & did no efforts to report them but now every spam i received get bounced for this reason & spams send to me grow in numbers. So i needed to take action and looked for above errors on this forum. I found a solution and with it i can report again but doing this for every spam is a time consuming workaround, besides that there is each time the risk i forget to mungle out my own email address & face retributions from the spammer if he receives a copy of the report. This is the solution: Seem a number of variants copy from including this line down ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of www.@vanilla.ocn.ne.jp designates as permitted sender) Then copy and paste the above bit in notes' After SpamCop has parsed it. I hope Spamcop could do an effort in including a process that automates this on their side so users can simply copy paste their mail source, in this case the mingling would also be automatically performed by spamcop as it was done before. Thanks for looking into this & providing a permanent solution. Albert PS if you require samples please respond to me & i will provide a few
  10. Hello, I want to report some spam but Spamcop wont accept it because the Mailhost configuration problem, identified internal IP as source. I receive this mail on my gmail account & it seems the spammer also uses a gmail account. I have configured Gmail as my Mailhost in my spamcop account. The mail seems indeed being send from internal IP range (10.x.x.x), This is not the internal IP range of my home network (168.x.x.x). I think this might be the internal IP from Google Gmail servers but i'm not sure of this. Have a look at it: Delivered-To: Me[at]gmail.com Received: by with SMTP id rl2csp386309obc; Wed, 12 Nov 2014 05:55:21 -0800 (PST) Return-Path: <them[at]gmail.com> Received-SPF: pass (google.com: domain of them[at]gmail.com designates as permitted sender) client-ip= Authentication-Results: mr.google.com; spf=pass (google.com: domain of them[at]gmail.com designates as permitted sender) smtp.mail=them[at]gmail.com; dkim=pass header.i=[at]gmail.com X-Received: from mr.google.com ([]) by with SMTP id w15mr2664864igp.39.1415800520858 (num_hops = 1); Wed, 12 Nov 2014 05:55:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=sHp0KLglkDMnaRwMjslVlYNGGS2qrLV6RRJH0vVSylg=; b=k/WGx30jlvYVHew2/tkIwdg94k56zl9QEf6/fFid3IBl8YWhlHQfdymvtKRB2KP2Ry cRVNkQO7nD6c/+Dl3RSkZRuasKjdwK5MNOlaadoSBEHCpipX06QLvxZMyBy6WBuEMxvs oZoV+jy7gFw447shfiCwzsBmJTmoqA+0dTQ8uVHyb+zxZ+03OeYZC0iI0bAdl9mSx8Rc ISgoKhaQIgSdBQqwIcS+ui80nfq6E67cJREUN9V9Inii9rvJQhyAvKyJl1TfNK/l8RWe Pwx2UO6DFlGYdrT1rxfhVrF3u7G4FNoiJAtJyszNBqSL2YXpLO0tB8q8d4ywzLDLOYS9 n/uQ== MIME-Version: 1.0 X-Received: by with SMTP id w15mr4159178igp.39.1415800520533; Wed, 12 Nov 2014 05:55:20 -0800 (PST) Received: by with HTTP; Wed, 12 Nov 2014 05:55:20 -0800 (PST) Date: Wed, 12 Nov 2014 14:55:20 +0100 Message-ID: <CAOw3h+4DDS_Gox9__=MPomZC2fN4Lok3enTKKVJ-Tg7-k5d_mQ[at]mail.gmail.com> Subject: Subject From: Them <them[at]gmail.com> To: Them <them[at]gmail.com> Content-Type: multipart/alternative; boundary=089e0158caa4197c420507a9bfc8 Bcc: me[at]gmail.com Message ....... containing url ....... You can see 2 differen ip adresses iin the 10.x.x.x range in the mail. So can this mail be reported as spam ? Are these Google's internal IP adresses ? Is this a way to hide the origin of the spam mail ? Is there another question about this i haven't ask but seems important & you can provide the answer to it, please do. Thanks for reading my question & providing answers and solutions. Albert
  • Create New...