On Fri, 9 Jan 2026 11:38:06 +0100
Sidney Cadot <[email protected]> wrote:
> Hi,
>
> I have proceeded to the point where an attempt is made for relayed
> mail to be delivered to my ISPs SMTP server.
>
> For relay, I have the following directive in my smtpd.conf:
>
> action "relay_via_ziggo" relay host smtp+tls://smtp.ziggo.nl:587
> auth { "dummy" = "login:password" }
>
> Obviously, login and password are filled in to the relevant values
> corresponding to what is required by my ISP.
>
> My first question is this -- the auth requires a key/value table. As
> to the key, the man page on table(5) says the following:
>
> (BEGIN QUOTE)
>
> In a relay context, the credentials are a mapping of labels and
> username:password pairs:
>
> label1 user:password
>
> The label must be unique and is used as a selector for the proper
> credentials when multiple credentials are valid for a single
> destination. The password is not encrypted as it must be provided to
> the remote host.
>
> (END QUOTE)
>
> This leaves me wondering what I should fill in there. The name of the
> action? The name of the server? Any random label?
>
>
> The behavior I now observe is that smtpd does try to send mail; a TLS
> session is started, and I see the expected to-and-fro between my side
> and the ISP side.
>
> However, while the server advocates "AUTH LOGIN PLAIN", smtpd never
> authenticates (ie it doesn't send an AUTH command), and consequently
> the mail dropoff is rejected by the remote side.
>
> What am I doing wrong?
>
>
> Cheers, Sidney
You may find this post from my blog helpful:
https://simonh.uk/2022/06/26/using-opensmtpd-as-a-personal-relay/
Simon
