Am 03.11.2016 um 20:57 schrieb Viktor Dukhovni:
Good morning.
> Perhaps "posttls-finger" is left over from an earlier install? Did
> you build and install Postfix from source?
I reinstalled the distro pf package and re-compiled pf snapshot 1101 again.
Now posttls-finger works again. Whyever.
>
On Thu, Nov 03, 2016 at 09:38:39PM +0100, Florian Piekert wrote:
> >> -rwxr-xr-x 1 root root 34768 Apr 13 2016 /usr/sbin/posttls-finger*
> >
> > Perhaps "posttls-finger" is left over from an earlier install? Did
> > you build and install Postfix from source?
>
> posttls-finger most
Am 03.11.2016 um 20:57 schrieb Viktor Dukhovni:
Hello Viktor,
you are correct, it is compiled & install from the source, like I did the last
ten+? years on all of my machines. No issues on ubuntu 14.04, opensuse, or
others. Only on 16.04. it causes me a pain.
I installed postfix from scratch
On Thu, Nov 03, 2016 at 06:05:50PM +0100, Florian Piekert wrote:
> Since there is no tlsproxy running at the moment (removed the modifications
> from Wietse and restarted pf, let's wait...?) I can't provide that output
> at the moment. Or do you have a suggestion how to get one up & running?
You
Am 03.11.2016 um 17:29 schrieb Viktor Dukhovni:
Hello Viktor, Wietse and everybody,
since there is no tlsproxy running at the moment (removed the modifications
from Wietse and restarted pf, let's wait...?) I can't provide that output at
the moment. Or do you have a suggestion how to get one up
> On Nov 3, 2016, at 12:29 PM, Viktor Dukhovni
> wrote:
>
> # grep "tlsproxy/\[$pid\]" /var/log/mail.log | tail
Oops, misplaced '/' there, it should of course be:
# grep "/tlsproxy\[$pid\]" /var/log/mail.log | tail
--
Viktor.
On Thu, Nov 03, 2016 at 12:48:01PM +0100, Florian Piekert wrote:
> Good morning everybody,
>
> I was wondering for quite some weeks now how to fix this issue with my
> postfix. I had a brief discussion with Ralf Hildebrandt and he suggested
> asking via the users lists, that's what I am doing
Am 03.11.2016 um 15:58 schrieb Wietse Venema:
> postconf \
> 'postscreen_bare_newline_enable = no' \
> 'postscreen_non_smtp_command_enable = no' \
> 'postscreen_pipelining_enable = no'
>
> postfix reload
Nov 3 16:03:51 blueberry postfix/smtp[12959]: SSL_connect:before/connect
Florian Piekert:
> ==> mail/mail.log <==
> Nov 3 08:50:29 blueberry postfix/tlsproxy[8057]: CONNECT from
> [2a01:111:f400:fe02::31f]:39552
Does it make a difference after:
postconf \
'postscreen_bare_newline_enable = no' \
'postscreen_non_smtp_command_enable = no' \
* Florian Piekert :
> Nov 3 08:50:30 blueberry postfix/tlsproxy[8057]: SSL_accept:unknown state
I checked my logs and couldn't find any log entries like the one above.
Hm, I am not using smtp(d)_tls_loglevel=2, but 1.
> smtp_tls_loglevel = 2
> smtpd_tls_loglevel = 2
--
Am 03.11.2016 um 14:26 schrieb Fazzina, Angelo:
Hello Angelo,
please find attached my output, looks pretty good to me, similar to yours.
> Hi Florian,
> I am curious if you ran a basic telnet test of your SSL config, trying to
> connect over port 465 or 587 ?
> Sorry for not reading your
Hi Florian,
I am curious if you ran a basic telnet test of your SSL config, trying to
connect over port 465 or 587 ?
Sorry for not reading your attachments.
I am attaching one file of the command and its output, showing example test
over both ports.
Does your postfix respond like my example or
12 matches
Mail list logo