Jump to content

RobiBue

Membera
  • Posts

    310
  • Joined

  • Last visited

Everything posted by RobiBue

  1. That is exactly what wants or needs to be avoided -- to redo the reports. Even though the message to the abuse departments didn't get sent, the spam got processed by SC and entered in the SCBL. every time the same identical spam gets reported, the reports get skewed and SC ends up being listed as unreliable due to skewed reports, and as a SC user, I don't think that would be a good thing. One report for one spam recipient. That's the goal. at least that's the goal I thought we were aiming for... Hence my inquiry into resending only the emails to the abuse depts, instead of resubmitting the spam over and over until the errors finally subside.
  2. While the spam was processed, the 3 mentioned Vietnamese abuse departments will never receive a report to act upon. Well, never for this specific submitted report due to the smtpEnvelope/smtpFrom errors (452 and 550). I'm not counting google's report since that one gets /dev/null'ed right away without any further decorum.
  3. sorry, I don't seem to be making myself clear. I'm not talking about the devnull reports, I am talking about reports that because of either Can't send report: smtpEnvelope ... or OP's [an error occurred while processing this directive] errors (assuming that if I check with [Past Reports] tab and the report was processed, but emails to me and the abuse depts of non-devnulled isps) were not sent — I can tell reports were not sent because I didn't receive mine — could be retried to send to a later time or manually triggered to re-send... edit 2021.10.18-04:50:00 CDT: I'm talking about reports like these: https://forum.spamcop.net/topic/46809-server-issue/?do=findComment&comment=158695 btw, I had just an "awesome" experience with cloudflare who replied to me with an automated message, but when I checked the link I reported about, I saw that they had manually edited the page in question (or replaced it) with the following message: <p>This link has been flagged as phishing. Phishing is an attempt to acquire personal information such as passwords and credit card details by pretending to be a trustworthy source.</p> <p><strong>If you're a visitor of this website</strong><br /> The website owner has been notified and is in the process of resolving the issue. For now, it is recommended that you do not continue to the link that has been flagged.</p> <p><strong>If you're the owner of this website</strong><br /> Please log in to cloudflare.com to review your flagged website. If you have questions about why this was flagged as phishing please contact the Trust &amp; Safety team for more information.</p> yay! 🎆 (fireworks)
  4. I understand that... I guess I wasn't clear: instead of me re-submitting the report (since it would be the same spam "reported twice") there should be an option to re-send the emails from the original report. the ones that were never sent in the first place... That's what I meant with "re-sending the report" as opposed to "re-submitting the report"
  5. I am curious, is there a way to "re-send" a report? What I mean, when an error like that happens, I don't receive a report which I usually send to my own email for "safekeeping/bookkeeping" to confirm that the spam was reported. That would enable me to avoid double reporting on such occasions...
  6. thanks forgot that part 😔 (although I can't confirm it, many times an error like that appears, the URL actually points to the error and not the tracking URL — will keep my eyes peeled though)
  7. when someone gets that sort of error, they won't get a tracking URL. that error happens before the spam gets parsed. @ArtmakersWorlds an hour later, here on Central Time, the reporting works for me without error. it also could be that the spammers have figured out a way to break the system (although I highly doubt that)
  8. it has been working for me too... clearly "speculation does not resolve the issue" but by the system working (be it on and off or even seemingly on) one can speculate that the system is being maintained and probably some disk space assigned (or even reprogrammed to account for certain 'errors') to work properly.... pure speculation here... also got a reply just moments ago from NTT Communications(OCN) (automated reply though) and from support.mchost.ru (also automated reply) something is working 😈
  9. or an option: coal from the locomotives (they are not used atm I believe), build a steam generator, use snow (melted) for steam and viola, you got yourself some power and heat too 😀 ... when we were young 😁 I take it power or internet is out again... back to basic life it is
  10. Reminds me somewhat of a Judy Collins song....
  11. well, got some replies from them and they said that the IP I reported about was not handled by google cloud platform.... heck, the whole internet is the cloud... and anything google is in the google cloud.... marronies!!! (or maybe I am the marroni... ðŸĪŠ )
  12. when I get the "Can't send report" message, I simply resubmit and usually the second time around it works. Honestly, I don't know if I'm "allowed" to resubmit spam (usually not,) but in these cases I believe these measures are warranted. The reason I resubmit is that reports are not sent if the error arises, and it is not possible (yet) to manually force a report to be re-sent.
  13. Yeah they fixed it 😁 but there for a couple of days thereafter the whole site was a mess until they fixed the css access which wasn't being downloaded with the forum pages.... but they eventually fixed that too 👍
  14. "Internal handoff" means that there is no reporting address to be found since it is internally and could be anywhere in any company. It's basically the same as either of the three private IPv4 addresses: 10.0.0.0/8, 172.16.0.0/12, or the more common home network 192.168.0.0/16 used in most home networks. This means that there is no set "reporting address" to contact the "owner" or its upstream owner. SC is correct in this assessment and, no matter how strongly you might feel about it being wrong, it still won't find a reporting address since there is none to find. I hope this explanation helps Just in case I am unable to explain it clearly, there is a Wikipedia article related to Unique Local Address Especially in the Properties section
  15. I use https://support.google.com/code/contact/cloud_platform_report instead. with Firefox it works. In the section about Cloud Platform Service I put "not sure" since emails don't really fall into any of those categories... then I place a short note about the received: header line in the Abuse Details box and attach the full email in the additional logs (the plural is somewhat misleading since only one file can be attached...) In the abuse details text box I also mention the lines spf=pass (google.com: domain of ????@gmail.com designates 209.85.220.41 as permitted sender) smtp.mailfrom=????@gmail.com; of both Authentication-Results: and ARC-Authentication-Results: in the headers.
  16. I don't know. I sure hope so, although they'd investigate them just as they'd investigate the reports sent through SC.... of course, if the reports to google abuse bounce, then the chance is higher by submitting them manually and directly.
  17. My apologies. Due to the CSS misconfiguration of the forum I somehow overlooked that part. All good now
  18. The problem is that abuse@google.com bounces (25774 sent : 16690 bounces) and that's why SC comes back with "no reporting address" If you want to report to google, you have to report manually through your email and not through SC.... I am thinking that those bounces created SC's latest submission hiccups.
  19. I believe the mail server is reaching its HDD limit, hence the SMTP 452 #4.3.1 errors. Somehow I think there is a cleanup job running in the background, but it is also possible that the server's HDD is starting to lose capacity due to corrupted sectors (this is just a thought, although it's feasible taking into consideration the age of the system...) and with that, even a cleanup job won't keep the system happy for long...
  20. in regard to the 452 #4.3.1 errors: the receiving smtp server is most probably at the end of free disk space here I would say that bounces.spamcop.net has reached its free HDD space (or the allocated space for the mail server) maybe @Richard W or @Lking could put in a word to the server's system admin to run a cleanup job (just a loud thought here 🖖)
  21. The problem is not that the site isn't upgraded to HTTPS. The problem is that the certificate is issued to *.cloudfront.net and that is what needs to be fixed... but I agree! I am browsing the forum with a security exception, which doesn't give me much confidence...
  22. Hello Perrin, not knowing how you got informed that you are "blacklisted" leaves me at a loss too. If you enter here (spamcop) your email address web address individually -- that is as a single address (one line only) -- you will be able to see if your email/site are blacklisted by spamcop (SC) but somehow I doubt it by your description of the issue. As an example: I added www.spamcop.net in the field and here is the result: https://www.spamcop.net/sc?track=www.spamcop.net under Statistics you can see the status of the website in the block lists. It is possible that your problem does not stem from SC but from an individual provider who claims that the BL (block list) is from SC ... edit: IIRC SC BLs are only active for 24 hours, which means that after 24 hours they should expire if it was ever listed through this anti-spam service. (If I Remember Correctly SpamCop Block Listings)
  23. at 4:30 CDT I get it too: it happens as soon as the [ Send spam Report(s) Now ] button is pressed. Edit: 30 minutes later it worked. No idea what's going on...
  24. while the IP address in the first link isn't in any BL listed in SC, Microsoft/Outlook seem to have a different view: <https://answers.microsoft.com/en-us/msoffice/forum/all/our-emails-being-blocked-for-no-reason-and-your/717fe0e7-a33d-4db3-ae0b-b89f98c1eb5c> I didn't check the other two though...
×
×
  • Create New...