On Wed, 06 Apr 2016 12:03:36 +0900, "Stephen J. Turnbull"
wrote:
> R. David Murray writes:
>
> > again. However, the IPV4 address has a poor reputation, and Verizon
> > at least appears to be blocking it. So more work is still needed.
>
> Don't take Verizon's policy as meaningful. Tell Ver
On Wed, 06 Apr 2016 12:21:04 +1000, Nick Coghlan wrote:
> On 6 April 2016 at 11:27, Terry Reedy wrote:
> bugs.python.org is currently sending notification emails directly to
> recipients, rather than routing them via the outbound SMTP server on
> mail.python.org.
Correct.
> Reconfiguring it to
R. David Murray writes:
> again. However, the IPV4 address has a poor reputation, and Verizon
> at least appears to be blocking it. So more work is still needed.
Don't take Verizon's policy as meaningful. Tell Verizon customers to
get another address. That is the only solution that works fo
On 6 April 2016 at 11:27, Terry Reedy wrote:
> On 4/5/2016 3:56 PM, R. David Murray wrote:
>>
>> We think we have a partial (and hopefully temporary) solution to the
>> bugs email blockage: ipv6 has been turned off on bugs, so it is sending
>> only from the ipv4 address. Google appears to be acce
On 4/5/2016 3:56 PM, R. David Murray wrote:
We think we have a partial (and hopefully temporary) solution to the
bugs email blockage: ipv6 has been turned off on bugs, so it is sending
only from the ipv4 address. Google appears to be accepting the emails
again. However, the IPV4 address has a p
We think we have a partial (and hopefully temporary) solution to the
bugs email blockage: ipv6 has been turned off on bugs, so it is sending
only from the ipv4 address. Google appears to be accepting the emails
again. However, the IPV4 address has a poor reputation, and Verizon
at least appears t
