Nov 20 20:24:27 pinkie postfix/smtp[14887]: certificate verification
failed for gmail-smtp-in.l.google.com[209.85.225.27]:25: untrusted issuer
/C=US/O=Equifax/OU=Equif$
Nov 20 20:24:28 pinkie postfix/smtp[14887]: 9C7281855D:
to=sepich.e...@gmail.com,
relay=gmail-smtp-in.l.google.com[209.85.225.27
On Sunday 20 November 2011 14:33:58 peng...@sepserver.net wrote:
Nov 20 20:24:27 pinkie postfix/smtp[14887]: certificate
verification failed for
gmail-smtp-in.l.google.com[209.85.225.27]:25: untrusted issuer
/C=US/O=Equifax/OU=Equif$
Nov 20 20:24:28 pinkie postfix/smtp[14887]: 9C7281855D
:
certificate verification failed for example.org untrusted issuer
/C=DE/ST=NW/O=My CA/CN=Me/email=mys...@example.org
[..] status=deferred (Server certificate not trusted)
(I did not change the postfix config during the postfix upgrade)
My tls related configuration looks like this:
smtp_use_tls
with 2.7.0, but after the upgrade I get following errors:
certificate verification failed for example.org untrusted issuer
/C=DE/ST=NW/O=My CA/CN=Me/email=mys...@example.org [..]
status=deferred (Server certificate not trusted)
(I did not change the postfix config during the postfix upgrade
mandatory TLS and certificate verification. The setup worked great
with 2.7.0, but after the upgrade I get following errors:
certificate verification failed for example.org untrusted issuer
/C=DE/ST=NW/O=My CA/CN=Me/email=mys...@example.org [..]
status=deferred (Server certificate
On Sat, Aug 20, 2011 at 03:08:43PM -0400, Scott Kitterman wrote:
There are open bug reports for this in Debian and Ubuntu. I expect this will
be fixed in the next uploads to each distro.
Ok, I assume it is this bug report (the debian report is linked from there):
On Sun, Jan 09, 2011 at 10:39:49PM +, IT geek 31 wrote:
My understanding is to prevent these errors, you obtain the root
certificate for each server mail certificate your Postfix server
connects to, append it to a pem file and reference it with
smtp_tls_CAfile in main.conf.
Not worth it,
On Mon, 10 Jan 2011 09:20:08 -0500
Victor Duchovni victor.ducho...@morganstanley.com articulated:
I'll see whether there is interest in adopting the fine-grained TLS
logging code in 2.9.
Just my 2¢; however, I think it would be worth while.
--
Jerry ✌
postfix-u...@seibercom.net
anywhere).
So I get this error as expected:
Jan 8 01:57:46 Ricochet postfix/smtp[24852]: certificate verification
failed for gmail-smtp-in.l.google.com[74.125.91.27]:25: untrusted
issuer /C=US/O=Equifax/OU=Equifax Secure Certificate Authority
Is there a way to have postfix not care about the issuer
I don't have it listed
as a trusted issuer anywhere).
So I get this error as expected:
Jan 8 01:57:46 Ricochet postfix/smtp[24852]: certificate verification
failed for gmail-smtp-in.l.google.com[74.125.91.27]:25: untrusted
issuer /C=US/O=Equifax/OU=Equifax Secure Certificate Authority
My understanding is to prevent these errors, you obtain the root
certificate for each server mail certificate your Postfix server
connects to, append it to a pem file and reference it with
smtp_tls_CAfile in main.conf.
This could obviously take a while. On a Windows installation you can
refer to
On 1/9/2011 4:39 PM, IT geek 31 wrote:
My understanding is to prevent these errors, you obtain the root
certificate for each server mail certificate your Postfix server
connects to, append it to a pem file and reference it with
smtp_tls_CAfile in main.conf.
This could obviously take a while.
Ricochet postfix/smtp[24852]: certificate verification
failed for gmail-smtp-in.l.google.com[74.125.91.27]:25: untrusted
issuer /C=US/O=Equifax/OU=Equifax Secure Certificate Authority
Is there a way to have postfix not care about the issuer and just
continue? I am aware that there can be security
Hi!
I act as a spamcheck-relay for another server and I get this error
message when my server tries to connect and send a mail to them:
certificate verification failed for
remote.example.se[85.197.XXX.XXX]:25: untrusted issuer
/CN=AAA-SBS-PYRAMID-CA
Its the certificate on the server
* Patric Falinder patric.falin...@omg.nu:
Hi!
I act as a spamcheck-relay for another server and I get this
error message when my server tries to connect and send a mail to
them:
certificate verification failed for
remote.example.se[85.197.XXX.XXX]:25: untrusted issuer
/CN=AAA-SBS
]:25: untrusted issuer
/CN=AAA-SBS-PYRAMID-CA
You don'T trust the CA, thus the cert is untrusted.
Yes but can I somehow make it trusted?
* Patric Falinder patric.falin...@omg.nu:
certificate verification failed for
remote.example.se[85.197.XXX.XXX]:25: untrusted issuer
/CN=AAA-SBS-PYRAMID-CA
You don'T trust the CA, thus the cert is untrusted.
Yes but can I somehow make it trusted?
By trusting the CA. Meaning: Installing
Ralf Hildebrandt skrev 2010-03-15 14:35:
* Patric Falinderpatric.falin...@omg.nu:
certificate verification failed for
remote.example.se[85.197.XXX.XXX]:25: untrusted issuer
/CN=AAA-SBS-PYRAMID-CA
You don'T trust the CA, thus the cert is untrusted.
Yes but can I somehow
On 3/15/2010 9:00 AM, Patric Falinder wrote:
Ralf Hildebrandt skrev 2010-03-15 14:35:
* Patric Falinderpatric.falin...@omg.nu:
certificate verification failed for
remote.example.se[85.197.XXX.XXX]:25: untrusted issuer
/CN=AAA-SBS-PYRAMID-CA
You don'T trust the CA, thus the cert is untrusted
Noel Jones skrev 2010-03-15 16:53:
On 3/15/2010 9:00 AM, Patric Falinder wrote:
Ralf Hildebrandt skrev 2010-03-15 14:35:
* Patric Falinderpatric.falin...@omg.nu:
certificate verification failed for
remote.example.se[85.197.XXX.XXX]:25: untrusted issuer
/CN=AAA-SBS-PYRAMID-CA
You don'T trust
20 matches
Mail list logo
