nextcloud 27.1.7
Hi everyone, I’m trying to set up notifications on nextcloud on ns8.
From the attachment you can see the error, it tells me to look at the logs of the mail server but I don’t see anything about it.
Is the username really amminnext or is there a typo (adminnext?)
No, but if I put a real user of the domain it is the same …
maybe localhost does not refer to what we use to expect and instead have to use FQDN, VPN IP or else…
1 Like
I think 587 but just try it please…
587 or 25 send email failure .
There could be many issues and the error doesn’t say much, so please check the mail app logs or just do a journalctl -f when you try to setup Nextcloud to get a better error information.
Do you still use the postfix customization for using a smarthost?
Maybe my issue with Mattermost is the same.
I am very curious too to see your logs …
1 Like
Ok thank you . Now I try with journal -f . No, I couldn’t change the type of encryption it supports, probably my knowledge stops there. With postconf I am listed dozens of parameters even with postconf |grep sasl … I don’t understand that much!
Apr 21 12:30:31 ns8 postfix/postscreen[108836]: CONNECT from [10.5.4.1]:49398 to [10.5.4.1]:25
Apr 21 12:30:31 ns8 postfix/postscreen[108836]: ALLOWLISTED [10.5.4.1]:49398
Apr 21 12:30:31 ns8 postfix/smtpd[108837]: connect from cluster-localnode[10.5.4.1]
Apr 21 12:30:31 ns8 rspamd[40983]: #55(rspamd_proxy) <6f7a10>; proxy; proxy_accept_socket: accepted milter connection from ::1 port 47882
Apr 21 12:30:31 ns8 postfix/smtpd[108837]: SSL_accept error from cluster-localnode[10.5.4.1]: -1
Apr 21 12:30:31 ns8 postfix/smtpd[108837]: warning: TLS library problem: error:0A000418:SSL routines::tlsv1 alert unknown ca:ssl/record/rec_layer_s3.c:1586:SSL alert number 48:
Apr 21 12:30:31 ns8 postfix/smtpd[108837]: lost connection after STARTTLS from cluster-localnode[10.5.4.1]
Apr 21 12:30:31 ns8 postfix/smtpd[108837]: disconnect from cluster-localnode[10.5.4.1] ehlo=1 starttls=0/1 commands=1/2
Apr 21 12:30:31 ns8 rspamd[40983]: #55(rspamd_proxy) <6f7a10>; milter; rspamd_milter_process_command: got connection from 10.5.4.1:49398
Apr 21 12:30:31 ns8 rspamd[40983]: #55(rspamd_proxy) <6f7a10>; proxy; proxy_milter_finish_handler: finished milter connection
Apr 21 12:30:31 ns8 nextcloud-app[3012]: 127.0.0.1 - 21/Apr/2024:10:30:31 +0000 "POST /index.php" 400
Apr 21 12:30:31 ns8 traefik[13616]: 192.168.3.2 - - [21/Apr/2024:10:30:31 +0000] "POST /settings/admin/mailtest HTTP/1.1" 400 186 "-" "-" 21869 "nextcloud2-https@file" "http://127.0.0.1:20025" 87ms
Apr 21 12:30:37 ns8 systemd[1]: systemd-hostnamed.service: Deactivated successfully.
I tried on an NS8 server that doesn’t use a smarthost and following settings worked to send a notification from Nextcloud:
many blocks/applications in NS, need a real FQDN, some times with “SSL”, that “SSL” relies on the FQDN , I would double check that first …
No mark . As written before, I was unable to configure the smarthost in ns8, so he uses the default postfix server on the node. If I add my ns7 as a smart host, everything works regularly. To finish independently he is not able to send emails from his MTA. I also wanted to tell you that the modification of the rewrite you suggested yesterday works, if I send an email from a user@intenal.lan it is rewritten with an email fdqn eg. user@outlook.it .
On ns7 I have nextcloud , and the configuration of notifications on nextcloud and localhost works great .
1 Like
I’ll put it on my todo list as you can use the NS7 as workaround in the meanwhile. It looks like an SSL/TLS issue.
Please also try to use settings as in my screenshot.
Maybe it’s an issue that you use internal names in the NC mail config…
EDIT:
Does it work if you enter your smarthost instead of the internal mail server in the NC mail config?
Yes , when i used neth7 yes .
I thought this is the workaround, isn’t it?
The relay host with ns7 I used it and it works. But if I quit ns7, nextcloud must be able to send emails with its MTA (as ns7 currently does). Attached this is the configuration of ns7 and it works without problems.
1 Like
The features you need are already in testing. (except the address rewriting)
You may enable the testing repository and try if it works…
I think you need to remove the previously customized smarthost setting.
Notifications can be sent through using mail app or not:
There are relay rules now:
1 Like