On Thu, Jan 24, 2019 at 11:34:39PM -0700, phoenixsagar wrote:
> Issue : postfix is marking unexpired certificates as expired randomly for
> these certificate chains.
Postfix does not contain any code for verifying certificate expiration,
that's done by OpenSSL. OpenSSL has not history of the pro
Hi Viktor,
These wire pcap is taken at same time when issue occurred.
Above mentioned certificates are same certificates for which postfix is
marking expired. For this chain only issue occurred and after some time
marked as valid.
Issue : postfix is marking unexpired certificates as expired ran
On 24 Jan 2019, at 21:00, Peter wrote:
> On 21/01/19 23:43, phoenixsagar wrote:
>> notAfter: utcTime (0)
>> utcTime: 20-05-18 22:06:55 (UTC)
> ...
>> notAfter: utcTime (0)
>>
On 24 Jan 2019, at 18:07, Viktor Dukhovni wrote:
> This may be especially important with submission, where various
> peripheral devices (fax-to-email, printers, ...) may only support
> TLSv1. So the "buster" system-wide default of TLSv1.2 and up may
> cause problems.
The least likely to be patch
On 21/01/19 23:43, phoenixsagar wrote:
notAfter: utcTime (0)
utcTime: 20-05-18 22:06:55 (UTC)
...
notAfter: utcTime (0)
utcTime: 25-09-04 00:00:00 (UTC)
Those both look
On Mon, Jan 21, 2019 at 11:06:31PM -0700, phoenixsagar wrote:
> See the posted certificates from wire.
> I am not getting why this is random behaviour. At some time only certificate
> marked as expired and after some time same certificate gets marked as valid.
Perhaps you're reaching different ba
On Thu, Jan 24, 2019 at 05:19:44PM -0500, Scott Kitterman wrote:
> I'm the Debian postfix
> maintainer and part of why I'm on this list is to help with our distro
> specific issues.
Speaking of "distro-specific issues", I just today came across a
Debian "buster" system where the OpenSSL version
No. Well designed ones won't do that to you.
Scott K
On Friday, January 25, 2019 01:51:55 AM Matt Wong wrote:
> This gets closer - and as far as I tested, it's not the name, but rather
> the ip to wich inet_interfaces is set to. Default seems "all" - wich
> includes the IPs of all interfaces + l
This gets closer - and as far as I tested, it's not the name, but rather
the ip to wich inet_interfaces is set to. Default seems "all" - wich
includes the IPs of all interfaces + loopback - and it seems the error
is caused by some quirk that postfix doesn't want to deliever to any ip
it self is
On Thu, Jan 24, 2019 at 05:15:58PM -0600, Noel Jones wrote:
> On 1/24/2019 4:54 PM, Matt Wong wrote:
>
> > Well, I got a bit further: When listing mailq postfix complains
> > about "127.0.0.1 loop back to myself".
>
> Change the postfix "myhostname" parameter to something other than
> what James
On 1/24/2019 4:54 PM, Matt Wong wrote:
> Well, I got a bit further: When listing mailq postfix complains
> about "127.0.0.1 loop back to myself".
Change the postfix "myhostname" parameter to something other than
what James uses.
-- Noel Jones
On 1/24/2019 4:09 PM, Matt Wong wrote:
> Well, I'll give mini-smtp a try now - let's see if this fits my
> purposes better.
>
> About the brain-dead system: isn't it supposed that the config-tool,
> wich, correct me if I'm wrong, belongs to postfix itself is run at
> its start-up? Also, if config.
*cut out rage about linux*
Well, I got a bit further: When listing mailq postfix complains about
"127.0.0.1 loop back to myself".
https://james.apache.org/server/james_and_sendmail.html mentions some
this way and how sendmail once had to been told "yea, don't worry, I
know what I do" - is the
On Thursday, January 24, 2019 11:09:25 PM Matt Wong wrote:
> Well, I'll give mini-smtp a try now - let's see if this fits my purposes
> better.
>
> About the brain-dead system: isn't it supposed that the config-tool,
> wich, correct me if I'm wrong, belongs to postfix itself is run at its
> start-
Well, I'll give mini-smtp a try now - let's see if this fits my purposes
better.
About the brain-dead system: isn't it supposed that the config-tool,
wich, correct me if I'm wrong, belongs to postfix itself is run at its
start-up? Also, if config.postfix generates master.cf from sysconfig -
s
On 1/24/2019 3:12 PM, Matt Wong wrote:
> Hi Noel Jones,
>
> sadly, this didn't the trick. I can change /etc/postfix/master.cf
> and call postfix reload - then smtpd shuts down and james is able to
> start its smtp server. Strangely, when using systemctl restart
> postfix master.cf is rebuild from
Hi Noel Jones,
sadly, this didn't the trick. I can change /etc/postfix/master.cf and
call postfix reload - then smtpd shuts down and james is able to start
its smtp server. Strangely, when using systemctl restart postfix
master.cf is rebuild from /etc/sysconfig/postfix - smtpd is re-enabled
a
17 matches
Mail list logo
