You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-user@db.apache.org by de...@segel.com on 2006/11/13 15:10:55 UTC
[OT] Two suggestions on list management...
Has anyone else noticed an increase in Spam?
I set up an alias derby@ <mailto:derby@%3cmydomain%3e.com> <mydomain>.com
which is now getting a ton of stock spams from 'bots.
The e-mail alias is only used for this list and I'm certain that its coming
from an archive site.
It would be nice if the e-mail addresses were munged prior to being placed
on the archive site.
Also, it would be nice to have a clear filter in the subject line to
indicate where this mail is coming from.
For example, the Dovecot mailing list will include inject a [dovecot] tag in
to the subject line. This makes it easier to filter the mail and put it
automatically in to the correct mbox. It will also make it easier to filter
against the alias. So that any mail to derby@
<mailto:derby@%3cmydomain%3e.com> <mydomain>.com that doesn't have a tag
like [derby-user] will automatically hit /dev/null.
Can this be done?
Danke!
-G
Re: [OT] Two suggestions on list management...
Posted by Michael Segel <ms...@mycingular.blackberry.net>.
Cute. Now if you said that SPAM was high in sodium, hence bad for you,
Then you'd be in hot water with hormel...
:-)
Back to being serious for a moment.
I try to set up aliases for each time I join a mailing list, or sign up for a web page.
So when I get spam to that address, I know where the leak occured.
For those who run their own domain and mail server, this is extremely easy to do.
Sine I am getty spam to my derby I'd, I know its being gleamed from this list.
Most likely when it gets put on the web as an archive. Hence the suggestion for munging the address on the archive site.
The other suggestion was to add a tag to the subject line. It should be pretty easy to do this.
Using yourself as an example,
You have one alias for all of your apache stuff. Imagine how nice it would be to be able to sort your e mail box on this tag so that you don't get your in mail boxed swamped... You just go to the folder that has your derby stuff and you can concentrate on derby...
Also if you wanted to, you could filter spam based on mail going to derby that either doesn't have the filter tag, or is on the white list of senders.
And if you want to get fancy, you couldstore this in a derby database.
Dovecot has hooks so you can use mysql. (Any db should work)
Now that would be a practicle exercise...
And if you want to take this a step further you could create virtual mailboxes for your users ...
Sent via BlackBerry.
-Mike Segel
Principal
MSCC
312 952 8175
-----Original Message-----
From: Paul J DeCoursey <pa...@decoursey.net>
Date: Mon, 13 Nov 2006 09:30:29
To:Derby Discussion <de...@db.apache.org>
Subject: Re: [OT] Two suggestions on list management...
derby@segel.com wrote:
>
> Has anyone else noticed an increase in Spam?
>
> I set up an alias derby@<mydomain>.com
> <mailto:derby@%3cmydomain%3e.com> which is now getting a ton of stock
> spams from ‘bots.
>
> The e-mail alias is only used for this list and I’m certain that its
> coming from an archive site.
>
> It would be nice if the e-mail addresses were munged prior to being
> placed on the archive site.
>
> Also, it would be nice to have a clear filter in the subject line to
> indicate where this mail is coming from.
>
> For example, the Dovecot mailing list will include inject a [dovecot]
> tag in to the subject line. This makes it easier to filter the mail
> and put it automatically in to the correct mbox. It will also make it
> easier to filter against the alias. So that any mail to
> derby@<mydomain>.com <mailto:derby@%3cmydomain%3e.com> that doesn’t
> have a tag like [derby-user] will automatically hit /dev/null.
>
> Can this be done?
>
> Danke!
>
> -G
>
Spam is an essential part of internet life, why are you trying to stop
it? It'd be like going to the pool for a swim and finding the pool only
filled to 10%. But seriously I have also noticed an influx on spam, but
I was unable to attribute it to any one list, I have the same address
for all my Apache project mailing lists, and it's on that address that I
get a lot of spam.
pd
Re: [OT] Two suggestions on list management...
Posted by Paul J DeCoursey <pa...@decoursey.net>.
derby@segel.com wrote:
>
> Has anyone else noticed an increase in Spam?
>
> I set up an alias derby@<mydomain>.com
> <mailto:derby@%3cmydomain%3e.com> which is now getting a ton of stock
> spams from ‘bots.
>
> The e-mail alias is only used for this list and I’m certain that its
> coming from an archive site.
>
> It would be nice if the e-mail addresses were munged prior to being
> placed on the archive site.
>
> Also, it would be nice to have a clear filter in the subject line to
> indicate where this mail is coming from.
>
> For example, the Dovecot mailing list will include inject a [dovecot]
> tag in to the subject line. This makes it easier to filter the mail
> and put it automatically in to the correct mbox. It will also make it
> easier to filter against the alias. So that any mail to
> derby@<mydomain>.com <mailto:derby@%3cmydomain%3e.com> that doesn’t
> have a tag like [derby-user] will automatically hit /dev/null.
>
> Can this be done?
>
> Danke!
>
> -G
>
Spam is an essential part of internet life, why are you trying to stop
it? It'd be like going to the pool for a swim and finding the pool only
filled to 10%. But seriously I have also noticed an influx on spam, but
I was unable to attribute it to any one list, I have the same address
for all my Apache project mailing lists, and it's on that address that I
get a lot of spam.
pd
Re: [OT] Two suggestions on list management...
Posted by "Bernt M. Johnsen" <Be...@Sun.COM>.
>>>>>>>>>>>> Bernt M. Johnsen wrote (2006-11-13 23:12:04):
> > The rest of this mail should be directed to infrastructure@apache.org
>
> [FYI] Since only comitters are allowed to mail on
> infrastructure@apache.org, I forwarded your mail there.
Reply from infrastructure:
> >For example, the Dovecot mailing list will include inject a [dovecot] tag
> >in
> >to the subject line. This makes it easier to filter the mail and put it
> >automatically in to the correct mbox. It will also make it easier to filter
> >against the alias. So that any mail to derby@
> ><mailto:derby@%3cmydomain%3e.com> <mydomain>.com that doesn't have a tag
> >like [derby-user] will automatically hit /dev/null.
>
> Ezlm mails already have various list-specific headers, namely List-Id,
> List-Post and others, which can be used for filtering. I use them to
> sort out my daily mail, and it's quite useful also for dealing with
> mails CC'd to several lists.
So, you have information suitable for filtering.
--
Bernt Marius Johnsen, Database Technology Group,
Staff Engineer, Technical Lead Derby/Java DB
Sun Microsystems, Trondheim, Norway
Re: [OT] Two suggestions on list management...
Posted by "Bernt M. Johnsen" <Be...@Sun.COM>.
> The rest of this mail should be directed to infrastructure@apache.org
[FYI] Since only comitters are allowed to mail on
infrastructure@apache.org, I forwarded your mail there.
--
Bernt Marius Johnsen, Database Technology Group,
Staff Engineer, Technical Lead Derby/Java DB
Sun Microsystems, Trondheim, Norway
Re: [OT] Two suggestions on list management...
Posted by "Bernt M. Johnsen" <Be...@Sun.COM>.
>>>>>>>>>>>> derby@segel.com wrote (2006-11-13 08:10:55):
> Has anyone else noticed an increase in Spam?
Yes. I'm running a server with several mailing lists (completely
unrelated to any Apache project whatsoever), and have had a notiecable
increase in spam attacks on list-adresses lately. I solved the problem
by greylisting (had spamassasin and spamcop+spahaus blacklisting
previously).
The rest of this mail should be directed to infrastructure@apache.org
> I set up an alias derby@ <mailto:derby@%3cmydomain%3e.com> <mydomain>.com
> which is now getting a ton of stock spams from 'bots.
>
>
>
> The e-mail alias is only used for this list and I'm certain that its coming
> from an archive site.
>
>
>
> It would be nice if the e-mail addresses were munged prior to being placed
> on the archive site.
>
>
>
> Also, it would be nice to have a clear filter in the subject line to
> indicate where this mail is coming from.
>
>
>
> For example, the Dovecot mailing list will include inject a [dovecot] tag in
> to the subject line. This makes it easier to filter the mail and put it
> automatically in to the correct mbox. It will also make it easier to filter
> against the alias. So that any mail to derby@
> <mailto:derby@%3cmydomain%3e.com> <mydomain>.com that doesn't have a tag
> like [derby-user] will automatically hit /dev/null.
>
>
>
> Can this be done?
>
>
>
> Danke!
>
>
>
> -G
>
--
Bernt Marius Johnsen, Database Technology Group,
Staff Engineer, Technical Lead Derby/Java DB
Sun Microsystems, Trondheim, Norway