Jump to content

turetzsr

Forum Admin
  • Posts

    5,460
  • Joined

  • Last visited

Posts posted by turetzsr

  1. The search as you describe it actually gives the error message:

    <snip>

    Hi, William,

    ...Oops, I'm sorry, I should have been more specific: you seem to have used the link labeled "Search" at the top right, under the graphic image, between the links labeled "Help" and "Members," right? I was referring to the search box tool nearer the very top of the screen, under the links in white labeled "SPAMCOP HOME" and "SPAMCOP FAQ," between the white "button" labeled "Search for -->" and the blue button labeled "GO," as described above by Steve S (Farelf).

  2. <snip>

    I copy and paste it into spamcop, and it says it has no body.

    <snip>

    ...Please forgive me if this is an entirely stupid question but, taking what you wrote at face value, I can not resist inquiring: did you insert a blank line at the end of those headers and then also paste in the spam body (or, if the actual spam body was empty, paste in some text like "[no body]")?
  3. Forgive me if the way I report is wrong

    <snip>

    ...Nope, that's right -- you're using Don's 84376[/snapback] Option 1. The only reason what you are doing seems different is that you just added the detail relevant to Outlook Express that Don describes more generally as "Copy/Paste the full (raw) headers and text into the SpamCop web form."
  4. ...Proposed modifications:

    • Options 2 and 3 are not permitted for Microsoft Outlook e-mails. Ref: SpamCop FAQ entry labeled "Forwarding "As Attachment" from Outlook - no longer allowed!! 6 April 2009."
    • Option 1: If you use the standard reporting box, leave a blank line between the headers and the spam text (body).
    • Option 2: leave a blank line between the headers and the spam text (body).
    • Option 3: per SpamCop FAQ entry "How do I submit spam via email?" "You should not exceed 20 spams attached to a submission. The maximum size for the overall submission must not exceed 50 KB."

    ...Please do not take these proposed modifications as authoritative unless validated by one of the SpamCop staff.

  5. It has been over 90 days.

    <snip>

    ...Actually, it's only been just short of a month since the last update telling us that the new release is due "in a couple of months:"
    <snip>

    Changing the SpamCop code so it will handle IPv6 headers is a big challenge. IPv6 support is the focus of the new release, which is due out in a couple of months.

  6. All gets a bit to complicated for me I'm afraid.
    ...In that case, please just delete them. No one here (that has any sense) will think the less of you! :) <g>
    I can't be the only one getting these daily now. :-

    ...Probably not but since nothing can be done about it right now it's a moot point how many people are experiencing it. :( <frown> But, possibly good news: see SpamCopAdmin Don D'Minion's post in SpamCop Forum article "/dev/null'ing report" last sentence. :) <g> OTOH, we've heard that, before. :( <frown>
  7. Yes, those were the points - "manual" reports can be risky, particularly for the novice, whereas SpamCop reporting is not.

    <snip>

    ...Ah, okay, thanks for clarifying, Steve. So would you agree that the risk can be reduced by using the SpamCop parser to the degree possible to determine where to send the reports, then canceling the parse? The only thing that I can see that might negate the value of such a strategy in this case is that the IPv6 addresses would have to be removed so that the parse will work and that might remove an important part of the internet headers for the parser, causing it to find the wrong abuse address(es)!
  8. Saw those, but :-

    "that would be an irresponsible thing to recommend "

    so assumed it wasn't what we should be doing. ;)

    <snip>

    ..Yes but I don't know what Steve (Farelf) meant by that -- hopefully he'll drop by soon to explain. All I can think of that he might have meant is:
    • Care must be taken to ensure you are manually reporting to the correct abuse address(es) for the correct source(s) of the spam.
    • Care must be taken to avoid sending a manual report to a spammer or someone friendly to the spammer or to spamming in general.

  9. <snip>

    spam received via the backup will need header mangling in order to be reported, and spam received ‘directly’ may need header mangling. (Also, the primary does greylisting; yahoo.com retries a lot, but most just… go away.)

    <snip>

    ...If you mean by SpamCop users: don't do that! For more information, please see SpamCop FAQ (links to which are available near the top left of all SpamCop Forum pages) items labeled "Material changes to spam," "Material changes to spam - Updated!" and "What if I break the rule(s)?"
  10. Is it typical for Hotmail to keep a block up for two weeks or is that just the treatment they give repeat offenders?

    <snip>

    ...There may be those here who might have evidence from which they could speculate but if you wish an authoritative answer you'd be more likely to get one from Hotmail support. On the other hand, since I suspect you are unlikely to have a question posed to them answered by someone with real knowledge, speculation might be the best you can get. :) <smile>
  11. <snip>

    Although, I'm probably going to get yelled at with something like "We told you, you're supposed to use those at your own risk. We don't endorse them, nor do we test them." <_< Admin don't like being asked about products that aren't their own.

    ...Ah, but you aren't (shouldn't be) asking them about a different product, you are asking them whether they tested the SpamCop parser with a third-party tool. Okay, I guess that it's conceivable that they might be testy about implicitly being expected to test with another tool. :) <g>

    Dear Ellen and Wazoo:

    <snip>

    ...Neither Ellen nor Wazoo is here. I'd suggest that you write to the SpamCop Deputies (FYI, Ellen used to be one but she left a while ago) at deputies[at]admin.spamcop.net.
  12. <snip>

    My comments on the "right way" and the "wrong way" are based on one assumption about the parsing process, namely that the process works from the recipient back towards the sender.

    <snip>

    ...The assumption is, from what I understand, correct. What we don't know is whether that fact allows us to conclude that it is necessarily feasible and "easy" for the parser to ignore all IPv6 addresses that appear prior to the point it decides that it has found the location at which it can stop trusting the headers. I think that is not an unreasonable conclusion but it is, nevertheless, a conclusion the validity of which we will never know because the SpamCop engineers won't ever reveal the answer to us. And since it's their product, they get to define the rules, so I for one feel unworthy to challenge it and can't imagine that anyone else outside the SpamCop staff circle is able to do so for certain, either.
  13. <snip>e. Posts are currently limited to 1k in size. HTML is not enabled. Graphics are not allowed. (If needed, host them somewhere and provide a URL, NOT an img tag.)
    ...Might it be appropriate to add that the poster should not assume that readers will visit their link to see the image (since clicking on unsolicited links from someone you don't know is, generally, not a good idea)?
  14. <snip>

    turetzsr, I think you have connections with Julian. Can you pass on the congratulations?

    ...Actually, no, everyone here has the same connections with SpamCop staff that I have -- you can just send an e-mail to deputies[at]admin.spamcop.net and a SpamCop deputy will (hopefully) let the relevant folks know.
×
×
  • Create New...