> We run tcp25 from /bin/service and smtpd is able to received mail via TLS.
>
>>From factotum(4):
>
> The factotum owner can use any key stored by factotum. Any
> key may have one or more owner attributes listing the users
> who can use the key as though they were
We run tcp25 from /bin/service and smtpd is able to received mail via TLS.
>From factotum(4):
The factotum owner can use any key stored by factotum. Any
key may have one or more owner attributes listing the users
who can use the key as though they were the owner. F
> Hm, /rc/bin/service/tcp25 runs as "none" and where as it can read the
> certificate *that's easy), but I could have sworn it could not access the
> "eve" factotum (I use "proxima" as a replacement for "bootes", I have a
> feeling there are namespace issues that Bell Labs ought to take into
>
> I can't answer all your questions immediately, but as long as smtpd
> can read the certificate it needs for TLS (typically
> /sys/lib/ssl/smtpd-cert.pem), tcp25 can reside in /rc/bin/service.
Hm, /rc/bin/service/tcp25 runs as "none" and where as it can read the
certificate *that's easy), but I
I can't answer all your questions immediately, but as long as smtpd
can read the certificate it needs for TLS (typically
/sys/lib/ssl/smtpd-cert.pem), tcp25 can reside in /rc/bin/service.
There needs to be a corresponding key in your cpu server(s)'s bootes's
factotum. We load ours automatically fr
The objective is to configure an authenticating SMTP server, so if
somebody has a formula for that, I'm game.
As I failed to figure it all out for myself (but thanks to those who
contributed to the wiki page on how to do authenticated outgoing
SMTP), let me explain where I'm stumped.
The diagnost
