On Tue, Dec 10, 2013 at 09:51:12AM +0000, John Cox wrote:
> Hi
>
> I think that the definition of "from source table" in the man page has
> a small typo. It should be "from source <table>" as the <>s are
> required for the table. If the <>s are omitted then an ip range can be
> used inline?
>
you're right, the doc should use <> but yes, if you omit <> then a
static table is created for the content:
smtpd.conf:
accept from source 192.168.1.1 for any deliver to mbox
smtpd -dv -T table:
[...]
TABLE "<dynamic:0>" type=LIST config=""
"192.168.1.1"
[...]
> 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.
> A small wishlist:
>
> For static or file source tables or other cases where ip addresses can
> be resolved it would be nice if I could have {smarthost.example.net}.
>
> It would also save a bunch of copy/paste (with consequent possible
> typos) if the syntax was extended to allow something like "from
> {local, source <localif>, $smarthost} for any deliver..." which would
> expand to 3 rules like a pf group.
>
We do support this, however we don't recursively lookup tables yet, so:
{ 192.168.1.1, 192.168.1.2, 192.168.2.0/24 } will work
{ local, <foobar> } won't
> Many thanks
>
> John Cox
>
> --
> You received this mail because you are subscribed to [email protected]
> To unsubscribe, send a mail to: [email protected]
>
--
Gilles Chehade
https://www.poolp.org @poolpOrg
--
You received this mail because you are subscribed to [email protected]
To unsubscribe, send a mail to: [email protected]
