• Patchmanagement.org listserve moving to a new location

    Home » Forums » Newsletter and Homepage topics » Patchmanagement.org listserve moving to a new location

    Author
    Topic
    #345174

    After trying to deal with all the dkim/dmarc listserve issues, we’re moving the patchmanagement.org listserve to a new location:  Google Groups.  The
    [See the full post at: Patchmanagement.org listserve moving to a new location]

    Susan Bradley Patch Lady/Prudent patcher

    4 users thanked author for this post.
    Viewing 6 reply threads
    Author
    Replies
    • #345187

      You’re going through all this because you’re not sure how DKIM/DMARC records work?

    • #345193

      Well that’s too bad.  It was useful and informative while it lasted.  But I, as well as many others that I know, with concerns about security and patch management of Windows systems lead a Google free life (or as close to one as we can get).

      Security and privacy are two sides of the same coin.

      -J

      • #345204

        You can sign up without a google profile.  I have and did.   And yes I know how Dmarc and Dkim work.  The problem is that with the current listserve software it adds dkim headers to the sent emails.  Every other email client on the planet handles emails differently and won’t handle two or more dkim headers.   So when an email is sent from you there’s one dkim header, then when it goes through the listserve software there’s another.   Google groups is the only one that pulls off the existing headers and rewrites them so that the headers are clean and do not have multiple headers so that they will get through.  Trust me, I have a single listserve set up so that it will go through all dkim requirements and you cannot tell who the email is being sent by.

        Susan Bradley Patch Lady/Prudent patcher

        1 user thanked author for this post.
        • #345369

          Google groups is the only one that pulls off the existing headers and rewrites them so that the headers are clean and do not have multiple headers so that they will get through. Trust me, I have a single listserve set up so that it will go through all dkim requirements and you cannot tell who the email is being sent by.

          Mailman also handles this quite well; I use it on the lists I run. You can configure it (easily) to rewrite the headers to avoid this particular issue, and you can do it easily through the management interface.

          • #345430

            It has to totally rewrite/strip off the headers and only put in the mail server header.  Can you show me exactly where mailman does this?  Most can add dkim headers, no one else that I’m aware of strips off the header file of what dkim is there and replaces it with the one from the mailing server.  All of the vendors I contacted said “oh you don’t want to do that”.

            Susan Bradley Patch Lady/Prudent patcher

            • #345440

              On the General Options page, setting the “from_is_list” parameter to “Mung From” resolves this issue (for my lists).

              The “first_strip_reply_to” parameter gets rid of the header entirely; I’ve not had to use that option.

              My apologies if I’ve misunderstood the original issue or if these settings won’t do the trick for you.

            • #345457

              That changes the reply to header.  That I can do.  This is specifically changing the DKIM headers (a sub header) in the mailing.  All listserves can change it so that the email is from the list.  What many don’t do is totally strip and rewrite the dkim headers.  Most let the dkim header be added.  Then the other mail server reacts to multiple dkim headers and totally freaks out and blocks them as spam.

              Susan Bradley Patch Lady/Prudent patcher

            • #345459

              For whatever reason, I’m not getting bounces due to multiple DKIM headers. I’ll review a few messages when I get home to see if these settings result in a single DKIM header or if my subscriber base just has more DKIM-aware (or DKIM-blind) mailservers.

    • #345213

      An admittedly biased report… as Susan says, this is the firehouse, especially for anyone who’s in charge of an organization’s machines.

    • #345378

      I successfully signed up at “https://groups.google.com/forum/#!forum/patchmanagement. I can see Susan’s post ” if you are reading this you got to the right spot.” I do not have a patchmanagement.org account. Do I need to sign up for one to read future posts? How does this work? thank you for your time! ASKWOODY is the greatest!!!

    • #345603

      Note that you can subscribe by sending an email to patchmanagement+subscribe@googlegroups.com

      No need to have a Google account.

      As for munging, one of our groups recently tried the option available in Mailman to wrap the message in an outer wrapper. It caused many problems with some only able to see postings as attachments and others like myself seeing loads of headers in the messages. We have not tried the first option yet, to munge the ‘from’ address but that probably works a bit better. The ‘wrap’ option most definitely does not.

       

    • #345606

      This link below appears to be correct, it will pop-up with a box to enter the e-mail address you want to use to subscribe:

       

      https://groups.google.com/forum/#!forum/patchmanagement/join

       

    • #345658

      Hello,
      I have a gmail account, but my Woody Plus account is based on a different email.
      Does it matter that I use a different email?
      Also, you indicated that using a google account gives one access to the “web interface.” What additional resources does that give us? For example, will I be able to search through past postings with the web interface? Seems to me that would be important if I was a new member of patchmanagement.org.
      Thanks!
      Norio

    Viewing 6 reply threads
    Reply To: Patchmanagement.org listserve moving to a new location

    You can use BBCodes to format your content.
    Your account can't use all available BBCodes, they will be stripped before saving.

    Your information: