FAQ
Seem to be getting this a lot on ffml at here - spam comes from ffml-owner,
but that address is not subscribed, so it bounces, and bombards six people
with rejected spam. Is there a more elegant way to deal with this than add
subscriber to a 'summarily discard all' rule?

-Dennis

Search Discussions

  • Adam McGreggor at Jan 31, 2010 at 7:35 pm

    On Sun, Jan 31, 2010 at 10:59:13AM -0800, Dennis Carr wrote:
    Seem to be getting this a lot on ffml at here - spam comes from ffml-owner,
    but that address is not subscribed, so it bounces, and bombards six people
    with rejected spam. Is there a more elegant way to deal with this than add
    subscriber to a 'summarily discard all' rule?
    Stop it earlier?

    <http://exim.org/howto/mailman21.html#lispol> may be of interest if
    you're using Exim.

    Some mailadmins may prefer a 'discard' over a 'deny'.

    --
    "In matters of grave importance, style, not sincerity, is the vital
    thing"
    -- The Importance of Being Earnest
  • Mark Sapiro at Jan 31, 2010 at 7:37 pm

    Dennis Carr wrote:
    Seem to be getting this a lot on ffml at here - spam comes from ffml-owner,
    but that address is not subscribed, so it bounces, and bombards six people
    with rejected spam. Is there a more elegant way to deal with this than add
    subscriber to a 'summarily discard all' rule?

    Adding listname-owner at ... to discard_these_nonmembers actually seems
    like a pretty good solution to me.

    The only other thing you might do in Mailman is try some
    header_filter_rules to block the spam.

    Of course, blocking it in the MTA ahead of Mailman is the best solution.

    --
    Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupmailman-users @
categoriespython
postedJan 31, '10 at 6:59p
activeJan 31, '10 at 7:37p
posts3
users3
websitelist.org

People

Translate

site design / logo © 2022 Grokbase