>[snip]
>Well you don't see the issue for your use-case, the issue is that
>for pretty much every other use-case this is not what's desired.
My argument would be that if you don't want that behaviour then you
shouldn't use the modifier, however ...
>We discussed shortly a new kind of rules with e
Hi,
I'm currently running OpenSMTPD on OpenBSD in a KVM on SmartOS after moving my
mail server from a physical machine. In order to reduce the OpenBSD in KVM I
attempted to build OpenSMTPD in a SmartOS Zone, but it cannot find db.h. The
reason is due to Joyent making /usr read-only and placin
On Fri, Mar 07, 2014 at 08:40:29AM +, John Cox wrote:
> Hi
>
> >> Is there any chance we could have a rule of the form
> >>
> >> accept for any virtual no-bounce relay
> >>
> >> such that if the virtual lookup fails then processing continues to the
> >> next line rather than generating a
Hi
>> Is there any chance we could have a rule of the form
>>
>> accept for any virtual no-bounce relay
>>
>> such that if the virtual lookup fails then processing continues to the
>> next line rather than generating a bounce message. This would
>> simplify the generation of forwarding table
