[mailop] Just wondering : did anyone ever get a useful response from Yahoo's contact form ?

[Mathieu Marnat]

Hi everyone,


Just a follow-up message : Yahoo community forum is actually not really 
helpful. It seems that there are no good channels to get an actual answer from 
them.

Did you also notice that since late september Yahoo seems to be much more 
aggressive in its throttling strategy or is it just us ? I notice that on the 
community forum a lot of people are complaining about getting 421 4.7.0 [TSS04] 
errors and 0 support from Yahoo.


Thanks.


Mathieu.
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Expires SSL cert for mailop

[Mike Hammett]

HTTP is pointless in this case because it just redirects to HTTPs. 




- 
Mike Hammett 
Intelligent Computing Solutions 

Midwest Internet Exchange 

The Brothers WISP 

- Original Message -

From: st...@greengecko.co.nz 
To: "Doug Barton" , mailop@mailop.org 
Sent: Thursday, October 25, 2018 11:11:04 PM 
Subject: Re: [mailop] Expires SSL cert for mailop 

http://chilli.nosignal.org won't be using any cert (: 

October 26, 2018 4:58 PM, "Doug Barton"  wrote: 

> Y'all might want to be aware that this issue is being discussed on the NANOG 
> list. In the age of 
> Let's Encrypt expired TLS certs are a really bad look. 
> 
> On 9/12/18 6:24 AM, Matt Gilbert via mailop wrote: 
> 
>> Hey gang, 
>> I was showing mailop to a new member of my team, and when I went to show > 
>> them where to request 
>> signup to the list, I noticed that the SSL > certificate has expired, which 
>> causes most (all?) 
>> current browsers to > block the page loading. I figured you’d want to know. 
>>> chilli.nosignal.org  uses an invalid > security 
>>> certificate. 
>>> The certificate expired on July 25, 2018, 7:59:59 PM GMT-4. The > current 
>>> time is September 12, 
>> 2018, 9:21 AM. 
>>> Error code: SEC_ERROR_EXPIRED_CERTIFICATE 
>>> Thanks, 
>> Matt Gilbert 
>> -- 
>> Deliverability Engineer | MailChimp 
>> delivery.mailchimp.com  
 ___ 
>> mailop mailing list 
>> mailop@mailop.org 
>> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop 
> 
> ___ 
> mailop mailing list 
> mailop@mailop.org 
> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop 

___ 
mailop mailing list 
mailop@mailop.org 
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop 

___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

[mailop] O365 discarding mail after User-Agent change

[Steve Dodd]

Hope nobody minds a 'civilian' posting here..

I switched to using Mailpile (https://www.mailpile.is/) on 1st Oct (but not
enabling any encryption features, etc.) About five days later I started to
have real problems with deliverability to certain recipients on O365.

I'm using my Gmail account, so messages are still going out through their
servers; SPF and DKIM should therefore be unchanged.

The recipients in question are people I have been corresponding with for
some time, so I am in their address books and there is a history of them
responding to my messages. Sadly they're non technical and so can't provide
me with any information.

All the tests I have run with technically minded contacts who happen to use
O365 have been fine, and when I've managed to get a look at the headers
there is nothing untoward flagged that I can see.

Absolutely baffled and having real problems running my life (O365 seems to
be preferred by UK government departments and services.) I have tried
sending from a Gandi-hosted domain as well, and having similar issues, even
after enabling DKIM.

Hints and tips gratefully received...
Steve
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Expires SSL cert for mailop

[Mark Milhollan]

On Thu, 25 Oct 2018, Doug Barton wrote:

>In the age of Let's Encrypt expired TLS certs are a really bad look.

Let's Encrypt changes little, processes can break whether they are 
yearly, bi-yearly or monthly.  Granted you'd think there would be 
monitoring and then reasonably quick restoration.


/mark

___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Expires SSL cert for mailop

[Thomas Walter]

Hey Mark,

On 26.10.18 17:34, Mark Milhollan wrote:
> Let's Encrypt changes little, processes can break whether they are 
> yearly, bi-yearly or monthly.  Granted you'd think there would be 
> monitoring and then reasonably quick restoration.

Let's Encrypt automates the whole process and in case that doesn't work
for whatever reason it sends you reminders by mail way before the
certificate finally expires.

If the main process and the backup reminder both fail, you are doing
something wrong ;).

Regards,
Thomas Walter

-- 
Thomas Walter
Datenverarbeitungszentrale

FH Münster
- University of Applied Sciences -
Corrensstr. 25, Raum B 112
48149 Münster

Tel: +49 251 83 64 908
Fax: +49 251 83 64 910
www.fh-muenster.de/dvz/

___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

[mailop] Mimecast

[rps462]

Hey all,

Anybody from Mimecast that can ping me off-list?

Thanks,
-Ryan
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Expires SSL cert for mailop

[Noel Butler]

On 27/10/2018 04:40, Thomas Walter wrote:

> Hey Mark,
> 
> On 26.10.18 17:34, Mark Milhollan wrote: 
> 
>> Let's Encrypt changes little, processes can break whether they are 
>> yearly, bi-yearly or monthly.  Granted you'd think there would be 
>> monitoring and then reasonably quick restoration.
> 
> Let's Encrypt automates the whole process and in case that doesn't work
> for whatever reason it sends you reminders by mail way before the
> certificate finally expires.
> 
> If the main process and the backup reminder both fail, you are doing
> something wrong ;).
> 
> Regards,
> Thomas Walter

Problem with letsencrypt is their preferred and insisted " certbot "  -
does not run (easily at least) on all flavours.. 
I gave up with it on slackware which is what my servers run, tried using
Crypt::LE and voila instant success, it was painless to use even for
(tested at least) renews, although it requires a working webserver so
come time to replace my comodo's on my MX's, will give me another
challenge :) 

-- 
Kind Regards, 

Noel Butler 

This Email, including any attachments, may contain legally 
privileged
information, therefore remains confidential and subject to copyright
protected under international law. You may not disseminate, discuss, or
reveal, any part, to anyone, without the authors express written
authority to do so. If you are not the intended recipient, please notify
the sender then delete all copies of this message including attachments,
immediately. Confidentiality, copyright, and legal privilege are not
waived or lost by reason of the mistaken delivery of this message. Only
PDF [1] and ODF [2] documents accepted, please do not send proprietary
formatted documents 

 

Links:
--
[1] http://www.adobe.com/
[2] http://en.wikipedia.org/wiki/OpenDocument___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Expires SSL cert for mailop

[Dave Warren]

On Fri, Oct 26, 2018, at 19:29, Noel Butler wrote:
> Problem with letsencrypt is their preferred and insisted " certbot "
> - does not run (easily at least) on all flavours..> I gave up with it on 
> slackware which is what my servers run, tried
> using Crypt::LE and voila instant success, it was painless to use even
> for (tested at least) renews, although it requires a working webserver
> so come time to replace my comodo's on my MX's, will give me another
> challenge :)
https://letsencrypt.org/docs/client-options/ does recommend starting with 
Certbot, but it certainly makes it clear that there are alternative options: 
"If certbot does not meet your needs, or you’d simply like to try something 
else, there are many more clients to choose from below"
You also don't need to generate your certificate on the same machine
that hosts the services using the certificates. It can either increase
or reduce complexity depending on the particulars of your environment,
but I generate most of my certificates centrally using DNS based
authorization and either push or pull the certificates based on what is
appropriate.
It is an imperfect world, and this definitely applies to Let's Encrypt's
documentation, but I've had good success building on top of what is
already out there to get a custom solution when I don't see a perfect
cookiecutter fix.

___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop