From: Marek Lindner <lindner_marek@yahoo.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] Fwd: Re: Debian extra modules
Date: Tue, 6 Oct 2009 21:27:42 +0800 [thread overview]
Message-ID: <200910062127.42925.lindner_marek@yahoo.de> (raw)
In-Reply-To: <200910061355.49409.sven.eckelmann@gmx.de>
On Tuesday 06 October 2009 19:55:46 Sven Eckelmann wrote:
> As far as I know it isn't a part which is currently not targeted for
> linux-2.6 (staging or netdev) as this isn't self contained, but just a
> "hack" to improve gateway speed with batmand. Marek has to decide what to
> do with it further.
That is a qood question. It is self-contained as well but I don't think it
makes much sense bringing it into staging as it is just a "hack". :)
I'm not sure what the best path forward might be. Does it hurt keeping it the
way it is ?
> Parts which are important:
> * TODO list for staging inside batman-adv folder
> * removed compat.h and remaining LINUX_VERSION_CODE (net_device_ops,
> unregister_chrdev)
> * clean Makefile and Kconfig
> * anyone who says how the further development should be done
> * anyone who sends the patch to Greg (probably Marek)
I think most of the things listed here are already done. It just needs to come
together. I'm confident that this will happen soon.
> @Marek: Is the postfix server configured to do greylisting? If yes, do you
> have a some statistics about how many spam mails come through and will be
> kicked out by the mailinglist system? If it isn't that much I would do some
> moderation for some months before we maybe move to a better option.
The postifx setup is quite simple at the moment: It rejects all unknown /
unregistered mail. Greylisting is not in place yet. I quickly ran pflogsumm to
give you an impression:
Per-Day Traffic Summary
date received delivered deferred bounced rejected
--------------------------------------------------------------------
Sep 27 2009 110 107 153 16 4874
Sep 28 2009 170 855 298 56 6894
Sep 29 2009 229 1235 379 90 6757
Sep 30 2009 176 525 420 38 7477
Oct 1 2009 187 222 377 20 7913
Oct 2 2009 132 132 414 17 8086
Oct 3 2009 112 117 374 18 7790
Oct 4 2009 128 658 294 42 6158
Oct 5 2009 243 1634 509 97 7657
But I tend to agree with you: We might have to face the fact that we have to
improve the SPAM filter on our end and open the list. As a first step we could
install greylisting and have a bunch of moderators to see how that goes.
@Jacob: How do you feel about that ?
@Andrew: Would you be willing to join the moderators group ?
Regards,
Marek
next prev parent reply other threads:[~2009-10-06 13:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 11:28 [B.A.T.M.A.N.] Fwd: Re: Debian extra modules Holger Levsen
2009-10-06 11:55 ` Sven Eckelmann
2009-10-06 13:27 ` Marek Lindner [this message]
2009-10-06 13:52 ` Andrew Lunn
2009-10-06 14:02 ` Andrew Lunn
2009-10-06 15:11 ` Marek Lindner
2009-10-06 17:12 ` Jacob Marble
2009-10-06 17:37 ` Sven Eckelmann
2009-10-06 18:10 ` Andrew Lunn
2009-10-07 14:56 ` Marek Lindner
2009-10-06 11:59 ` Andrew Lunn
2009-10-20 10:04 ` [B.A.T.M.A.N.] " Sven Eckelmann
2009-10-20 10:35 ` Holger Levsen
2009-10-29 13:15 ` Sven Eckelmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200910062127.42925.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--cc=b.a.t.m.a.n@lists.open-mesh.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox