From Michael.Paoli@cal.berkeley.edu  Sat Jan 12 17:32:41 2019
From: Michael.Paoli@cal.berkeley.edu (Michael Paoli)
Date: Sat, 12 Jan 2019 17:32:41 -0800
Subject: [BALUG-Test] VERP (testing VERP)
Message-ID: <20190112173241.90882w8o4b1gmu0w@webmail.rawbw.com>

/etc/mailman/mm_cfg.py

added (at least for now):
# Set this Yes to activate VERP probe for disabling by bounce
# VERP_PROBES = No
VERP_PASSWORD_REMINDERS = Yes
VERP_PERSONALIZED_DELIVERIES = Yes
VERP_DELIVERY_INTERVAL = 1
VERP_CONFIRMATIONS = Yes

For better or worse with the installed Mailman version,
that's only globally configurable, not per-list.

Let's see if that helps nail some of the annoying bounces /
auto-responders where source isn't otherwise identifiable ...

Here's a typical example I get from sending to:
balug-announce@lists.balug.org
... but trimming headers ("only" removing those that offer no clue as to the
email address that "bounced" / auto-responded):

Received: from o9.email.freshdesk.com (o9.email.freshdesk.com. [167.89.69.3])
         by mx.google.com with ESMTPS id  
y6-v6si9038821ybg.2.2018.12.18.03.48.21
         for <michael.paoli@cal.berkeley.edu>
         (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
         Tue, 18 Dec 2018 03:48:21 -0800 (PST)
Received: by filter0053p1iad2.sendgrid.net with SMTP id  
filter0053p1iad2-28863-5C18DE84-1F
         2018-12-18 11:48:20.998500814 +0000 UTC m=+62908.201055891
Received: from freshdesk.com (mail-us1.freshemail.io [34.198.193.174])
	by ismtpd0024p1mdw1.sendgrid.net (SG) with ESMTP id PLtTaOlxSBi7mz0H6ryrVQ
	for <michael.paoli@cal.berkeley.edu>; Tue, 18 Dec 2018 11:48:20.917  
+0000 (UTC)
Received: from ec2-54-172-69-206.compute-1.amazonaws.com (EHLO  
freshdesk.com) ([54.172.69.206])
           by smtpout.freshdesk.com (Freshworks SMTP Server) with  
ESMTPA ID 520262660.
           for <michael.paoli@cal.berkeley.edu>;
           Tue, 18 Dec 2018 11:48:20 +0000 (UTC)
Date: Tue, 18 Dec 2018 11:48:21 +0000 (UTC)
From: Team at TruBrain <team@trubrain.com>
Reply-To: Team at TruBrain <team@trubrain.com>
To: michael.paoli@cal.berkeley.edu
Message-ID:  
<5c18de846f831_23f74b377d0382369f0.sidekiq-email-2x1@notification.freshdesk.com>
Subject: Ticket Received - [BALUG-Announce] BALUG: No December meeting!, next
  meeting dates: 2019-01-15 2019-02-19 ...
Content-Type: multipart/alternative;
  boundary="--==_mimepart_5c18de8475f9d_23f74b377d038237079";
  charset=UTF-8
Content-Transfer-Encoding: 7bit
sent-on: 2018-12-18 11:48:20 +0000
Auto-Submitted: auto-generated
X-Auto-Response-Suppress: DR, RN, OOF, AutoReply

----==_mimepart_5c18de8475f9d_23f74b377d038237079
Content-Type: text/plain;
  charset=UTF-8
Content-Transfer-Encoding: 7bit

   Dear Michael Paoli,  Thank you for messaging us here at TruBrain!  
We would like to acknowledge that we have received your request and a  
ticket has been created.  We try to be responsive and will get back to  
you as soon as we can!      Thank you for your patience.  Have a great  
day, TruBrain Support Team



----==_mimepart_5c18de8475f9d_23f74b377d038237079
Content-Type: text/html;
  charset=UTF-8
Content-Transfer-Encoding: 7bit

<div style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;  
font-size:13px;">

<div dir="ltr"><p>Dear Michael Paoli,<br><br>Thank you for messaging  
us here at TruBrain! We would like to acknowledge that we have  
received your request and a ticket has been created.</p><p>We try to  
be responsive and will get back to you as soon as we  
can!<br></p><p><br></p><p>Thank you for your patience.<br><br>Have a  
great day,<br>TruBrain Support Team</p>
</div>




	<br/>



<span title="fd_tkt_identifier" style='font-size:0px;  
font-family:"fdtktid"; min-height:0px; height:0px; opacity:0;  
max-height:0px; line-height:0px; color:#ffffff'>114761:553856</span>

</div>
----==_mimepart_5c18de8475f9d_23f74b377d038237079--



From Michael.Paoli@cal.berkeley.edu  Sat Jan 12 17:43:09 2019
From: Michael.Paoli@cal.berkeley.edu (Michael Paoli)
Date: Sat, 12 Jan 2019 17:43:09 -0800
Subject: [BALUG-Test] Fwd: VERP (testing VERP)
Message-ID: <20190112174309.20422fdq7ikg3af4@webmail.rawbw.com>

And again, after bouncing mailman ...

----- Forwarded message from Michael.Paoli@cal.berkeley.edu -----
     Date: Sat, 12 Jan 2019 17:32:41 -0800
     From: "Michael Paoli" <Michael.Paoli@cal.berkeley.edu>
  Subject: VERP (testing VERP)
       To: BALUG-Test <balug-test@lists.balug.org>

/etc/mailman/mm_cfg.py

added (at least for now):
# Set this Yes to activate VERP probe for disabling by bounce
# VERP_PROBES = No
VERP_PASSWORD_REMINDERS = Yes
VERP_PERSONALIZED_DELIVERIES = Yes
VERP_DELIVERY_INTERVAL = 1
VERP_CONFIRMATIONS = Yes

For better or worse with the installed Mailman version,
that's only globally configurable, not per-list.

Let's see if that helps nail some of the annoying bounces /
auto-responders where source isn't otherwise identifiable ...

Here's a typical example I get from sending to:
balug-announce@lists.balug.org
... but trimming headers ("only" removing those that offer no clue as to the
email address that "bounced" / auto-responded):

Received: from o9.email.freshdesk.com (o9.email.freshdesk.com. [167.89.69.3])
         by mx.google.com with ESMTPS id  
y6-v6si9038821ybg.2.2018.12.18.03.48.21
         for <michael.paoli@cal.berkeley.edu>
         (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
         Tue, 18 Dec 2018 03:48:21 -0800 (PST)
Received: by filter0053p1iad2.sendgrid.net with SMTP id  
filter0053p1iad2-28863-5C18DE84-1F
         2018-12-18 11:48:20.998500814 +0000 UTC m=+62908.201055891
Received: from freshdesk.com (mail-us1.freshemail.io [34.198.193.174])
	by ismtpd0024p1mdw1.sendgrid.net (SG) with ESMTP id PLtTaOlxSBi7mz0H6ryrVQ
	for <michael.paoli@cal.berkeley.edu>; Tue, 18 Dec 2018 11:48:20.917  
+0000 (UTC)
Received: from ec2-54-172-69-206.compute-1.amazonaws.com (EHLO  
freshdesk.com) ([54.172.69.206])
           by smtpout.freshdesk.com (Freshworks SMTP Server) with  
ESMTPA ID 520262660.
           for <michael.paoli@cal.berkeley.edu>;
           Tue, 18 Dec 2018 11:48:20 +0000 (UTC)
Date: Tue, 18 Dec 2018 11:48:21 +0000 (UTC)
From: Team at TruBrain <team@trubrain.com>
Reply-To: Team at TruBrain <team@trubrain.com>
To: michael.paoli@cal.berkeley.edu
Message-ID:  
<5c18de846f831_23f74b377d0382369f0.sidekiq-email-2x1@notification.freshdesk.com>
Subject: Ticket Received - [BALUG-Announce] BALUG: No December meeting!, next
  meeting dates: 2019-01-15 2019-02-19 ...
Content-Type: multipart/alternative;
  boundary="--==_mimepart_5c18de8475f9d_23f74b377d038237079";
  charset=UTF-8
Content-Transfer-Encoding: 7bit
sent-on: 2018-12-18 11:48:20 +0000
Auto-Submitted: auto-generated
X-Auto-Response-Suppress: DR, RN, OOF, AutoReply

----==_mimepart_5c18de8475f9d_23f74b377d038237079
Content-Type: text/plain;
  charset=UTF-8
Content-Transfer-Encoding: 7bit

   Dear Michael Paoli,  Thank you for messaging us here at TruBrain!  
We would like to acknowledge that we have received your request and a  
ticket has been created.  We try to be responsive and will get back to  
you as soon as we can!      Thank you for your patience.  Have a great  
day, TruBrain Support Team



----==_mimepart_5c18de8475f9d_23f74b377d038237079
Content-Type: text/html;
  charset=UTF-8
Content-Transfer-Encoding: 7bit

<div style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;  
font-size:13px;">

<div dir="ltr"><p>Dear Michael Paoli,<br><br>Thank you for messaging  
us here at TruBrain! We would like to acknowledge that we have  
received your request and a ticket has been created.</p><p>We try to  
be responsive and will get back to you as soon as we  
can!<br></p><p><br></p><p>Thank you for your patience.<br><br>Have a  
great day,<br>TruBrain Support Team</p>
</div>




	<br/>



<span title="fd_tkt_identifier" style='font-size:0px;  
font-family:"fdtktid"; min-height:0px; height:0px; opacity:0;  
max-height:0px; line-height:0px; color:#ffffff'>114761:553856</span>

</div>
----==_mimepart_5c18de8475f9d_23f74b377d038237079--


----- End forwarded message -----



From Michael.Paoli@cal.berkeley.edu  Sat Jan 12 17:52:16 2019
From: Michael.Paoli@cal.berkeley.edu (Michael Paoli)
Date: Sat, 12 Jan 2019 17:52:16 -0800
Subject: [BALUG-Test] a VERP testin' we will go ...
Message-ID: <20190112175216.74845wcymnfv9qo8@webmail.rawbw.com>

Hmmm... another test ...

/etc/mailman/mm_cfg.py

added (at least for now):
# Set this Yes to activate VERP probe for disabling by bounce
# VERP_PROBES = No
VERP_PASSWORD_REMINDERS = Yes
VERP_PERSONALIZED_DELIVERIES = Yes
VERP_DELIVERY_INTERVAL = 1
VERP_CONFIRMATIONS = Yes



From Michael.Paoli@cal.berkeley.edu  Sat Jan 12 17:58:41 2019
From: Michael.Paoli@cal.berkeley.edu (Michael Paoli)
Date: Sat, 12 Jan 2019 17:58:41 -0800
Subject: [BALUG-Test] VERP ...
Message-ID: <20190112175841.81662j5q5jrstikg@webmail.rawbw.com>

Maybe test further at some other time, ... but VERP disabled
again for now:

/etc/mailman/mm_cfg.py:
# 2019-01-12 Tried enabling VERP ... then disabled it again,
# with the VERP enabled, postings make it to the archive, but don't seem
# to be getting successfully sent?
## Set this Yes to activate VERP probe for disabling by bounce
## VERP_PROBES = No
#VERP_PASSWORD_REMINDERS = Yes
#VERP_PERSONALIZED_DELIVERIES = Yes
#VERP_DELIVERY_INTERVAL = 1
#VERP_CONFIRMATIONS = Yes



From Michael.Paoli@cal.berkeley.edu  Sun Dec 15 15:11:33 2019
From: Michael.Paoli@cal.berkeley.edu (Michael Paoli)
Date: Sun, 15 Dec 2019 07:11:33 -0800
Subject: [BALUG-Test] And now IPv4 email/SMTP/lists should be originating
	from the new	IPv4 IP
Message-ID: <20191215071133.98051vtaopi13sqs@webmail.rawbw.com>

And now IPv4 email/SMTP/lists should be originating from the new IPv4 IP,
traffic may be via IPv4 or IPv6 (no change on the IPv6), but at least
for that traffic going over IPv4 ...



From Michael.Paoli@cal.berkeley.edu  Sun Dec 15 15:37:05 2019
From: Michael.Paoli@cal.berkeley.edu (Michael Paoli)
Date: Sun, 15 Dec 2019 07:37:05 -0800
Subject: [BALUG-Test] And now IPv4 email/SMTP/lists should
	be	originating from the new	IPv4 IP
In-Reply-To: <20191215071133.98051vtaopi13sqs@webmail.rawbw.com>
References: <20191215071133.98051vtaopi13sqs@webmail.rawbw.com>
Message-ID: <20191215073705.588520deag7dqkis@webmail.rawbw.com>

And one more test, with IPv6 temporarily disabled, to force IPv4 ...

> From: "Michael Paoli" <Michael.Paoli@cal.berkeley.edu>
> Subject: [BALUG-Test] And now IPv4 email/SMTP/lists should be  
> originating from the new	IPv4 IP
> Date: Sun, 15 Dec 2019 07:11:33 -0800

> And now IPv4 email/SMTP/lists should be originating from the new IPv4 IP,
> traffic may be via IPv4 or IPv6 (no change on the IPv6), but at least
> for that traffic going over IPv4 ...



From Michael.Paoli@cal.berkeley.edu  Sun Dec 15 15:44:52 2019
From: Michael.Paoli@cal.berkeley.edu (Michael Paoli)
Date: Sun, 15 Dec 2019 07:44:52 -0800
Subject: [BALUG-Test] And now IPv4 email/SMTP/lists
	should	be	originating from the new	IPv4 IP
In-Reply-To: <20191215073705.588520deag7dqkis@webmail.rawbw.com>
References: <20191215071133.98051vtaopi13sqs@webmail.rawbw.com>
 <20191215073705.588520deag7dqkis@webmail.rawbw.com>
Message-ID: <20191215074452.11984flhqow16lus@webmail.rawbw.com>

Drats ... didn't actually go via IPv6 ... will test more later.

> From: "Michael Paoli" <Michael.Paoli@cal.berkeley.edu>
> Subject: Re: [BALUG-Test] And now IPv4 email/SMTP/lists should  
> be	originating from the new	IPv4 IP
> Date: Sun, 15 Dec 2019 07:37:05 -0800

> And one more test, with IPv6 temporarily disabled, to force IPv4 ...
>
>> From: "Michael Paoli" <Michael.Paoli@cal.berkeley.edu>
>> Subject: [BALUG-Test] And now IPv4 email/SMTP/lists should be  
>> originating from the new	IPv4 IP
>> Date: Sun, 15 Dec 2019 07:11:33 -0800
>
>> And now IPv4 email/SMTP/lists should be originating from the new IPv4 IP,
>> traffic may be via IPv4 or IPv6 (no change on the IPv6), but at least
>> for that traffic going over IPv4 ...



From Michael.Paoli@cal.berkeley.edu  Tue Dec 17 11:00:24 2019
From: Michael.Paoli@cal.berkeley.edu (Michael Paoli)
Date: Tue, 17 Dec 2019 03:00:24 -0800
Subject: [BALUG-Test] And now IPv4 email/SMTP/lists
	should	be	originating from the new	IPv4 IP
In-Reply-To: <20191215074452.11984flhqow16lus@webmail.rawbw.com>
References: <20191215071133.98051vtaopi13sqs@webmail.rawbw.com>
 <20191215073705.588520deag7dqkis@webmail.rawbw.com>
 <20191215074452.11984flhqow16lus@webmail.rawbw.com>
Message-ID: <20191217030024.27214ws9dd58x24g@webmail.rawbw.com>

And yet another test ... ought be a "good" one this time.  ;-)
I *temporarily* disabled the IPv6 IPs - to force IPv4 (yes, there
are other ways ... but for the relatively quick-and dirty ...
also still testing and flushing out any minor issues that may
remain in the full
/etc/network/interfaces ifup/ifdown functionality).

Also, relevant SPF records updated (alas, had dropped TTLs, and queued
the changes, but forgot to get 'em in earlier) ... so that part
of it ought work now too (and might otherwise prevent delivery,
and rightfully so - especially with -all).

> From: "Michael Paoli" <Michael.Paoli@cal.berkeley.edu>
> Subject: Re: [BALUG-Test] And now IPv4 email/SMTP/lists should  
> be	originating from the new	IPv4 IP
> Date: Sun, 15 Dec 2019 07:44:52 -0800

> Drats ... didn't actually go via IPv6 ... will test more later.
>
>> From: "Michael Paoli" <Michael.Paoli@cal.berkeley.edu>
>> Subject: Re: [BALUG-Test] And now IPv4 email/SMTP/lists should  
>> be	originating from the new	IPv4 IP
>> Date: Sun, 15 Dec 2019 07:37:05 -0800
>
>> And one more test, with IPv6 temporarily disabled, to force IPv4 ...
>>
>>> From: "Michael Paoli" <Michael.Paoli@cal.berkeley.edu>
>>> Subject: [BALUG-Test] And now IPv4 email/SMTP/lists should be  
>>> originating from the new	IPv4 IP
>>> Date: Sun, 15 Dec 2019 07:11:33 -0800
>>
>>> And now IPv4 email/SMTP/lists should be originating from the new IPv4 IP,
>>> traffic may be via IPv4 or IPv6 (no change on the IPv6), but at least
>>> for that traffic going over IPv4 ...
>




From Michael.Paoli@cal.berkeley.edu  Tue Dec 17 11:47:00 2019
From: Michael.Paoli@cal.berkeley.edu (Michael Paoli)
Date: Tue, 17 Dec 2019 03:47:00 -0800
Subject: [BALUG-Test] And now IPv4 email/SMTP/lists
	should	be	originating from the new	IPv4 IP
In-Reply-To: <20191217030024.27214ws9dd58x24g@webmail.rawbw.com>
References: <20191215071133.98051vtaopi13sqs@webmail.rawbw.com>
 <20191215073705.588520deag7dqkis@webmail.rawbw.com>
 <20191215074452.11984flhqow16lus@webmail.rawbw.com>
 <20191217030024.27214ws9dd58x24g@webmail.rawbw.com>
Message-ID: <20191217034700.226998or50dp3m7o@webmail.rawbw.com>

Okay, this time, "for real"?

Yet another test.
With new ISP making IPv6 available, host had automagically picked
that up ... but alas, sending SMTP (& notably SPF) not prepared
for that ... and in any case wanted to test the IPv4, not IPv6 (oops),
so ... have autoconf & accept_ra disabled for now on that interface,
to be able to test via the new IPv4.

$ grep . /proc/sys/net/ipv6/conf/eth0/accept_ra  
/proc/sys/net/ipv6/conf/eth0/autoconf
/proc/sys/net/ipv6/conf/eth0/accept_ra:0
/proc/sys/net/ipv6/conf/eth0/autoconf:0
$ tail -n 6 /etc/sysctl.conf# for now, disable autoconf and accept_ra  
for IPv6 on eth0
# (not yet expected for SMTP SPF, etc.)
# grep . /proc/sys/net/ipv6/conf/eth0/accept_ra  
/proc/sys/net/ipv6/conf/eth0/autoconf
net.ipv6.conf.eth0.accept_ra=0
net.ipv6.conf.eth0.autoconf=0
########################################################################
$

> From: "Michael Paoli" <Michael.Paoli@cal.berkeley.edu>
> Subject: Re: [BALUG-Test] And now IPv4 email/SMTP/lists should  
> be	originating from the new	IPv4 IP
> Date: Tue, 17 Dec 2019 03:00:24 -0800

> And yet another test ... ought be a "good" one this time.  ;-)
> I *temporarily* disabled the IPv6 IPs - to force IPv4 (yes, there
> are other ways ... but for the relatively quick-and dirty ...
> also still testing and flushing out any minor issues that may
> remain in the full
> /etc/network/interfaces ifup/ifdown functionality).
>
> Also, relevant SPF records updated (alas, had dropped TTLs, and queued
> the changes, but forgot to get 'em in earlier) ... so that part
> of it ought work now too (and might otherwise prevent delivery,
> and rightfully so - especially with -all).
>
>> From: "Michael Paoli" <Michael.Paoli@cal.berkeley.edu>
>> Subject: Re: [BALUG-Test] And now IPv4 email/SMTP/lists should  
>> be	originating from the new	IPv4 IP
>> Date: Sun, 15 Dec 2019 07:44:52 -0800
>
>> Drats ... didn't actually go via IPv6 ... will test more later.
>>
>>> From: "Michael Paoli" <Michael.Paoli@cal.berkeley.edu>
>>> Subject: Re: [BALUG-Test] And now IPv4 email/SMTP/lists should  
>>> be	originating from the new	IPv4 IP
>>> Date: Sun, 15 Dec 2019 07:37:05 -0800
>>
>>> And one more test, with IPv6 temporarily disabled, to force IPv4 ...
>>>
>>>> From: "Michael Paoli" <Michael.Paoli@cal.berkeley.edu>
>>>> Subject: [BALUG-Test] And now IPv4 email/SMTP/lists should be  
>>>> originating from the new	IPv4 IP
>>>> Date: Sun, 15 Dec 2019 07:11:33 -0800
>>>
>>>> And now IPv4 email/SMTP/lists should be originating from the new IPv4 IP,
>>>> traffic may be via IPv4 or IPv6 (no change on the IPv6), but at least
>>>> for that traffic going over IPv4 ...