Re: Simple rewrite-from filter in awk

2019-08-18 Thread Gilles Chehade
On Sun, Aug 18, 2019 at 06:49:25PM +0200, Jakub Jirutka wrote:
> Hi,
> 
> I was playing a bit with new proc filters and wrote a very simple filter
> for rewriting email address in both MAIL FROM command and From header
> with the specified email address... in just ~60 lines of AWK!
> 
> https://github.com/jirutka/opensmtpd-filter-rewrite-from
> 
> I'm really impressed how simple yet powerful is the new proc filter
> interface! The fact that you can implement a simple filter in fews lines
> of such limited language as AWK clearly proves the simplicity. No
> language-specific API and bindings, no complex formats or craps like
> gRPC, just plain old processes, stdin/stdout and simple line-oriented
> protocol with delimiter-separated fields. The proper Unix way. <3
> 

You. made. my. day :-)

I'm glad that I resisted the pressure to implement milters and to push a
ton of features in the daemon because the implementation is exactly what
we wanted to achieve: fast, easy and secure. Took time but we are there.

We lose the many milters that are available, but the simplicity allows a
rewrite of any filter we need in a very short time, including maybe some
milter interface on top of our implementation if someone feels like it.

Looking forward to see what the community builds with this !

-- 
Gilles Chehade @poolpOrg

https://www.poolp.orgpatreon: https://www.patreon.com/gilles



Simple rewrite-from filter in awk

2019-08-18 Thread Jakub Jirutka
Hi,

I was playing a bit with new proc filters and wrote a very simple filter
for rewriting email address in both MAIL FROM command and From header
with the specified email address... in just ~60 lines of AWK!

https://github.com/jirutka/opensmtpd-filter-rewrite-from

I'm really impressed how simple yet powerful is the new proc filter
interface! The fact that you can implement a simple filter in fews lines
of such limited language as AWK clearly proves the simplicity. No
language-specific API and bindings, no complex formats or craps like
gRPC, just plain old processes, stdin/stdout and simple line-oriented
protocol with delimiter-separated fields. The proper Unix way. <3

Jakub



signature.asc
Description: OpenPGP digital signature


Re: filter-senderscore for testing

2019-08-18 Thread Gilles Chehade
On Sun, Aug 18, 2019 at 10:39:29AM +0200, Gilles Chehade wrote:
> Hello,
> 
> I have written a second filter:
> 
>   https://github.com/poolpOrg/filter-senderscore
> 
> Senderscore is the reputation scoring built by Return-Path which some of
> the Big Mailers Corp feedback into.
> 
> It isn't bullet-proof but, while good reputations doesn't mean sender is
> good for real, bad reputations generally mean sender is bad for real.
> 
> I'd appreciate some testing and reporting ;-)
> 

Just for the record:

Aug 18 09:02:42 in smtpd[81815]: 0fc6a2f85d8dccfa smtp connected 
address=23.129.64.207 host=207.emeraldonion.org
Aug 18 09:02:42 in smtpd[27481]: : senderscore(23.129.64.207) 
-> 127.0.4.8
Aug 18 09:02:42 in smtpd[81815]: 0fc6a2f85d8dccfa smtp failed-command 
command="" result="550 your IP reputation is too low for this MX"
Aug 18 09:02:42 in smtpd[81815]: 0fc6a2f85d8dccfa smtp disconnected reason=quit
Aug 18 09:02:43 in smtpd[81815]: 0fc6a2f9cbd54d4e smtp connected 
address=23.129.64.216 host=
Aug 18 09:02:43 in smtpd[27481]: : senderscore(23.129.64.216) 
-> 127.0.4.2
Aug 18 09:02:43 in smtpd[81815]: 0fc6a2f9cbd54d4e smtp failed-command 
command="" result="550 your IP reputation is too low for this MX"
Aug 18 09:02:43 in smtpd[81815]: 0fc6a2f9cbd54d4e smtp disconnected reason=quit
Aug 18 09:02:51 in smtpd[81815]: 0fc6a2face31cde3 smtp connected 
address=23.129.64.162 host=162.emeraldonion.org
Aug 18 09:02:51 in smtpd[27481]: : senderscore(23.129.64.162) 
-> 127.0.4.4
Aug 18 09:02:51 in smtpd[81815]: 0fc6a2face31cde3 smtp failed-command 
command="" result="550 your IP reputation is too low for this MX"
Aug 18 09:02:51 in smtpd[81815]: 0fc6a2face31cde3 smtp disconnected reason=quit
Aug 18 09:02:52 in smtpd[81815]: 0fc6a2fb4fd79b8c smtp connected 
address=23.129.64.162 host=162.emeraldonion.org
Aug 18 09:02:52 in smtpd[27481]: : senderscore(23.129.64.162) 
-> 127.0.4.4
Aug 18 09:02:52 in smtpd[81815]: 0fc6a2fb4fd79b8c smtp failed-command 
command="" result="550 your IP reputation is too low for this MX"
Aug 18 09:02:52 in smtpd[81815]: 0fc6a2fb4fd79b8c smtp disconnected reason=quit
Aug 18 09:07:09 in smtpd[81815]: 0fc6a2fc398ab74f smtp connected 
address=193.169.252.212 host=
Aug 18 09:07:09 in smtpd[27481]: : 
senderscore(193.169.252.212) -> 127.0.4.0
Aug 18 09:07:09 in smtpd[81815]: 0fc6a2fc398ab74f smtp failed-command 
command="" result="550 your IP reputation is too low for this MX"
Aug 18 09:07:09 in smtpd[81815]: 0fc6a2fc398ab74f smtp disconnected reason=quit


-- 
Gilles Chehade @poolpOrg

https://www.poolp.orgpatreon: https://www.patreon.com/gilles



filter-senderscore for testing

2019-08-18 Thread Gilles Chehade
Hello,

I have written a second filter:

  https://github.com/poolpOrg/filter-senderscore

Senderscore is the reputation scoring built by Return-Path which some of
the Big Mailers Corp feedback into.

It isn't bullet-proof but, while good reputations doesn't mean sender is
good for real, bad reputations generally mean sender is bad for real.

I'd appreciate some testing and reporting ;-)

-- 
Gilles Chehade @poolpOrg

https://www.poolp.orgpatreon: https://www.patreon.com/gilles