> On Dec 10, 2018, at 8:00 PM, Sean Son
> wrote:
>
> Thank you for the reply. Can the client be configured to trust more
> than one SSL cert?
most of clients support more than one certificate authority.
On Mon, Dec 10, 2018 at 9:40 PM Viktor Dukhovni
wrote:
You've told us nothing about
On Mon, Dec 10, 2018 at 9:40 PM Viktor Dukhovni
wrote:
> > On Dec 10, 2018, at 8:00 PM, Sean Son
> wrote:
> >
> > Thank you for the reply. Can the client be configured to trust more
> than one SSL cert?
>
> You've told us nothing about the client, so it would be a miracle
> if someone on the
> On Dec 10, 2018, at 8:00 PM, Sean Son
> wrote:
>
> Thank you for the reply. Can the client be configured to trust more than one
> SSL cert?
You've told us nothing about the client, so it would be a miracle
if someone on the list could give an answer to that question.
Is the client
On Mon, Dec 10, 2018 at 6:57 PM Viktor Dukhovni
wrote:
> > On Dec 10, 2018, at 6:41 PM, Sean Son
> wrote:
> >
> > 330462 Dec 7 20:39:21 mailer postfix/smtpd[12242]: SSL3 alert
> read:fatal:unknown CA
> > 330463 Dec 7 20:39:21 mailer postfix/smtpd[12242]: SSL_accept:failed
> in SSLv3 read
> On Dec 10, 2018, at 6:41 PM, Sean Son
> wrote:
>
> 330462 Dec 7 20:39:21 mailer postfix/smtpd[12242]: SSL3 alert
> read:fatal:unknown CA
> 330463 Dec 7 20:39:21 mailer postfix/smtpd[12242]: SSL_accept:failed in
> SSLv3 read client key exchange A
> 330464 Dec 7 20:39:21 mailer
hello all
We have a RHEL 7 based server running monitoring software consisting of
Groundwork Monitoring Software, which includes Nagios , Nedi, and other
tools. This server is set up with TLS enabled and it uses a script to send
email to any SMTP server that we choose. I have an SMTP server set
On 09/02/2013 08:11 AM, Eric Kom wrote:
Good day,
Please my smtp based on postfix its sending me a messages with the
above subject and body:
Postfix SMTP server: errors from mail-ve0-f174.google.com[209.85.128.174]
Transcript of session follows.
Out: 220 Great Kom Networks (Pty) LTD
Good day,
Please my smtp based on postfix its sending me a messages with the above
subject and body:
Postfix SMTP server: errors from mail-ve0-f174.google.com[209.85.128.174]
Transcript of session follows.
Out: 220 Great Kom Networks (Pty) LTD, Ready.
In: EHLO mail-ve0-f174.google.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
Unfortunately, I'm finding this singularly unhelpful:
- Original Message
Subject: Postfix SMTP server: errors from unknown[209.85.212.69]
Date: Thu, 22 Aug 2013 23:39:49 -0700 (PDT)
From: mailer-dae...@mail.parts
On Aug 23, 2013, at 09:20, David Benfell dbenf...@gmail.com wrote:
Unfortunately, I'm finding this singularly unhelpful:
- Original Message
Subject: Postfix SMTP server: errors from unknown[209.85.212.69]
Check your DNS configuration; that IP address has matching forward
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/23/2013 12:55 AM, DTNX Postmaster wrote:
On Aug 23, 2013, at 09:20, David Benfell dbenf...@gmail.com
wrote:
Unfortunately, I'm finding this singularly unhelpful:
- Original Message Subject: Postfix SMTP
server: errors
David Benfell:
Why is this line not working?
smtp_tls_key_file = /big/www/ssl/munich/munich.parts-unknown.org.key
http://www.postfix.org/DEBUG_README.html#no_chroot
Try turning off chroot operation in master.cf
A common mistake is to turn on chroot operation in the master.cf
file without
On Aug 23, 2013, at 10:36, David Benfell dbenf...@gmail.com wrote:
Have you tested your server with 'openssl s_client'? This is what I
am getting;
$ openssl s_client -connect mail.parts-unknown.org:25 -starttls
smtp CONNECTED(0003) 4851:error:140770FC:SSL
From: Ansgar Wiechers li...@planetcobalt.net
On 2012-06-18 Kaushal Shriyan wrote:
Are there any High Availability Solution for Postfix SMTP Server meaning
primary and secondary nodes in Active/Active or Active/Passive Clustering
mode?
Please describe the problem you're trying to solve
John Doe wrote:
From: Ansgar Wiechers li...@planetcobalt.net
On 2012-06-18 Kaushal Shriyan wrote:
Are there any High Availability Solution for Postfix SMTP Server meaning
primary and secondary nodes in Active/Active or Active/Passive Clustering
mode?
Please describe the problem you're
John Doe:
From: Ansgar Wiechers li...@planetcobalt.net
On 2012-06-18 Kaushal Shriyan wrote:
Are there any High Availability Solution for Postfix SMTP Server meaning
primary and secondary nodes in Active/Active or Active/Passive Clustering
mode?
Please describe the problem you're
, Jun 18, 2012 at 2:22 PM, Ansgar Wiechers li...@planetcobalt.net
wrote:
On 2012-06-18 Kaushal Shriyan wrote:
Are there any High Availability Solution for Postfix SMTP Server meaning
primary and secondary nodes in Active/Active or Active/Passive Clustering
mode?
Please describe the problem
Hi,
Are there any High Availability Solution for Postfix SMTP Server meaning
primary and secondary nodes in Active/Active or Active/Passive Clustering
mode?
Regards,
Kaushal
On 2012-06-18 Kaushal Shriyan wrote:
Are there any High Availability Solution for Postfix SMTP Server meaning
primary and secondary nodes in Active/Active or Active/Passive Clustering
mode?
Please describe the problem you're trying to solve instead of what you
perceive as the solution
Onderwerp:
Postfix SMTP server: errors from
118-167-100-152.dynamic.hinet.net[118.167.100.152]
Datum:
Thu, 14 Jul 2011 14:02:49 +0200 (CEST)
Van:
mailer-dae...@mail.rytec.be (Mail
,
Ryan
Originele bericht
Onderwerp:
Postfix SMTP server: errors from
114-24-208-96.dynamic.hinet.net[114.24.208.96]
Datum:
Thu, 14 Jul 2011 14:46:51 +0200 (CEST
Zitat von Rytec ry...@rytec.be:
Dear members,
Which restriction should I need to use to prevent HELO/EHLO
connections with IP numbers ?
This person is spoofing me.
See example below.
regards,
Ryan
Maybe have a look here:
http://www.postfix.org/postconf.5.html#check_helo_access
Regards
On 2011-07-14 15:13, Rytec wrote:
Sorry guys,
Now I got a new request and I see it is rejected by Postfix, so it
means that first it is checked by dnsbl and after that passed it is
checked by Postfix itself.
So I should rearrange my restriction order in main.cf ?
Should we know ?
Perhaps
oeps, something went wrong with my message, I see the mail info is not
attached, see below the two different sessions:
Transcript of session follows.
Out: 220 mail.rytec.be ESMTP Postfix (Ubuntu)
In: HELO 77.109.86.75
Out: 250 mail.rytec.be
In: MAIL FROM:ertre785...@hotmail.com
Out: 250
so what info are you missing?
114.44.105.43 is blocked by Barracuda RBL
77.109.86.75 is blocked by smtpd_helo_restrictions
Am 14.07.2011 21:22, schrieb rytec:
oeps, something went wrong with my message, I see the mail info is not
attached,
see below the two different sessions:
Transcript
On 2011-07-14 21:22, rytec wrote:
oeps, something went wrong with my message, I see the mail info is not
attached, see below the two different sessions:
Transcript of session follows.
Out: 220 mail.rytec.be ESMTP Postfix (Ubuntu)
In: HELO 77.109.86.75
Out: 250 mail.rytec.be
In: MAIL
On 7/14/2011 7:59 AM, Rytec wrote:
Dear members,
Which restriction should I need to use to prevent HELO/EHLO connections with
IP
numbers ?
This person is spoofing me.
See example below.
118-167-100-152.dynamic.hinet.net[118.167.100.152]
The following PCRE table is designed to block
[On-line version will be at http://www.postfix.org/CVE-2011-1720.html]
Summary
===
The Postfix SMTP server has a memory corruption error when the Cyrus
SASL library is used with authentication mechanisms other than PLAIN
and LOGIN (the ANONYMOUS mechanism is unaffected but should
Should I be worried when I see: root+:|sleep 5 as the username?
-- Forwarded message --
From: Mail Delivery System mailer-dae...@someserver.com
Date: Wed, Dec 22, 2010 at 02:33
Subject: Postfix SMTP server: errors from sc4-scan54.someserver.com[x.x.x.x]
To: Postmaster postmas
John Brahy:
Should I be worried when I see: root+:|sleep 5 as the username?
-- Forwarded message --
From: Mail Delivery System mailer-dae...@someserver.com
Date: Wed, Dec 22, 2010 at 02:33
Subject: Postfix SMTP server: errors from sc4-scan54.someserver.com[x.x.x.x
* motty.cruz motty.c...@gmail.com:
Hello,
When a client has a typo in the recipient email address it takes 5 days for
my SMTP server to notify that the user does not exist or was unable to
deliver email. Any idea where to change the option to make it more reliable.
Please sho some logs of
On 2010-09-28 6:43 PM, Noel Jones wrote:
You can also consider setting delay_warning_time to a non-zero value, 4h
is probably reasonable, so the user will be notified when their mail
isn't delivered in a timely manner.
http://www.postfix.org/postconf.5.html#delay_warning_time
SMTP is reliable
On 2010-09-28 9:25 PM, pf at alt-ctrl-del.org wrote:
And set a value for:
maximal_queue_lifetime (default: 5d)
And this I set to 1d... if the user wants to resend it again, they can.
These settings were what the owner of a company I do work for decided on
after I explained to him how smtp
On Tue, 28 Sep 2010 17:43:50 -0500
Noel Jones njo...@megan.vbhcs.org articulated:
An example of this is hotmal.com -- it has an A record but
doesn't answer on port 25. This behavior is identical to a
domain whose mail server is temporarily down, so it would be
wrong for postfix to return
On Wed, 29 Sep 2010 13:57:00 +0200
Ralf Hildebrandt ralf.hildebra...@charite.de articulated:
hotmal.com without i?
Opps, sorry. Too early in the morning, I haven't had my third cup of
coffee yet.
--
Jerry ✌
postfix-u...@seibercom.net
On 09/29/2010 01:35 PM, Charles Marcus wrote:
On 2010-09-28 9:25 PM, pf at alt-ctrl-del.org wrote:
And set a value for:
maximal_queue_lifetime (default: 5d)
And this I set to 1d... if the user wants to resend it again, they can.
These settings were what the owner of a company I do
Le 28/09/2010 23:44, motty.cruz a écrit :
Hello,
When a client has a typo in the recipient email address it takes 5 days for
my SMTP server to notify that the user does not exist or was unable to
deliver email.
No. you are wrong. when you mistype an address, you get an immediate
error
Le Wed 29/09/2010, mouss disait
Le 28/09/2010 23:44, motty.cruz a écrit :
Hello,
When a client has a typo in the recipient email address it takes 5 days for
my SMTP server to notify that the user does not exist or was unable to
deliver email.
No. you are wrong. when you mistype an
Hello,
When a client has a typo in the recipient email address it takes 5 days for
my SMTP server to notify that the user does not exist or was unable to
deliver email. Any idea where to change the option to make it more reliable.
Thanks,
Motty
On 9/28/2010 4:44 PM, motty.cruz wrote:
Hello,
When a client has a typo in the recipient email address it takes 5 days for
my SMTP server to notify that the user does not exist or was unable to
deliver email. Any idea where to change the option to make it more reliable.
When a user addresses
On 09/28/2010 11:44 PM, motty.cruz wrote:
Hello,
When a client has a typo in the recipient email address it takes 5 days for
my SMTP server to notify that the user does not exist or was unable to
deliver email. Any idea where to change the option to make it more reliable.
Make *what* more
Jeroen Geilman wrote:
On 09/28/2010 11:44 PM, motty.cruz wrote:
Hello,
When a client has a typo in the recipient email address it takes 5 days for
my SMTP server to notify that the user does not exist or was unable to
deliver email. Any idea where to change the option to make it more reliable.
On Sat, Apr 24, 2010 at 4:21 PM, Noel Jones njo...@megan.vbhcs.org wrote:
Then read the developer's labeling.
snip
I've read it, and it doesn't really change anything for me personally,
but everyone is entitled to their own opinion. Wietse may use them on
his production systems, but that still
The Doctor:
In: DATA
Out: 354 End data with CRLF.CRLF
Out: 451 4.3.0 Error: queue file write error
Session aborted, reason: lost connection
For other details, see the local mail logfile
- End forwarded message -
And from a heavily debugged log
Apr 23 07:36:59 doctor
Wietse Venema put forth on 4/24/2010 7:02 AM:
Perhaps you missed this in prior email:
- Send non-verbose logging.
- Send logging that covers an entire message life cycle from the
SMTP port to final delivery.
Wietse
Wietse, check the listserv logs and your MUA. He sent that
On Sat, Apr 24, 2010 at 12:20 AM, Victor Duchovni
victor.ducho...@morganstanley.com wrote:
On Sat, Apr 24, 2010 at 12:01:05AM -0400, Jeff Mitchell wrote:
On Thu, Apr 22, 2010 at 6:44 PM, The Doctor doc...@doctor.nl2k.ab.ca wrote:
??Out: 220 doctor.nl2k.ab.ca ESMTP Postfix (2.8-20100323)
I
On 4/24/2010 3:06 PM, Jeff Mitchell wrote:
On Sat, Apr 24, 2010 at 12:20 AM, Victor Duchovni
victor.ducho...@morganstanley.com wrote:
On Sat, Apr 24, 2010 at 12:01:05AM -0400, Jeff Mitchell wrote:
On Thu, Apr 22, 2010 at 6:44 PM, The Doctordoc...@doctor.nl2k.ab.ca wrote:
??Out: 220
)
From: Mail Delivery System mailer-dae...@doctor.nl2k.ab.ca
To: Postmaster postmas...@doctor.nl2k.ab.ca
Subject: Postfix SMTP server: errors from defout.telus.net[204.209.205.55]
Message-Id: 20100424192200.28dab12cf...@doctor.nl2k.ab.ca
Transcript of session follows.
Out: 220 doctor.nl2k.ab.ca
: Sat, 24 Apr 2010 13:22:00 -0600 (MDT)
From: Mail Delivery Systemmailer-dae...@doctor.nl2k.ab.ca
To: Postmasterpostmas...@doctor.nl2k.ab.ca
Subject: Postfix SMTP server: errors from defout.telus.net[204.209.205.55]
Message-Id:20100424192200.28dab12cf...@doctor.nl2k.ab.ca
Transcript of session
The Doctor:
Apr 24 13:20:10 doctor doctor[31]: postfix/smtpd[17053]: 0762D12CFB0D:
client=defout.telus.net[204.209.205.55]
Apr 24 13:20:41 doctor doctor[31]: postfix/cleanup[17311]: 0762D12CFB0D:
message-id=6ef179d262924e5a8c03336971544...@taskercomp
Apr 24 13:22:04 doctor doctor[31]:
Here is my reconstruction from this inadequate logging sample.
Apr 24 13:20:10 doctor doctor[31]: postfix/smtpd[17053]: 0762D12CFB0D:
client=defout.telus.net[204.209.205.55]
Apr 24 13:20:41 doctor doctor[31]: postfix/cleanup[17311]: 0762D12CFB0D:
On Sat, Apr 24, 2010 at 06:36:48PM -0400, Wietse Venema wrote:
Here is my reconstruction from this inadequate logging sample.
Apr 24 13:20:10 doctor doctor[31]: postfix/smtpd[17053]: 0762D12CFB0D:
client=defout.telus.net[204.209.205.55]
Apr 24 13:20:41 doctor doctor[31]:
Perhaps you missed this in prior email:
- Send non-verbose logging.
- Send logging that covers an entire message life cycle from the
SMTP port to final delivery.
Wietse
It never ceases to amaze me, how really bright people (and I'm assuming
everyone on this list has an IQ above
-Original-To: postmaster
Delivered-To: postmas...@doctor.nl2k.ab.ca
Date: Fri, 23 Apr 2010 07:38:48 -0600 (MDT)
From: Mail Delivery System mailer-dae...@doctor.nl2k.ab.ca
To: Postmaster postmas...@doctor.nl2k.ab.ca
Subject: Postfix SMTP server: errors from idcmail-mo2no.shaw.ca[64.59.134.9]
Transcript
version=3.3.1
X-Original-To: postmaster
Delivered-To: postmas...@doctor.nl2k.ab.ca
Date: Fri, 23 Apr 2010 07:38:48 -0600 (MDT)
From: Mail Delivery System mailer-dae...@doctor.nl2k.ab.ca
To: Postmaster postmas...@doctor.nl2k.ab.ca
Subject: Postfix SMTP server: errors from idcmail-mo2no.shaw.ca
Dave Shariff Yadallee - System Administrator a.k.a. The Root of the Problem:
In: DATA
Out: 354 End data with CRLF.CRLF
Out: 451 4.3.0 Error: queue file write error
Session aborted, reason: lost connection
For other details, see the local mail logfile
- End
On Thu, Apr 22, 2010 at 03:02:30PM -0700, brian moore wrote:
On Thu, 22 Apr 2010 15:38:06 -0600
The Doctor doc...@doctor.nl2k.ab.ca wrote:
Out: 220 doctor.nl2k.ab.ca ESMTP Postfix (2.8-20100323)
In: mail-iw0-f172.google.com
Out: 402 4.5.2 Error: command not recognized
On Thu, Apr 22, 2010 at 6:44 PM, The Doctor doc...@doctor.nl2k.ab.ca wrote:
Out: 220 doctor.nl2k.ab.ca ESMTP Postfix (2.8-20100323)
I know this (probably) has little bearing on the problem at hand, but
if I used experimental snapshot releases in a customer-facing setting
I'd be booted out the
On Sat, Apr 24, 2010 at 12:01:05AM -0400, Jeff Mitchell wrote:
On Thu, Apr 22, 2010 at 6:44 PM, The Doctor doc...@doctor.nl2k.ab.ca wrote:
??Out: 220 doctor.nl2k.ab.ca ESMTP Postfix (2.8-20100323)
I know this (probably) has little bearing on the problem at hand, but
if I used experimental
...@doctor.nl2k.ab.ca
To: Postmaster postmas...@doctor.nl2k.ab.ca
Subject: Postfix SMTP server: errors from
mail-iw0-f172.google.com[209.85.223.172]
Transcript of session follows.
Out: 220 doctor.nl2k.ab.ca ESMTP Postfix (2.8-20100323)
In: mail-iw0-f172.google.com
Out: 402 4.5.2 Error
On Thu, 22 Apr 2010 15:38:06 -0600
The Doctor doc...@doctor.nl2k.ab.ca wrote:
Out: 220 doctor.nl2k.ab.ca ESMTP Postfix (2.8-20100323)
In: mail-iw0-f172.google.com
Out: 402 4.5.2 Error: command not recognized
is not a valid SMTP/ESMTP command.
Are you using a Pix?
Out: 451
)
From: Mail Delivery Systemmailer-dae...@doctor.nl2k.ab.ca
To: Postmasterpostmas...@doctor.nl2k.ab.ca
Subject: Postfix SMTP server: errors from
mail-iw0-f172.google.com[209.85.223.172]
Transcript of session follows.
Out: 220 doctor.nl2k.ab.ca ESMTP Postfix (2.8-20100323)
In: mail-iw0
...@doctor.nl2k.ab.ca
Date: Thu, 22 Apr 2010 14:52:20 -0600 (MDT)
From: Mail Delivery Systemmailer-dae...@doctor.nl2k.ab.ca
To: Postmasterpostmas...@doctor.nl2k.ab.ca
Subject: Postfix SMTP server: errors from
mail-iw0-f172.google.com[209.85.223.172]
Transcript of session follows.
Out
On Thu, Apr 22, 2010 at 06:35:52PM -0400, Bill Cole wrote:
In: DATA
Out: 354 End data withCRLF.CRLF
Out: 451 4.3.0 Error: queue file write error
http://www.postfix.org/SMTPD_PROXY_README.html explains one possible source
of this: inability to connect to a before-queue proxy.
This
I just changed the password. sorry i'am r13151.ovh.net
On Tue, 4 Aug 2009 18:06:42 +0200 (CEST), mailer-dae...@r13151.ovh.net
(Mail Delivery System) wrote:
Transcript of session follows.
Out: 220 r13151.ovh.net ESMTP Postfix (2.5.1)
In: HELO 6.mail-out.ovh.net
Out: 250 r13151.ovh.net
I just changed the password. sorry I'm r13151.ovh.net
On Tue, 4 Aug 2009 18:16:52 +0200 (CEST), mailer-dae...@r13151.ovh.net
(Mail Delivery System) wrote:
Transcript of session follows.
Out: 220 r13151.ovh.net ESMTP Postfix (2.5.1)
In: HELO 6.mail-out.ovh.net
Out: 250 r13151.ovh.net
66 matches
Mail list logo