On Mon, Jan 16, 2012 at 10:20:48AM -0500, Wietse Venema wrote: > > It isn't difficult to add the local TCP port number to the Dovecot > > SASL request. May I suggest that this be added? > > You may suggest, but you may not know what you're asking for. Adding > server (local) port support to Postfix was discussed a few weeks > ago here.
I'm sorry, I hope I'm not duplicating anything... but I didn't see this topic in the list archive. > For consistency server port support needs to work in the exact same > way as the existing code for client (remote) port support. According It sounds like you're saying that support for testing the server port shouldn't be added at all unless it is added consistently throughout Postfix. I disagree that just applying my patch to the Dovecot SASL code without adding support for the server port in many other places in Postfix would cause user surprises. The fact that you would be able to meaningfully use "%a" (a Dovecot variable that expands to the server port number) somewhere Dovecot auth configuration doesn't imply anything to users about what you can and can't do in Postfix. Rather, it is more likely that the current behaviour causes a surprise: Dovecot knows the port number is 143 when it authenticates an IMAP request but it thinks it's 0 (because it doesn't know it) when it authenticates an SMTP request. -Phil
