• WSarthurhixon

    WSarthurhixon

    @wsarthurhixon

    Viewing 12 replies - 1 through 12 (of 12 total)
    Author
    Replies
    • in reply to: USPS Barcode (2007) #1079479

      Thanks Hans, I will try that.

      Arthur

    • in reply to: CPU infinite loop on REPLY (2002) #731312

      A couple more things I can identify:
      1) the lockup occurs before:
      a) the message in the Outbox is created, and
      the original message is marked as “replied to”.
      2) the same message will lockup on two different machines
      running different OS and diferrent versions of Outlook
      (I pull my messages to two diffferent machines, leaving
      a copy on the server for 10 days).
      3) I have 7 different accounts at 2 different IPS’s.

      I anything like this happened in a “real” database, I would export/import the whole file 🙂

      Thanks for helping.

    • in reply to: CPU infinite loop on REPLY (2002) #731313

      A couple more things I can identify:
      1) the lockup occurs before:
      a) the message in the Outbox is created, and
      the original message is marked as “replied to”.
      2) the same message will lockup on two different machines
      running different OS and diferrent versions of Outlook
      (I pull my messages to two diffferent machines, leaving
      a copy on the server for 10 days).
      3) I have 7 different accounts at 2 different IPS’s.

      I anything like this happened in a “real” database, I would export/import the whole file 🙂

      Thanks for helping.

    • in reply to: CPU infinite loop on REPLY (2002) #731104

      Here are the few things that I know:
      1) it does not happen in the send process: Outllok locks up when the “send Immediately…” is turned off;
      2) it happens so often and randomly that I now save the text of my replies to the clipboard before cklicking the Send button;
      3) the format of the original message is not relevant: happens with both HTML and plain text;
      4) in all lockup cases, Task Manager will flag Outlook and all its open windows as “not responding”.
      5) in the lastest occurences on a brand new .PST under v2002, only e-mail messages and contacts were copied over from the old v2000 .PST, nothing else.

      I am going to try one more thing: re-create a new .PST (again) and copy messages to newly created sub-folders (rather than drag the message sub-folders across.

      Thanks for helping.

    • in reply to: CPU infinite loop on REPLY (2002) #731105

      Here are the few things that I know:
      1) it does not happen in the send process: Outllok locks up when the “send Immediately…” is turned off;
      2) it happens so often and randomly that I now save the text of my replies to the clipboard before cklicking the Send button;
      3) the format of the original message is not relevant: happens with both HTML and plain text;
      4) in all lockup cases, Task Manager will flag Outlook and all its open windows as “not responding”.
      5) in the lastest occurences on a brand new .PST under v2002, only e-mail messages and contacts were copied over from the old v2000 .PST, nothing else.

      I am going to try one more thing: re-create a new .PST (again) and copy messages to newly created sub-folders (rather than drag the message sub-folders across.

      Thanks for helping.

    • in reply to: Sync PSTs on 2 computers (2002) #725794

      Thank for the interest in my situation. That is: I own a small business and process my e-mail at work; I also pull my e-mail and make replies from home (small business means all-hours business :-). The two computers are not on the same network ( well, I’ll take that back: they are both connected to Internet via broadband).

      Thanks for helping.

    • in reply to: Sync PSTs on 2 computers (2002) #725795

      Thank for the interest in my situation. That is: I own a small business and process my e-mail at work; I also pull my e-mail and make replies from home (small business means all-hours business :-). The two computers are not on the same network ( well, I’ll take that back: they are both connected to Internet via broadband).

      Thanks for helping.

    • in reply to: SPAM Handling (2000 SR-1) #648432

      Great new!

      I like the idea of stopping spam from “known spam servers” (I mean not all those in the various black lists but only those that I personally verified as repeatedly being the originating server for spam received).

      Unfortunately Outlook chokes on IP addresses if set up in “when specific words appear in header fields”, it is completely unpredictable about what it does with that 🙁

      Can’t wait for Mike’s add-in for Outlook 🙂 It is going to be in the next WOPR, am I right?

      Anyway to get a beta copy if I promise to buy the real thing when it comes out (BTW I used to beta for WOPR a few years ago, but now I cannot commit so much time)?

      Thanks,

    • in reply to: SPAM Handling (2000 SR-1) #647916

      Tim, thanks for your reply, but…

      I have tried that approach and it is very frustrating. The main cause is that 90% of the originating mail domains are forged: the only reliable data is the sending IP as recorded in the headers by the receiving server. Positive identification on this IP results in a good personal black hole list, especially if no response comes from a report to the associated abuse@…. address.

      I have little confidence in Outlook’s Junk Senders handling. Just for kicks I tried it with a single domain name and Outlook’s rule came to read something like “Apply this rule after the message arrives, suspected to be junk e-mail or from ‘Junk Senders’ or Junk Senders’ or ‘Junk Senders’ or…or ‘Junk Senders’ etc. The number of ‘Junk Senders’ appears to be random according to my experiments.

      Let’s look at some “real” spam tools.

      Thanks,

    • in reply to: SPAM Handling (2000 SR-1) #647914

      Thanks for your interest Charlie.

      I do not like the commercial “black hole list” handling because most are so aggressive that many genuine e-mail get filtered out. On the other hand a personal “black hole list” created with care and verification using tools to chop down headers and screening whois at sites like SpamCop can be built up pretty accurately (I don’t mind a little investigative work to get my filters accurate). I estimate that 80-90% satisfactory filtering can be achieved with a personal black hole list.

      I like the idea of an “AI” filter like Mike is developing though and will certainly try it out. But I would also like the possibility of inserting my personal black hole list and hope that this is included in the “That’s in addition to filters you can create on any part of a message…” If so, I want to get my hands on Mike’s tool right away, maybe even help test it.

      Again thanks for your reply.

    • in reply to: SMTP Header (2000 SR-1) #642268

      I apologize if it looked like I was venting frustration over SPAM, because I was to some extent.

      The fact is that I designed a system where a VRFY was required to accept e-mail transaction resulting in billing consequences for telecom services. There were a few issues in service support but they were resolved promptly.

      I also think the a standard VRFY response (required) is a lot better than the current schemes with copyrighting poems to protect oneself from SPAM. Ther has to be a standards-based solution )SMTP is an extensible standard). I have not followed standards developments in the last several months: does anybody know about any developement regarding SPAM?

      I might check out Outlook Spy 🙂

      Arthur

    • in reply to: SMTP Header (2000 SR-1) #642107

      Thank you for your reply.

      I do understand the forging of headers. I also know that a message addressed to septic.tank@yahoo.com cannot be delivered to me. So I assume the BCC is used and not shown in the headers displayed by Outlook.

      I have a wish in the battle against SPAM which in my case has increased 200% in the last few months. I wish ISPs would offer an option to their subscribers by which the ISP server would not deliver any message for which the return path cannot be verified. That would take care of most SPAM as the FROM and REPLY-TO are also mostly forged.

      True, this would cause additional processing for the ISP servers, and a delay in message delivery, that is why I suggest this service as an option.

    Viewing 12 replies - 1 through 12 (of 12 total)