, with my login. But then
the client connection hangs until timeout.
If a firewall rule existed then I would think it would block my attempt of
openssl to look at the certificate.
On July 24, 2022 10:46:56 PM EDT, Sam Varshavchik wrote:
>Greg Pfister writes:
>
>> Hi Sam,
>>
>
. The only thing I had to do
manually is the 10 or so couriertls running, had to kill those.
Again, no firewall changes made, nor any courier configuration files.
On July 24, 2022 9:00:37 PM EDT, Sam Varshavchik wrote:
>Greg Pfister writes:
>
>> Then I checked the logs and realized t
and route email. However, what I can't do, is send through it -
client programs just sit and timeout. Using port 587, and have checked
using sl_client and everything looks good. Again, no errors in log, do
see connection, but nothing after that.
On 7/24/22 10:50, Sam Varshavchik wrote:
Greg
Updating my GoDaddy Certificate by placing in a pem file, in order,
cert, chain certificates, and key. MTA and IMAP start in ssl, however,
received while performing a openssl s_client
139637514474880:error:0407E085:rsa
routines:RSA_verify_PKCS1_PSS_mgf1:first octet
-mta.com) escribió:
Greg Pfister writes:
« HTML content follows »
Hi Sam,
soft error on the domain.
softfails for lookups if the A lookup succeeded. Before 1.0.10 the only
option is to rebuild Courier using --without-ipv6
as i fixed in my personal packages.. XD puff i know that was a
problem
om we trust you
250-DSN
250-SIZE 104857600
250-STARTTLS
250-ETRN
250-TURN
250-ATRN
250-NO-SOLICITING
250-8BITMIME
250-HELP
250-PIPELINING
250-SMTPUTF8
250 EHLO
Telnet to dns produces same result.
On 1/7/21 7:59 PM, Sam Varshavchik wrote:
Greg Pfister writes:
System: Debian 4.19.0-6-amd64 (B
, PICCORO McKAY Lenz wrote:
El jue, 7 de ene. de 2021 a la(s) 21:01, Sam Varshavchik
(mr...@courier-mta.com <mailto:mr...@courier-mta.com>) escribió:
Greg Pfister writes:
> System: Debian 4.19.0-6-amd64 (Buster 10)
>
>
> Courier (mta): 1.0.6-1
>
>
a courier issue. Could be wrong - been known to
happen.rarely.
--
Greg Pfister
___
Courier-imap mailing list
Courier-imap@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
Dan,
The mail server will send messages to your system logging, however, it
doesn't appear that it's receiving. Have you checked your main system
log to see if any messages are being delivered there?
On 8/12/20 6:38 PM, Dan Egli wrote:
No one has any ideas on how to fix this? Or is this
Dan,
What does your mail.err log file say (or the mail.log log file)?
On 8/12/20 4:43 AM, Dan Egli wrote:
I am needing some help here. I downloaded the courier source and used
CentOS 7's rpmbuild to make rpms to install. After everything is
installed I tried to test it. But it always says
On Mon, 2018-07-30 at 21:18 +0200, Ángel wrote:
> On 2018-07-30 at 14:17 -0400, Greg Pfister wrote:Seeing 30+ second
> delay on port 465 or 587 connections, yet CourierIMAP 993 connections
> are instant using openssl s_client.
>
> I though that it may be the ISP putting in a del
er of connections accepted from the same IP address
MAXPERIP=5
***
**
/end contents of esmtpd-ssl configuration file
--
--
Greg Pfister
gpfis...@a4gtechnology.com
WARNING - Oath Inc. now owns all ema
On Tue, 2018-07-24 at 17:56 -0400, Sam Varshavchik wrote:
> Greg Pfister writes:
> Thanks. I'll try that. All the research that I've come up with show
> s that the cert and key file goes into one pem file (which I have) fo
> r the TLS_CERTFILE. However, I thought the TLS_TRUSTCERTS
On Mon, 2018-07-23 at 20:47 -0400, Sam Varshavchik wrote:
> Greg Pfister writes:
> « HTML content follows »
> Attempted to install a known good GoDaddy certificate (works on
> apache2 on same machine), utilizing all the same files sent from
> GoDaddy, fails with error 21 -
have both the signed
certificate from GoDaddy and the key file as a pem file.
Here is the error from openssl s_client:
verify error:num=21:unable to verify the first certificate
--
--
Greg Pfister
--
Check out
15 matches
Mail list logo
