Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

-owner email is a spam haven #23

Open
GoogleCodeExporter opened this issue Mar 30, 2015 · 1 comment
Open

-owner email is a spam haven #23

GoogleCodeExporter opened this issue Mar 30, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

I think we need to get rid of the -owner email. I'm getting a lot of spam to it
now. I would accept just putting it in the moderator hold. If someone wants to
get a hold of the list owner, maybe we should make a mini messaging service via
the webapp layer.

jon
------- Additional comments from Martin Marcher Wed Jul 18 17:09:13 -0700 2007 
-------

How about a digest option for the -owner?

We host a couple of Mailing lists and people are quite happy about the -owner as
they do get help requests on that address.

IMHO A workable solution would be something like:

 * pass mail from subscribed senders
 * Optional: deliver all other messages (or subject lines with link to the held
message archive) in a daily/weekly/$interval digest mode
 * Notify in $INTERVALS about how many messages are held for -owner (that option
could also be reused for a digest notification for "normal" held messages)

Original issue reported on code.google.com by lhori...@gmail.com on 4 Jun 2009 at 10:34

@GoogleCodeExporter
Copy link
Author

The new version rejects mail to the list when sent from the list-owner address, 
which might cut down the amount of spam.  There may be other obvious spam 
behaviors we can block.

Original comment by lhori...@gmail.com on 24 Jul 2010 at 6:33

  • Added labels: ****
  • Removed labels: ****

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant