Thanks you very much for you continuing explanations. I'll see if I can find to fold some of what you have clarified into the wiki, but it might take till Christmas before I have any concentrated spare time to do that. (It might be nice if there was a link to the wiki somewhere obvious on www.opensmtpd.org as I'm not sure where it is meant to be - the wiki I found on github looks very empty)
> [snip] >> I spent quite a while wondering why "from source em2 for any >> deliver..." (where em2 is a valid interface used in a previous listen >> statement) didn't do what I wanted (due to inadequate man reading). >> Some sort of error or warning in cases like that would be useful or is >> there some reason why it was accepted but just failed to match >> anything I tried? >> > >It is accepted because it's a string and we should support hostnames in >there but now that you mention it we haven't tried this in a while as >most people including ourselves use ip addresses, tables or networks >here, I'll give a try and fix if it's broken. So how was my em2 being interpreted? Was it being looked and translated to an IP address via DNS (as em2.example.net) when the smtpd.conf was parsed or when a message comes in? In either of these two case I would hope for at least a warning that it couldn't resolve. Or was it some sort of text match - if so against what? Many thanks John Cox P.S. When, if ever, is smtpd.conf reread? -- You received this mail because you are subscribed to [email protected] To unsubscribe, send a mail to: [email protected]
