On 16/04/2023 21:11, Viktor Dukhovni via Postfix-users wrote:
> Not surprising,
I suspect that the OP did not recognise the $ and # characters in your
instructions as shell prompts (to be omitted from the commands being
executed), and copy/pasted them into his shell as-is.
HTH, Jan
Dear Viktor,
I'm is an old grandfather, and I'm already not thinking straight in Linux and
I'm confused about these adjustments.
But I very need to get this stubborn and also old Videocam to work :-)
You have already helped me a lot in solving this problem, for which I thank you
very much!
If
On Sun, Apr 16, 2023 at 10:05:02PM +0300, Oleksandr wrote:
> > You now need to again post your configuration settings. Post the output
> > of:
> >
># postconf -nf smtpd_tls_cert_file smtpd_tls_key_file smtpd_tls_chain_files
># ls -l $(postconf -xh smtpd_tls_cert_file smtpd_tls_key_file
> You now need to again post your configuration settings. Post the output
> of:
>
# postconf -nf smtpd_tls_cert_file smtpd_tls_key_file smtpd_tls_chain_files
# ls -l $(postconf -xh smtpd_tls_cert_file smtpd_tls_key_file
smtpd_tls_chain_files)
# grep -E '^-(BEGIN|END) ' $(postconf
On Sun, Apr 16, 2023 at 09:24:09PM +0300, Oleksandr wrote:
> I think I've followed all your instructions, and now I've got another
> mistake:
That means that either my instructions had a typo, or your
implementation of correct instructions had a typo.
> Apr 16 21:20:29 mailserver
I think I've followed all your instructions, and now I've got another mistake:
Apr 16 21:20:29 mailserver postfix/smtps/smtpd[2496]: warning: No server certs
available. TLS won't be enabled
Apr 16 21:20:30 mailserver postfix/smtps/smtpd[2496]: connect from
unknown[192.168.8.144]
Apr 16 21:20:30
On Sun, Apr 16, 2023 at 07:49:00PM +0300, Oleksandr wrote:
> > Did you reconfigure Postfix to use the generated PEM file
> > as your certificate and private key file?
>
> I didn't know it had to be done... I just do what you recommend. How
> do I need to do this reconfiguration? Please tell
> Did you reconfigure Postfix to use the generated PEM file
> as your certificate and private key file?
I didn't know it had to be done...
I just do what you recommend.
How do I need to do this reconfiguration?
Please tell me about this in more detail.
And another question: do these commands
On Sun, Apr 16, 2023 at 06:03:09PM +0300, Oleksandr via Postfix-users wrote:
> Okay, Viktor! I executed these commands and got this result:
>
> $ dnsname=mailserver.mail.lan
> $ rm certkey.pem
> rm: Unable to delete 'certkey.pem': No such file or directory
> user@mailserver:~$ openssl req -new
Okay, Viktor! I executed these commands and got this result:
$ dnsname=mailserver.mail.lan
$ rm certkey.pem
rm: Unable to delete 'certkey.pem': No such file or directory
user@mailserver:~$ openssl req -new -nodes -newkey rsa:2048 -keyout /dev/stdout
\
-config <(printf
On Sun, Apr 16, 2023 at 03:07:38AM +0300, Oleksandr via Postfix-users wrote:
> Yes, it looks like this :-)
> But I was hoping that it would be enough to make corrections in the main.cf
> and master.cf, and Postfix friendship with the camera would be restored.
It isn't actually Postfix
> ... so asking to have PF modified to accommodate a client’s
> old & outdated firmware seems a bit like the tail waggin’
> the dog don’t you think?
Yes, it looks like this :-)
But I was hoping that it would be enough to make corrections in the main.cf and
master.cf, and Postfix friendship
On Sun, Apr 16, 2023 at 12:30:14AM +0300, Oleksandr wrote:
> Viktor, How you have analyzed everything perfectly! :-)
>
> Of course, I cannot influence the camera firmware, it is old and there
> are no new firmware.
>
> But maybe you can change the Postfix settings so that he makes friends
>
“…maybe you can change the Postfix settings so that he makes friends
with this camera and successfully receives mail from it…”
PF already does this - in plain-text. PF handles TLS\SSL properly so
asking to have PF modified to accommodate a client’s old & outdated
firmware seems a bit like
Viktor, hHow you have analyzed everything perfectly! :-)
Of course, I cannot influence the camera firmware, it is old and there are no
new firmware.
But maybe you can change the Postfix settings so that he makes friends with
this camera and successfully receives mail from it?
--
On Sat, Apr 15, 2023 at 10:09:10PM +0300, Oleksandr wrote:
> Sorry, I temporarily changed the IP camera to 192.168.8.144, but it doesn't
> affect anything.
>
> So, I executed the command:
>
> # tcpdump -s0 -w file.pcap tcp port 465 and host 192.168.8.144
>
> The result is in the
Sorry, I temporarily changed the IP camera to 192.168.8.144, but it doesn't
affect anything.
So, I executed the command:
# tcpdump -s0 -w file.pcap tcp port 465 and host 192.168.8.144
The result is in the attachment.
--
file.pcap
Description: application/vnd.tcpdump.pcap
Viktor Dukhovni via Postfix-users skrev den 2023-04-15 20:12:
On Sat, Apr 15, 2023 at 08:09:58PM +0200, Benny Pedersen via
Postfix-users wrote:
> As stated above, there was no need. What's needed now is a PCAP file
> with a full recording of exactly one TCP connection between the camera
> and
On Sat, Apr 15, 2023 at 08:09:58PM +0200, Benny Pedersen via Postfix-users
wrote:
> > As stated above, there was no need. What's needed now is a PCAP file
> > with a full recording of exactly one TCP connection between the camera
> > and Postfix on port 465.
>
> first remove the 2nd port 465
>
Viktor Dukhovni via Postfix-users skrev den 2023-04-15 20:06:
As stated above, there was no need. What's needed now is a PCAP file
with a full recording of exactly one TCP connection between the camera
and Postfix on port 465.
first remove the 2nd port 465
imho postfix list this as error ?
Oleksandr via Postfix-users skrev den 2023-04-15 19:37:
Please, here are the results of executing this command in attachment:
port 465 is twice in master
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to
On Sat, Apr 15, 2023 at 08:37:14PM +0300, Oleksandr wrote:
> > > provide postconf -nf not just raw file, and postconf -Mf not just raw
> > > file
> >
> > No longer necessary.
>
> Please, here are the results of executing this command in attachment:
As stated above, there was no need. What's
> > provide postconf -nf not just raw file, and postconf -Mf not just raw
> > file
>
> No longer necessary.
Please, here are the results of executing this command in attachment:
--
smtp inet n - y - 1 postscreen
smtpd pass - - y
On Sat, Apr 15, 2023 at 05:57:51PM +0200, Benny Pedersen via Postfix-users
wrote:
> add 192.168.1.44 to mynetwork in postfix main.cf, in master.cf allow
> permit_mynetwork before permit
Irrelevant. The TLS connection setup hadn't completed yet.
> but best is simply to make another
postfix--- via Postfix-users skrev den 2023-04-15 17:12:
Apr 14 23:00:08 mailserver postfix/smtps/smtpd[1653]: connect from
unknown[192.168.1.44]
Apr 14 23:00:08 mailserver postfix/smtps/smtpd[1653]: SSL_accept error
from unknown[192.168.1.44]: Connection reset by peer
Apr 14 23:00:08
On Sat, Apr 15, 2023 at 05:39:21PM +0300, Oleksandr via Postfix-users wrote:
> However, Postfix refuses to accept mail from the video camera and
> demonstrates these lines in the log:
That's not an accurate statement. Postfix is happy to accept mail from
the camera, but the camera aborts the
On Sat, 15 Apr 2023 11:12:51 -0400
postfix--- via Postfix-users wrote:
> > Apr 14 23:00:08 mailserver postfix/smtps/smtpd[1653]: connect from
> > unknown[192.168.1.44]
> > Apr 14 23:00:08 mailserver postfix/smtps/smtpd[1653]: SSL_accept error from
> > unknown[192.168.1.44]: Connection reset by
Apr 14 23:00:08 mailserver postfix/smtps/smtpd[1653]: connect from
unknown[192.168.1.44]
Apr 14 23:00:08 mailserver postfix/smtps/smtpd[1653]: SSL_accept error from
unknown[192.168.1.44]: Connection reset by peer
Apr 14 23:00:08 mailserver postfix/smtps/smtpd[1653]: lost connection after
28 matches
Mail list logo
