HQJaTu

Members
  • Content count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral

About HQJaTu

  • Rank
    Newbie
  1. Thanks for the e-mail address. I'll try that. Regards, Jari Turkia
  2. My mailserver changed to using IPv6 internally. It has both IPv4 and IPv6 public endpoints for receiving mail. As Spamcop doesn't properly detect the internally used IPv6 hosts, the Spamcop is useless for me. Any ideas how to fix this? How can I make Spamcop dig the Received-list back to the original sender? Regards, Jari Turkia
  3. I've seeing more and more of these: Sorry, this email is too old to file a spam report. You must report spam within 2 days of receipt. This mail was received on Thu, 14 Aug 2014 00:43:30 PDT SpamCop parsed headers indicate: 3: Received: from nm36.bullet.mail.ne1.yahoo.com (nm36.bullet.mail.ne1.yahoo.com [98.138.229.29]) by smtp2.-removed-.fi (Postfix) with ESMTPS id 2F74E3F01E1 for <x>; Tue, 26 Aug 2014 21:41:07 +0300 (EEST) Hostname verified: nm36.bullet.mail.ne1.yahoo.com 4: Received: from [197.78.141.134] by web162906.mail.bf1.yahoo.com via HTTP; Thu, 14 Aug 2014 00:43:30 PDT No unique hostname found for source: 197.78.141.134 Trusted site ne1.yahoo.com received mail from 197.78.141.134 In reality, there are number of received-lines in the mail. However, regardless of the number of hops, the entire path looks legit to me: Received: from nm36.bullet.mail.ne1.yahoo.com by smtp2.-removed-.fi (Postfix) with for <x>; Tue, 26 Aug 2014 21:41:07 +0300 (EEST) Received: from [127.0.0.1] by nm36.bullet.mail.ne1.yahoo.com with NNFMP; 26 Aug 2014 18:41:01 -0000 Received: from [98.138.226.180] by nm36.bullet.mail.ne1.yahoo.com with NNFMP; 14 Aug 2014 07:46:39 -0000 Received: from [66.196.81.171] by tm15.bullet.mail.ne1.yahoo.com with NNFMP; 14 Aug 2014 07:43:31 -0000 Received: from [98.139.212.240] by tm17.bullet.mail.bf1.yahoo.com with NNFMP; 14 Aug 2014 07:43:31 -0000 Received: from [127.0.0.1] by omp1049.mail.bf1.yahoo.com with NNFMP; 14 Aug 2014 07:43:31 -0000 Received: (qmail 31539 invoked by uid 60001); 14 Aug 2014 07:43:31 -0000 Received: from [197.78.141.134] by web162906.mail.bf1.yahoo.com via HTTP; Thu, 14 Aug 2014 00:43:30 PDT I don't know how spammers do it, but apparently it is possible for e-mail to be stuck in the SMTP-routes of Yahoo. They seriously need to start streamlining the process at Yahoo. My guess is, that spammers can trigger the holding of mail somehow, by sending large volume of mail or using a bug somewhere in Yahoo's system. Anyway, to keep the crap out of circulation my suggested change is to start evaluating dates on my server instead of a trusted server. When it comes to Yahoo, I absolutely don't trust them. Regards, Jari Turkia
  4. This is beyond ridiculous! Today: Received: from WINXBEUS26.exchange.xchg ([172.23.130.69]) by winxhubus05.exchange.xchg ([fe80::b4d2:7ab6:7111:440c%10]) with mapi; Thu, 7 Feb 2013 23:18:36 -0500 Unable to process message. IPv6 addresses are not supported. How difficult it is to ignore ::1 and fe80::/64?
  5. Sir, my Thunderbird's Habul-plugin does not have that option. Well, perhaps I'll add the space-thingie into Habul and post the patch to the author. Regards, Jari Turkia
  6. I'm intentionally replying to a 4 year old mail. My box is getting increasing numbers of spam without body. Example: http://www.spamcop.net/sc?id=z5412285355z3...14ce0c35adbf2cz Posted with Thunderbird Habul-plugin. No manual copy/pasting errors. Sure, the spammers know SpamCop analysing/parsing policy. They manage to put all needed information in a pretty long subject-field and no body. The IP-address won't be blocked. Simple. Should I forge the spam to contain something in the body just to let it pass? I'd rather have SpamCop to add a button "Yes, I did report the entire mail. It does not have a body. I confirm this!". Regards, Jari Turkia