On 1 Dec 2016, at 13:47, rich.gre...@hushmail.com wrote:
On 11/28/2016 at 4:56 PM, "Bill Cole"
wrote:
[...]
I made modifications to the master.cf file.
To get one, you need an entry similar to this in
your
master.cf file:
submission inet n - n - - smtpd
-
Okay, I'm made some exciting progress and I am grateful for the help. I will
show to people how I got this working
At first thought, I figured that it would simply be the IMAP password used by
Dovecot to access my mailbox. Not exactly true... I did some digging in some
blogs and the document
On 11/28/2016 at 4:56 PM, "Bill Cole"
wrote:
>
>On 28 Nov 2016, at 17:29, rich.gre...@hushmail.com wrote:
>
>> I changed it. When I compose and send to an outside domain now,
>I get
>> an error that hints towards port 25 being strongly preferred
>over 587.
>>
>> Sending of the message faile
Texto em portugues:
Pelo que eu entendi você está com problemas para enviar e-mails partindo do
thunderbird; não sei se compreendi o motivo do teste de DNS mas me parece
que você quer confirmar o MX.
Em geral a porta segura do SMTP é a 465, o gmail utiliza a 587.
Utilizando a lógica seu dominio não
On 28 Nov 2016, at 17:29, rich.gre...@hushmail.com wrote:
I changed it. When I compose and send to an outside domain now, I get
an error that hints towards port 25 being strongly preferred over 587.
Sending of the message failed.
The message could not be sent because connecting to Outgoing se
On Mon, Nov 28, 2016 at 04:29:58PM -0600, rich.gre...@hushmail.com wrote:
> >Did you also fix the key_file setting?
>
> Yes, I did.
Good, at this point STARTTLS is working on port 25.
> >You have received headers and logs that should indicate how the
> >mail it sent entered your mailbox. You c
On 11/28/2016 at 3:25 PM, "Viktor Dukhovni" wrote:
>
>On Mon, Nov 28, 2016 at 02:59:22PM -0600, rich.gre...@hushmail.com
>wrote:
>
>>
>>smtpd_tls_cert_file=/etc/letsencrypt/live/example.com/fullchain.pe
>m
>> >>
>smtpd_tls_key_file=/etcletsencrypt/live/example.com/privkey.pem
>> >
>> >The key
On Mon, Nov 28, 2016 at 02:59:22PM -0600, rich.gre...@hushmail.com wrote:
> >smtpd_tls_cert_file=/etc/letsencrypt/live/example.com/fullchain.pem
> >> smtpd_tls_key_file=/etcletsencrypt/live/example.com/privkey.pem
> >
> >The key file setting seems to have a typo.
> >
> >> smtpd_use_tls=yes
> >
>
On 11/28/2016 at 1:28 PM, "Viktor Dukhovni" wrote:
>
>> On Nov 28, 2016, at 2:13 PM, rich.gre...@hushmail.com wrote:
>>
>> # TLS parameters
>> smtpd_tls_loglevel = 1;
>
>If that ';' is really there, get rid of it.
>
Got rid of it. C habits are hard to break. Good eye spotting that; mistakes
l
> On Nov 28, 2016, at 2:13 PM, rich.gre...@hushmail.com wrote:
>
> # TLS parameters
> smtpd_tls_loglevel = 1;
If that ';' is really there, get rid of it.
> smtpd_tls_cert_file=/etc/letsencrypt/live/example.com/fullchain.pem
> smtpd_tls_key_file=/etcletsencrypt/live/example.com/privkey.pem
The
Okay,
Victor, thanks for the stats in the second email! That is quite interesting to
read. I have only recently (this summer) heard of LetsEncrypt.org. Up until
that point, I had expected that I was condemned by powers-that-be to buy a key
annually forever.
Oh yeah, I love the "smoke and m
On Mon, Nov 28, 2016 at 07:29:15PM +0100, Florian Piekert wrote:
> I use the same certificate for postfix, apache, dovecot, proftpd, etc...
> (from cacert.org).
The cacert.org root CA's MD5 self-signature tends to trigger
inteoperability problems. You're typically better off with some
other CA.
On Mon, Nov 28, 2016 at 12:18:09PM -0600, rich.gre...@hushmail.com wrote:
> Okay, I am already using letsencrypt.org for my port 443 traffic. So once
> I have it extended to also cover SMTP on port 587, would it be acceptable
> to disable port 25, or is port 25 still needed (perhaps to suggest to
Am 28.11.2016 um 19:18 schrieb rich.gre...@hushmail.com:
> Okay, I am already using letsencrypt.org for my port 443 traffic. So
> once I have it extended to also cover SMPT on port 587, would it be
> acceptable to disable port 25, or is port 25 still needed (perhaps to
> suggest to clients that it
Am 28.11.2016 um 18:57 schrieb rich.gre...@hushmail.com:
Hello,
it looks Thunderbird can't validate the certificate the mailserver is using.
The dialogue you refer to is normal. What I recommend to my folks when using my
servers is to simply "accept it" and get done with it (happens every 6 mon
Okay, I am already using letsencrypt.org for my port 443 traffic. So once I
have it extended to also cover SMPT on port 587, would it be acceptable to
disable port 25, or is port 25 still needed (perhaps to suggest to clients that
it isn't accepting any traffic except 587)
I have to admit, I ha
On Mon, Nov 28, 2016 at 11:57:44AM -0600, rich.gre...@hushmail.com wrote:
> Nov 28 18:35:14 example postfix/smtpd[1293]: connect from
> 69-179-xxx-yyy.dyn.centurytel.net[69.179.xxx.yyy]
> Nov 28 18:35:16 example postfix/smtpd[1293]: warning: TLS library problem:
> error:14094418:SSL routines:ssl
I should make clear in the post that u...@example.com is the IMAP mailbox name
and that m...@example.com is a virtual alias. This machine hosts about 8
domains and has, I think, three mailboxes. I am the sole user of the email
system.
On 11/28/2016 at 11:58 AM, rich.gre...@hushmail.com wrote:
Okay, I am really curious how this works then. Good catch on the 'www' test.
I winged it without reading the manpage. I've never known a good starting
point for learning DNS, so that is definitely a weak point. So, now that the
DNS is out of the way. I'm going to dig deeper here.
When I tr
On 11/28/2016 9:07 AM, rich.gre...@hushmail.com wrote:
> Hello,
>
> First, email has been working fine on this server for past several months
> while using the Squirrelmail web client located on the same server. I am
> needing an alternative method to access mail services and decided, on a whim
Okay,
I accidentally sent this half-composed. But yes. I was able to send via SMTP,
but only if my destination address was on my machine (which is probably good)
Maybe since I sent this, I let people deliver their opinions on if this is an
MX record issue first.
Thanks
Rick
On 11/28/2016 at
21 matches
Mail list logo