Jump to content

mrmaxx

Memberp
  • Posts

    820
  • Joined

  • Last visited

Posts posted by mrmaxx

  1. I'd like to second the request to parse the email as it goes, and not bail if a later received header has an IPv6 header in it.

    An email I just tried to submit should have been reported to the first received header, even though the second header contains an IPv6 header - you already ignore later headers due to possible forging, it seems like it might be possible to remove the IPv6 check for the potentially forged headers, and then these types of spams would be reported correctly.

    Thanks!

    +1 Googleplex! I just had a spam fail to parse for *exactly* this reason! Can we not just ignore IPV6 until such time as they start handing them out? Of course, you should continue working on the IPV6 support code, but don't break parsing just because one INTERNAL handoff in IPV6.

  2. Ok. Problem is resolved... turns out that Petzl got it right... :) The user had subscribed to a pay service that handles keeping antivirus, etc up-to-date and when I called that service they walked me through how to fix it so the computer would boot back up normally... had to remove a driver file that their software installed and once that happened, we were good to go... :D

    'Preciate it!

  3. One of my users at work asked me to look at his machine from home which is running Windows Vista Home Premium. It was working fine until Tuesday night / Wednesday when it got an update from Microsoft. After that, it rebooted and now it will only give a blue screen at boot with error 0x0000007E. Google search doesn't turn up much helpful. I've got the original install media, but would rather not reinstall Windows if I can help it.

    This is remarkably similar to a problem that Windows XP users are having with KB977165. :(

    Anyone here know how to fix this problem on Vista machines? I'd really rather avoid reloading the whole computer. I just did that for a machine at work yesterday and it took all day to load Windows and get all the updates!

  4. FWIW, Don D'Minion has given his blessing to SpamSource. Of course, it's still a good idea to double-check everything before hitting "send reports." Still, I thought I'd pass it along.

    Moderator edit 12-3-09 - Actually Don has NOT given his blessing to any third party tool that would attempt to fix the problem with Outlook's failure to maintain proper headers, but he did provide a list of third party tools that try to address the problem. see Here is the boilerplate on Outlook...

    Note: discussion that follows has not been edited, but this initial post was edited to avoid "a misrepresentation of what was actually said" - dbiel -

  5. Hi mrmaxx. I suspect anything, touched by Outlook and submitted by mail, will be er ... suspect but I think you will have to ask a deputy. The door was certainly 'left open' for add-ons/add-ins but AFAIK there has been no confirmation of specifics. Unless anyone comes up with a better idea, I suggest that you ask.

    I can certainly confirm that the headers - as seen in the two reports you gave links for - are, character-by-character from the text of the "View entire message" pages pasted into Excel, precisely the same except the Outlook case has two extra (non-critical) lines:

    • X-Vipre-Scanned: 0007FA8A00150D0007FBD7-TDI
    • Bcc:

    Deputies address is deputies[at]admin.spamcop.net If SpamSource 4 is confirmed as an 'authorised' add-on to Outlook 2007 for mailed submissions, it would be appreciated if you could pass the word on with a further post 'here' :) . Or if it's not :( .

    Yeah... I've got a new antivirus I'm testing. It's Vipre from SunbeltSoftware. I'm not sure where that BCC line came from, but... anyway, I'll copy my post and email it to the deputies for review. I suspect they will want more than one sample before giving SpamSource their blessing. :)

  6. Question -- I've got SpamSource 4.0.10.98 installed on my Outlook 2007. Does that fix the problem or is it still forbidden to submit via email from Outlook?

    Since I receive my work email on another computer that doesn't use Outlook as well as my main machine which *does* use OL2007, I can submit from that machine, if necessary, but it would be nice to be able to submit from my desk at work. :-)

    Note: I have compared the results of two spam messages I received at work and initially used SpamSource to forward to SpamCop from my Outlook 2007. At a glance, the results are identical. I *did* cancel the ones I forwarded using SpamSource to be sure I did not violate any rules, however I did end up reporting them using "forward as an attachment" from my linux box at home.

    Further, reports can be reviewed as follows -- Outlook version (NOT reported): http://www.spamcop.net/sc?id=z3315769724z3...f7f64272f63645z

    Non-Outlook version: http://www.spamcop.net/sc?id=z3315804596z3...ca12e2a134942ez

    I'd give you the other spam, but I cancelled it before I parsed it so SpamCop does not have any traces of it from the Outlook version.

  7. I've been having issues for a couple of weeks receiving messages dated in the year 2038 which never seem to be downloaded. I simply delete them and things begin working again. I have also had intermittant times when I get an "Invalid login" error in the POP config. Simply hitting the modify button (no changes made) removes the error message and starts mail flowing again.

    Neither of those two things describes my issue. This is mostly normal mailing list traffic which is being sent to my Yahoo account. I'm not getting an "invalid login" error either. I did get a message, something like "error 4" one time, but I had just reset my password on both Yahoo and SpamCop so there was a decent chance I hadn't gotten the passwords synchronized yet.

  8. FYI, it appears Yahoo has broken things again. I've got a bunch of email in my Yahoo account. I don't see any errors in my pop list, but it also doesn't appear to be downloading Yahoo mail any more either. I'm still on Yahoo "classic" but they've changed things around again. Probably in order to get us to pony up the $20(US) for "enhanced" access (including pop access.) :(

  9. Yahoo changed their interface over the weekend, and all the tools that allow POPing from Yahoo accounts are affected. We will be testing solutions over the next few days, and hope to have a fix for both this and Hotmail Live accounts soon.

    Kewl. It does appear to be b0rken at this time, unfortunately. I have a bunch of email in my Yahoo account, and I guess I'm just going to have to read it on Yahoo's site for now. <_<

  10. Recently I got in a hurry and didn't pay attention to what I was doing and whitelisted & released a bunch of spam from my held mail folder. I'm slowly deleting the bad whitelist entries, but it would be nice if SpamCop would "auto-clean" my whitelist or at least give me the OPTION to do it when reporting spam. Heck, even if I had to report 'em one-at-a-time, it would be worth it if there were a checkbox to "remove this entry from the personal whitelist" or something?

    Just a thought. It would help people like me who get in a hurry and whitelist a whole bunch of spam. :)

    Another idea would be a "filter" in the whitelist to show all the "new" whitelist entries for the past X days (say 30) for those of us who have done stupid stuff like this so we don't have to wait for spam to get through on the whitelist.

    Thanks

    Maxx

  11. ...You mean something like Richard's post, above?

    35445[/snapback]

    Nooo, not really. :D I mean a real "Oops. We see the problem, we know where the problem is, should be fixed in a bit." That was just a "Oops. I can verify the problem. Bug Report filed." I do that all the time with MY users, so I know exactly what that means... it means "I've informed someone who can actually DO something about the problem and it'll get fixed when they get around to fixing it."

    What I would recommend doing is backing out the changes until you can fix it so that there are no unintended consequences, such as those that we are seeing. That's just my 2¢ though. <_<

  12. ...Historically, we discover that things have been fixed when they start behaving "properly." We almost never get progress reports. Personally, I prefer having something "fixed" in, say, seven days but without progress reports than to have them fixed in, say, four weeks but with timely progress reports. :) <g>

    35441[/snapback]

    True... Then again, it would be "nice" to have someone (say Julian or Don D'Minion) poke their head in here to say "Oops. Sorry. Should be fixed shortly" or something. :-) Oh, well... as long as it's fixed eventually. Then again, I do believe in the old aphorism, "The Squeaky Wheel Gets the Grease!" so maybe if we keep the heat on The Powers That Be, (not too much heat... just a friendly reminder once in awhile) it'll get pushed higher on the priority list to get us to shut up about it! ;)

  13. This behavior is considered to be a bug by at least two Deputies, and has been reported as such.

    35400[/snapback]

    And has anyone heard back about a possible ETA on when it'll be fixed or at least a user-preference set up in the SpamCop configs? This is getting ridiculous... I'm VERY concerned that I'll accidentally send a user-defined report to someone who doesn't need it. Matter of fact, I'm pretty sure I probably have already done so, despite my best intentions not to do so.

×
×
  • Create New...