> 10€ for the project :-)
Haha, I'm sure a clever lawyer would have arguments for either of us already
winning that bet.
> Hm, maybe you need a "application password".
>
> Try
> # smtpd -dv -Ttransfer
>
> There will be the line "mta: 0x: >>> AUTH PLAIN SomeBase64Code
>
> $ echo
Looks good.
I bet money that the username:password pair in is just wrong :-)
How much would you like to wager? :)
10€ for the project :-)
I copied and pasted the info into a weblogin and it worked (unfortunately?)
Hm, maybe you need a "application password".
Try
# smtpd -dv -Ttransfer
> Looks good.
> I bet money that the username:password pair in is just wrong :-)
How much would you like to wager? :)
I copied and pasted the info into a weblogin and it worked (unfortunately?)
The format of my secrets file is:
my_relay sender:PASSWORD
> Don't forget to run
> # smtpctl update
For the server I am trying to connect, I was told to use 587 if 25 didn't work,
so I've been trying both.
You should use 587.
Here is the smtpd.conf now:
Looks good.
I bet money that the username:password pair in is just wrong :-)
Don't forget to run
# smtpctl update table secrets
after
> What happened "late March"? Did you reboot the system or did smtpd crash?
I think I rebooted after applying these patches:
015: SECURITY FIX: March 22, 2019 All architectures
A state in pf could pass ICMP packets to a destination IP address that did not
match the state.
A source code patch
==
/etc/mail/smtpd.conf diffs (-OLD +NEW)
==
--- /var/backups/etc_mail_smtpd.conf.current Fri Feb 22 01:30:23 2019
+++ /etc/mail/smtpd.conf Fri Mar 15 20:49:37 2019
@@ -17,3 +17,5 @@
# match from any for domain "example.org" action "local"
match for local action "local"
Am 05.04.2019 um 05:58 schrieb Juan Trippe:
What's the alternative? Did you make an update?
I don't know, it was about a month ago. I was trying to get the relay working so
I was making changes to the smtpd.conf file. AFAIK I was restarting smtpd after
each edit and stopped when it worked.
