Yahoo Groups archive

Milter-greylist

Index last updated: 2026-04-28 23:32 UTC

Message

Re: [milter-greylist] block SRS senders

2016-09-04 by Jim Klimov

4 \u0441\u0435\u043d\u0442\u044f\u0431\u0440\u044f 2016�\u0433. 14:03:03 CEST, "Marcus Schopen lists-yahoogroups@... [milter-greylist]" <milter-greylist@yahoogroups.com> \u043f\u0438\u0448\u0435\u0442:
>On 2016-09-03 16:08, Marcus Schopen lists-yahoogroups@... 
>[milter-greylist] wrote:
>> Hi Emmanuel,
>> 
>> I get a lot of spam forwarded from an external server to my server.
>> The
>> used SRS return path e.g. looks like this:
>> 
>> <srs0+uc/j=ux=mailer-service.de=postmaster@...>
>> 
>> To block the forwarding server udag.de in sendmail access is not an
>> option, because ham is also forwarded. Sendmail's access file doesn't
>> support regular expressions on "From:" filter and I don't see further
>> options with sendmail. Is there a way to block those messages with
>> milter-greylist using something like this:
>> 
>> -------
>> list "superspammer" from { \
>> *=mailer-service.de=*@... \
>> }
>> 
>> racl blacklist list superspammer msg "Spam blocked" flushaddr
>> -------
>> 
>> I'm using milter-greylist 4.3.9-1 on Ubuntu 12.04 LTS, but could
>build
>> 
>> backports to newer version if necessary.
>
>This seems to work
>
>-----------
># Test
>list "SUPERSPAMMER" from { \
>         /peter.lustig@.../ \
>         /.*mailer-service\.de.*@udag\.de$/ \
>}
>
>racl blacklist list "SUPERSPAMMER" msg "Bad reputation - %f listed on 
>SPAM blacklist %a" flushaddr
>-----------
>
>But the line
>
>   /.*mailer-service\.de.*@udag\.de$/ \
>
>never matches on
>
>  <srs0+uc/j=ux=mailer-service.de=postmaster@...>
>
>I've tested different regular expression, but without success. Any
>ideas 
>how the regular expression must look like?
>
>Ciao
>Marcus

Just in case, check regexes are on in your build and maybe the domain-matching keyword (don't have docs atm) acts up?
--
Typos courtesy of K-9 Mail on my Samsung Android

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.