From: pe...@easthope.ca
Date: Sat, 01 Mar 2014 07:59:02 -0800
> cPanel instructions for configuring the email client.
> "Secure SSL/TLS Settings
> (Recommended)
> Username: peter[at]easthope.ca
> Password: Use the email account's password.
> Incoming Server: ccx.websitewelcome.com
>
On Du, 27 apr 14, 07:13:32, pe...@easthope.ca wrote:
> From: Andrei POPESCU
> Date: Sat, 1 Mar 2014 19:31:22 +0200
> > P.S. could you please not break threads *and* munge the Subject on every
> > reply?
>
> The limitations in using a Web browser to reply to a mailing list are
> known a
From: Andrei POPESCU
Date: Sat, 1 Mar 2014 19:31:22 +0200
> P.S. could you please not break threads *and* munge the Subject on every
> reply?
The limitations in using a Web browser to reply to a mailing list are
known and documented in
https://wiki.debian.org/DebianMailingLists#Messag
On Sb, 01 mar 14, 07:59:02, pe...@easthope.ca wrote:
>
> The only way I can make sense of this is that the instructions are crossed.
> TLS access should be to mail.easthope.ca with appropriate certificate.
> In-the-clear access should be to ccx.websitewelcome.com with no certificate.
Sorry, I mus
From: Dan Purgert
Date: Sat, 01 Mar 2014 06:41:31 -0500
> Because that's how SSL/TLS works. If the server you're attempting to get
> to presents the wrong certificate, then it's assumed that server is not
> who the user intended to get to, and the connection is failed.
Makes perfect sense.
A
On 01/03/14 22:41, Dan Purgert wrote:
> On 01/03/2014 00:38, Peter Easthope wrote:
>> References: <2b8c71ec0272453c696df1a5d4ad9c87.squir...@easthope.ca>
>> <53115869.3090...@gmail.com>
>>
>> From: Scott Ferguson
>> Date: Sat, 01 Mar 2014 14:47:53 +1100
>>> Shouldn't that certificate be for domain
On 01/03/2014 00:38, Peter Easthope wrote:
> References: <2b8c71ec0272453c696df1a5d4ad9c87.squir...@easthope.ca>
> <53115869.3090...@gmail.com>
>
> From: Scott Ferguson
> Date: Sat, 01 Mar 2014 14:47:53 +1100
>> Shouldn't that certificate be for domain from which you are mailing?
>> e.g. *.eastho
On 01/03/14 16:38, Peter Easthope wrote:
> References: <2b8c71ec0272453c696df1a5d4ad9c87.squir...@easthope.ca>
> <53115869.3090...@gmail.com>
>
> From: Scott Ferguson
> Date: Sat, 01 Mar 2014 14:47:53 +1100
>> Shouldn't that certificate be for domain from which you are mailing?
>> e.g. *.easthope
References: <2b8c71ec0272453c696df1a5d4ad9c87.squir...@easthope.ca>
<53115869.3090...@gmail.com>
From: Scott Ferguson
Date: Sat, 01 Mar 2014 14:47:53 +1100
> Shouldn't that certificate be for domain from which you are mailing?
> e.g. *.easthope.ca
Why? The only configuration given to mutt was t
On 01/03/14 13:59, Peter Easthope wrote:
> In accord to https://wiki.debian.org/Mutt, these four lines are in .muttrc.
>
> set smtp_url = "smtps://pe...@easthope.ca:465" # ESMTP with TLS
> set smtp_pass="_"
> set from="pe...@easthope.ca"
> set realname="Pete"
>
> A test message yields th
In accord to https://wiki.debian.org/Mutt, these four lines are in .muttrc.
set smtp_url = "smtps://pe...@easthope.ca:465" # ESMTP with TLS
set smtp_pass="_"
set from="pe...@easthope.ca"
set realname="Pete"
A test message yields the following output.
The problem is at COMODO CA Limited?
11 matches
Mail list logo
