Jump to content

Argus

Members
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Argus

  • Rank
    Newbie
  1. Argus

    Piracy reporting

    I usually supplement the Spamcop report on such things with a direct report to the FDA, Adobe, whatever. I also leave the Cyveillance box checked and note the other report in the comments box.
  2. Argus

    MASSIVE LAWSUIT AGAINST SCOTT RICHTER...

    The usual term for that is confirmed opt-in, not double opt-in. When I see "double-opt-in", I am reminded of web forms that ask for the same email address to be entered twice.
  3. Well, from the earlier comments, it sounds like any mailserver with Postini in front of it produces headers much like: Received: from psmtp.com ([12.158.38.185]) by alias.acm.org (ACM Email Forwarding Service) with SMTP id COB73880 for <argus[at]acm.org>; Sat, 08 May 2004 01:13:01 -0400 Received: from source ([206.14.107.103]) by exprod7mx45.postini.com ([12.158.38.251]) with SMTP; Fri, 07 May 2004 22:13:00 MST The question is whether adding code in the parser to recognize such a pair of Received lines would be easier than doing a separate waiver for each of Postini's customers. Note that the 12.158.38.251 MX host does seem to be shared with arkansas.net and presumably others, so the Mailhosts code could theoretically recognize a Postini customer before it even sends the mail.
  4. I encountered the same thing just now when I tried to add the Mailhosts records for my ACM forwarding address (with the domain acm.org). I submitted a waiver request, but I wonder whether it might be practical for them to add general recognition of Postini spam filtering. ACM doesn't seem to use Postini spam filtering quite yet (http://spam.acm.org/public/spamapp/faq/postini_transf.html), but they do seem to be getting email through those servers already.
×