> On Nov 12, 2019, at 16:42, gil...@poolp.org wrote:
>
> November 12, 2019 5:45 PM, "Chris Ross" <cross+open...@distal.com> wrote:
>> Well, I don’t know how easy that would be either. These were both, I
>> believe, written by Gilles. I
>> would appreciate your input Gilles. I see both of these particularly tools,
>> opensmtpd filters, are
>> Golang only and require nothing beyond the standard library. It would be
>> ugly, but I might be able
>> to hack them into my system with the go fork you mention above. Whether or
>> not I _want_ to is more
>> complicated. :-/
>>
>
> I don't know what input to provide here :-)
Just your experience, I guess. Thank you for that. ;-)
> The API was designed so that it is very easy to write filters using tools you
> know, so if you wonder
> if you should hack an old go fork or use an existing filter as a model to
> write your own, my take is
> to go the second option as you will avoid having to maintain a huge hack and
> might just have a thing
> working in an hour or so.
>
> There is a C library by martijn@ that can ease writing a C filter btw.
Great to know that, too. Thanks. I’ll take a swing at that. Might be faster
to write in python, but if
there’s already a library to give structure, C will be as easy and is preferred.
- Chris
