manu@... writes:
the right one. Guaranteed if I have one address, and pretty good if
this is in response to a connection even if I have a few. But, the answer for a wrong connection from THEM to US (for wildcarded US) is still the right answer for milter-greylist's purposes,
environments without patched postfix for quite a a while.
information to provide to a milter.
> Greg Troxel <gdt@...> wrote:If the wildcard is for my address, then it's pretty likely it will be
>
>> I have hard-coded by if_addr in the source for testing for now, but it
>> seems the only real fix is to add if_addr to postfix. A kludge or
>> workaround would be to have wildcard support in p0f and use INADDR_ANY
>> for my adddr.
>
> Can p0f answer a query that has a wildcard? Won't you get an answer for
> another connexion instead of the one you are looking for?
the right one. Guaranteed if I have one address, and pretty good if
this is in response to a connection even if I have a few. But, the answer for a wrong connection from THEM to US (for wildcarded US) is still the right answer for milter-greylist's purposes,
> IMO, a configuration option to set IP and port could help, at list onThat would be good to add because a lot of people will be running in
> non-multihomed setups. Another approach would be to contribute {if_addr}
environments without patched postfix for quite a a while.
> and {daemon_port} macros to Postfix: these should not be very difficultIndeed - one wonders why they don't exist - seems like really obvious
> to implement.
information to provide to a milter.