[GRLUG] Mic check

Grand Rapids Linux Users Group grlug at grlug.org
Mon Feb 11 10:32:12 EST 2019


G-man, ya might not need to do that…

       spf=pass (google.com: best guess record for domain of grlug-bounces at grlug.org designates 74.208.251.96 as permitted sender) smtp.mailfrom=grlug-bounces at grlug.org
Return-Path: <grlug-bounces at grlug.org>
Received: from mail.grlug.org (mail.grlug.org. [74.208.251.96])
        by mx.google.com with ESMTPS id 79si1888931itv.114.2019.02.11.04.55.55
        (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
        Mon, 11 Feb 2019 04:56:07 -0800 (PST)
Received-SPF: pass (google.com: best guess record for domain of grlug-bounces at grlug.org designates 74.208.251.96 as permitted sender) client-ip=74.208.251.96;
Authentication-Results: mx.google.com;
       spf=pass (google.com: best guess record for domain of grlug-bounces at grlug.org designates 74.208.251.96 as permitted sender) smtp.mailfrom=grlug-bounces at grlug.org
Received: from vp.grlug.org (localhost.localdomain [127.0.0.1])
	by mail.grlug.org (Postfix) with ESMTP id B2C3D206FC;
	Mon, 11 Feb 2019 07:55:52 -0500 (EST)


Looks like maybe it just took a while for DNS to propagate.



cheers

-j





> On Feb 11, 2019, at 7:55 AM, Grand Rapids Linux Users Group <grlug at grlug.org> wrote:
> 
> Hi all,
> 
> On a plane to AL atm.  Will add SPF record as soon as I get a chance.
> 
> Godwin (since we can't see who). 😊
> 
> Get Outlook for Android <https://aka.ms/ghei36>
> From: grlug <grlug-bounces at grlug.org> on behalf of Grand Rapids Linux Users Group <grlug at grlug.org>
> Sent: Sunday, February 10, 2019 10:22:21 PM
> To: Grand Rapids Linux Users Group
> Subject: Re: [GRLUG] Mic check
> 
> Sender != From != Reply-To
> 
> munging is fine, and the reply to is "hardcoded" to go to the list. This is ideal.
> 
> SPF and DKIM notwithstanding this set up is tits.
> 
> Adding the "real" person to the "From" does not actually mean mailman is not the "Sender" and it does help to know who is saying what, but with all things considered, a little extra privacy never hurts.
> 
> sorry to be esoteric.
> 
> 
> 
> cheers
> 
> -j
> 
> 
> 
> 
> 
>> On Feb 10, 2019, at 10:15 PM, Grand Rapids Linux Users Group <grlug at grlug.org <mailto:grlug at grlug.org>> wrote:
>> 
>> On Sun, 10 Feb 2019, Grand Rapids Linux Users Group wrote:
>> 
>>> The "From" address on all of these is showing up as "Grand Rapids Linux
>>> Users Group <grlug at grlug.org <mailto:grlug at grlug.org>>" instead of having the original sender's
>>> name with the list as the Reply-To address.
>>> 
>> Including the original sender and not the list breaks it for some large
>> ISPs - i.e. if you include the original sender in the from headers a Yahoo
>> (AT*T) cannot reply to a reply sent from another Yahoo user.
>> 
>> Tool quite a while to figure that one out!
>> 
>> Lee
>> --
>> grlug mailing list
>> grlug at grlug.org <mailto:grlug at grlug.org>
>> https://shinobu.grlug.org/mailman/listinfo/grlug
> 
> --
> grlug mailing list
> grlug at grlug.org
> https://shinobu.grlug.org/mailman/listinfo/grlug

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://shinobu.grlug.org/pipermail/grlug/attachments/20190211/bc6bce8d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <https://shinobu.grlug.org/pipermail/grlug/attachments/20190211/bc6bce8d/attachment-0001.sig>


More information about the grlug mailing list