Hello ! Fristly excuse me for cross-posting. Actually, I did not like to be the person who comes this up however the amount of spams which is propagated thru the lists is annoying. I wonder why the guys at Zope Inc. does not tweak the list settings so posting is only allowed by the members. I have some experience with MailMan and I know it can be done by changing the following options: AdminIface-> Privacy Options -> Sender Filters -> default_memeber_moderation AdminIface -> Privacy Options -> Sender Filters -> generic_nonmemberaction I hope if there are other open-spam zope/plone lists, their managers see my message. :-) Thanks, Mohsen,
[Mohsen Moeeni]
Fristly excuse me for cross-posting. Actually, I did not like to be the person who comes this up however the amount of spams which is propagated thru the lists is annoying. I wonder why the guys at Zope Inc. does not tweak the list settings so posting is only allowed by the members.
Perhaps just the weight of history, and/or trying to keep the barriers to participation as low as possible. Speaking as zodb-dev's list admin, I'd be happy to restrict posting to members, *if* people don't object to the idea. I spend an increasingly resented part of each day doing list-admin triage (for zodb-dev and about 6 other mailing lists). A predictable irritation is that Mailman's answer to "member?" is based on the posting's sender's email address, but many people post from more than one account. If you want the default action for non-member posts to be "hold for review", I won't do it -- I can't afford the additional time sink. "reject" is the no-manual-intervention default action, but it would place a new burden on members posting from non-member accounts (their posts would be rejected, at least until they asked the list admin to add their other posting accounts to Mailman's list of non-members to accept -- and they would need to do that on a per-list basis).
On Tue, 15 Jun 2004 20:41:16 -0400 "Tim Peters" <tim@zope.com> wrote:
[Mohsen Moeeni]
Fristly excuse me for cross-posting. Actually, I did not like to be the person who comes this up however the amount of spams which is propagated thru the lists is annoying. I wonder why the guys at Zope Inc. does not tweak the list settings so posting is only allowed by the members.
Perhaps just the weight of history, and/or trying to keep the barriers to participation as low as possible. Speaking as zodb-dev's list admin, I'd be happy to restrict posting to members, *if* people don't object to the idea. I spend an increasingly resented part of each day doing list-admin triage(for zodb-dev and about 6 other mailing lists).
A predictable irritation is that Mailman's answer to "member?" is based on the posting's sender's email address, but many people post from more than one account. If you want the default action for non-member posts to be"hold for review", I won't do it -- I can't afford the additional time sink."reject" is the no-manual-intervention default action, but it would place a new burden on members posting from non-member accounts (their posts would be rejected, at least until they asked the list admin to add their other posting accounts to Mailman's list of non-members to accept -- and they would need to do that on a per-list basis).
Another issue is posting from Gmane, which I am doing right now. Although that may look like a post from me to mailman, I dunno. -Casey
Quoting Tim Peters <tim@zope.com>:
[Mohsen Moeeni]
Fristly excuse me for cross-posting. Actually, I did not like to be the person who comes this up however the amount of spams which is propagated thru the lists is annoying. I wonder why the guys at Zope Inc. does not tweak the list settings so posting is only allowed by the members.
Perhaps just the weight of history, and/or trying to keep the barriers to participation as low as possible. Speaking as zodb-dev's list admin, I'd be happy to restrict posting to members, *if* people don't object to the idea. I spend an increasingly resented part of each day doing list-admin triage (for zodb-dev and about 6 other mailing lists).
And, just like me, some time to delete your spams. :-)
A predictable irritation is that Mailman's answer to "member?" is based on the posting's sender's email address, but many people post from more than one account.
How many people? I think just a few of them use multiple addresses to comminucate on a particular list. BTW, why should one receive an email in one account/identity and use another account/identity to reply? (When I think it only makes sense for the posts which are the first in the thread) IMHO, it's better to prohibit the spams, but if that makes some barriers for people and if this is what most members want, then certainly I can live with it. :-) Mohsen,
Hi Tim, Tim Peters wrote:
I'd be happy to restrict posting to members, *if* people don't object to the idea.
I wouldn't ever even /expect/ to be able to submit from a non-member address...
I spend an increasingly resented part of each day doing list-admin triage (for zodb-dev and about 6 other mailing lists).
(Snap!)
"reject" is the no-manual-intervention default action, but it would place a new burden on members posting from non-member accounts (their posts would be rejected, at least until they asked the list admin to add their other posting accounts to Mailman's list of non-members to accept -- and they would need to do that on a per-list basis).
...and I wouldn't expect the list admin to take special measures for me either - I'd expect to have to subscribe from two addresses and deal with the dupes if I wanted to send from two addresses. Does Mailman have a "nomail" facility that subscribers could set /themselves/ on secondary accounts? In gentler times, your concern would be wonderful - in the current climate, you'll drown if you can't automate it. Save yourself, while you can! ;-) -- Regards, PhilK Email: phil@xfr.co.uk / Voicemail & Facsimile: 07092 070518 "The lyf so short, the craft so long to learne" - Chaucer
[Philip Kilner]
... Does Mailman have a "nomail" facility that subscribers could set /themselves/ on secondary accounts?
There are different versions of Mailman (of course), but at least recent ones offer this. If you go to your personal list subscription page on the web, a checkbox to suspend delivery is the first of the listed checkbox options. That seems a reasonable workaround to me. As to why this comes up, I expect my own case is typical: I have 6 POP3 accounts with various providers. I can retrieve email from all of them when logged in with any of the providers, but SMTP access (for sending email) is often limited to the specific account I'm logged into. For example, I cannot use my Zope Corp SMTP account, or my Comcast SMTP account, when logged in to my MSN account from a dialup line in a hotel room. It doesn't matter whose "fault" that is (although I suspect it's MSN's ...), it's just the fact of the matter. I don't have dialup facilities thru Zope Corp or Comcast, so when I'm on the road and restricted to dialup access, I send mail via MSN or Hotmail, or not at all. I'm told that posting from my Hotmail account doesn't project a professional image <wink>. The same kind of thing happens on the one list I admin where non-member posts are held for review (this is the PSF Board mailing list, where non-member posts can be legitimate, e.g. a company asking about becoming a PSF sponsor). There are fewer than a dozen members on that list, and the legit traffic is usually light, so accommodating two or ten email addresses per member was a finite task there.
In gentler times, your concern would be wonderful - in the current climate, you'll drown if you can't automate it. Save yourself, while you can!
;-)
If there's spam on Zope's mailing lists, I never see it(*), so my only stake in this is in a list-admin capacity. (*) I never see it because I started this project -- and it works <wink>: http://www.spambayes.org/
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jun 15, 2004, at 8:41 PM, Tim Peters wrote:
[Mohsen Moeeni]
Fristly excuse me for cross-posting. Actually, I did not like to be the person who comes this up however the amount of spams which is propagated thru the lists is annoying. I wonder why the guys at Zope Inc. does not tweak the list settings so posting is only allowed by the members.
Perhaps just the weight of history, and/or trying to keep the barriers to participation as low as possible. Speaking as zodb-dev's list admin, I'd be happy to restrict posting to members, *if* people don't object to the idea. I spend an increasingly resented part of each day doing list-admin triage (for zodb-dev and about 6 other mailing lists).
A predictable irritation is that Mailman's answer to "member?" is based on the posting's sender's email address, but many people post from more than one account. If you want the default action for non-member posts to be "hold for review", I won't do it -- I can't afford the additional time sink. "reject" is the no-manual-intervention default action, but it would place a new burden on members posting from non-member accounts (their posts would be rejected, at least until they asked the list admin to add their other posting accounts to Mailman's list of non-members to accept -- and they would need to do that on a per-list basis).
They can just subscribe their other addresses and set them nomail in the mailman interface. Things have gotten out of hand, I don't think it's possible to run a mailing list that allows nonmember posting any more. That said, could the reject message be set to include text saying something to the effect of "spammers make it impossible to allow non-members to post to this list. Please go to ____ to sign up your address and resend your message. If you already have an address subscribed to the list, go sign this one up and set it nomail in the mailman interface" jpb - -- Joe Block <jpb@apesseekingknowledge.net> "I believe there are more instances of the abridgment of the freedom of the people by gradual and silent encroachment of those in power than by violent and sudden usurpations." - James Madison, 1798 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iD4DBQFA1OyAyEXo8W2M9hsRArFJAKCf+DExEYU+4Az5ShdVcEsa44kOIwCYoIGz RCkoCZUKRZsb/8IFBGsqsg== =88La -----END PGP SIGNATURE-----
participants (5)
-
Casey Duncan -
Joe Block -
Mohsen Moeeni -
Philip Kilner -
Tim Peters