Support 'senders' and 'received-auth' in 'listen on socket'

[Wolf480pl]

Currently listen on socket accepts only filters option.
It would be useful if it also accepted senders and received-auth options, which would behave like in regular listen directives.

[poolpOrg]

I'll look into this next week during the hackathon ;-)

[Wolf480pl]

I started looking through the source code to see if it's been already implemented, and if not, how hard it would be to implement.

Apparently, if the config grammar was slightly changed to allow these two options in listen on socket, they would almost work, except s->username on the smtp_session would be empty.

Looks like the control process already checks the user's effective uid with getpeereid, and sends it to the pony process, so it's just a matter of taking it from here, resolving it to a username and putting the username in the smtp_session somewhere around here?

Oh, and the uid->username lookup would have to go through the lookup process, cause it requires /etc/passwd access... looks like the hard part.

[ngortheone]

@poolpOrg this looks a bit old.
What is the current status and are there any future plans regarding this?

[poolpOrg]

The PR was not adding the feature correctly and adding it correctly is tricky.

The status is "this might require a rework of how we consider the socket in the daemon to be done right", so not closing as wontfix but keeping open as don't hold your breath.

[crabctrl]

Any update on this? Being able to use senders in particular feels quite important, as otherwise there's seemingly no way of restricting what addresses local users can use.