greylist based on sender-domain/recipient tuples

[d.mul...@gmail.com]

Hi!
Could you explain me, how can I write mopherd.acl rule to greylisting by sender domain\recipient address?
I need that if one email get status=visa, then all email from the same domain automaticaly get status visa  without deferred
I had wrote the next rules
envrcpt counter_relay == null greylist delay 5m deadline 24h visa 192h
envrcpt counter_relay >= 1 continue
but it is not works. Every next mail from the same domain get status=defer.
looks like mopher marked emails as statu=visa if  all tuple (server, sender address and recipient address) coincides

[Manuel Badzong]

On Thu, Jan 19, 2017 at 06:38:39AM -0800, d.mul...@gmail.com wrote:
> envrcpt counter_relay == null greylist delay 5m deadline 24h visa 192h
> envrcpt counter_relay >= 1 continue

Unless you are running a very old version of mopher you want to use 'is null'
instead of '== null'. The result of '== null' is always null.

Keep in mind counter_relay counts successfully delivered messages by an
individual IP address. Counter_relay usually does not work with server farms.
Is it possible this particular message is from a server farm?

In newer versions of mopher you can use counter_origin, wich uses the RDNS
domain as key and is less strict than counter_relay and thus works with most
server farms.

I guess you want to do something like this:

envrcpt counter_origin >= 1 continue
envrcpt greylist delay 5m deadline 24h visa 192h

Just a thought - counter_origin >= 1 is a very low threshold. I personally would
recommend setting the bar a little higher.

Kind regards

Manuel

[d.mul...@gmail.com]

Thank you, I will try it today.
"Is it possible this particular message is from a server farm? " - no, I had tried sent email from my local PC

"Just a thought - counter_origin >= 1 is a very low threshold. I personally would

recommend setting the bar a little higher. " - I use counter_origin >= 1 only for testing mopher)

As to  counter_origin, I use mopherd-0.6.0, is this a latest version of mopher? If it is not then where I can find latest version mopher with manual?
I have read man mopherd.acl and mopher.org/doc/man/mopherd.acl.5.html1qq and don`t find any information about it... When I use counter_origin mopher does not start with error "unknown variable "counter_origin" in "/etc/mopher/mopherd.acl" on line 1"

четверг, 19 января 2017 г., 21:19:49 UTC+3 пользователь Manuel Badzong написал:

[Manuel Badzong]

On Thu, Jan 19, 2017 at 09:18:17PM -0800, d.mul...@gmail.com wrote:
> "Is it possible this particular message is from a server farm? " - no, I had
> tried sent email from my local PC

In this case counter_relay should work. Can you post your mopherd.acl?

> As to  counter_origin, I use mopherd-0.6.0, is this a latest version of mopher?
> If it is not then where I can find latest version mopher with manual?
> I have read man mopherd.acl and mopher.org/doc/man/mopherd.acl.5.html1qq and
> don`t find any information about it... When I use counter_origin mopher does
> not start with error "unknown variable "counter_origin" in "/etc/mopher/
> mopherd.acl" on line 1"

Sorry, my bad. I just reviewed the code. In 0.6.0 '== null' is fine and also
counter_origin does not exist in 0.6.0.

HEAD hasn't changed for quite a while, so I think it's time for a new release.
I will update the manual.

Thank you for bringing that up.

[d.mul...@gmail.com]

My mopherd.acl :
envrcpt counter_relay >= 5 accept
envrcpt greylist delay 1m deadline 24h visa 192h

and it`s works fine, I just thought that means relay=origin.
I will look forward when you release new version mopher with counter_origin support. It is really great function.
I am sorry for my audacity, but may be you can tell me tentative dates of release?

пятница, 20 января 2017 г., 10:48:43 UTC+3 пользователь Manuel Badzong написал:

[Manuel Badzong]

On Fri, Jan 20, 2017 at 12:33:14AM -0800, d.mul...@gmail.com wrote:
> I am sorry for my audacity, but may be you can tell me tentative dates of
> release?

Because nobody worked on mopher for some time, we need to review all code
changes and update the docs.

I would say early to mid february is realistic.

Kind regards

Manuel

[d.mul...@gmail.com]

It is a good news. I think mopher it is good stuff with a big capability, at least it seems that mopher has more then milter-greylist for example)
So, I will trace your updates and I hope it is happens in a short time.
In any case, thank you)

пятница, 20 января 2017 г., 15:41:32 UTC+3 пользователь Manuel Badzong написал:

[d.mul...@gmail.com]

Hello Manuel!
I sorry for my annoyance, but have you any updates about new version of mopher?))

пятница, 20 января 2017 г., 15:41:32 UTC+3 пользователь Manuel Badzong написал:

[Petar Bogdanovic]

On Mon, Apr 10, 2017 at 03:16:32AM -0700, d.mul...@gmail.com wrote:
> I sorry for my annoyance, but have you any updates about new version
> of mopher?

Unfortunately, it still needs some docs but since mopher 0.7 will be
pretty much what (the well tested) master is now, you could just build
and run master in the meantime.

Petar

[d.mul...@gmail.com]

Many thanks! I will to try.

понедельник, 10 апреля 2017 г., 22:58:56 UTC+3 пользователь Petar Bogdanovic написал: