RE: [Mailman-Users] mass subscription
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Rob Eckerson Sent: Tuesday, July 22, 2003 5:04 PM To: [EMAIL PROTECTED] Subject: [Mailman-Users] mass subscription > I want to mass subscribe people that I have on another list. > I want to just send them an email with a link to subscribe > ( cutting out the confirmation email). These people have already > opted in to receive email from me. Is the second list related by topic to the first? If not, then 'already opted in' may not cover it, unless they've given blanket permission for all your email, not just the one list. Not to say for a moment that what you're planning isn't appropriate. Some more paranoid admins, however, might look a little askance at this. -Don -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Strangenesses with URLs in the admin/listinfo pages
First, please let me apologise if this topic has been covered here before; I've just discovered this resource. I'm an amateur list/sysadmin; I've got a home web/mail server, but I'm not a pro nor do I have a pro's knowledge. I think I've got my system set up properly (Mailman 2.1.2), but there's one lingering problem. My web server is running on a non-standard port. Thus, any URL I use appends the port number to the host name (http://www.domain.tld:7080). By playing with the URL parameters in the mm_cfg.py file (copied from the Defaults.py file), I've managed to get *most* of the links on the admin and info (etc) pages to display properly. However, the link to the Archives will NOT append that info. Here's what I've got (not the real values): DEFAULT_EMAIL_HOST = 'domain.tld' DEFAULT_URL_HOST = 'www.domain.tld' DEFAULT_URL_PATTERN = 'http://%s:7080/mailman/' MAILMAN_URL = 'http://www.domain.tld:7080/' VIRTUAL_HOSTS.clear() add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) The link for the archives consistently shows as: http://www.domain.tld/pipermail/soapbox/ if I edit the DEFAULT_URL_HOST value to include the port number, the Archive link shows properly - as do most of the other links. However, the "show all lists on this server" link then truncates the port number. If I put the port number on BOTH parameters, then it's doubled for everything except the archives and "show all lists." I do run the fix_url script each time. Has anyone run into this before and/or does anyone have any suggestions? BTW, from what I saw when trying to run with 2.1, these two links have been problematic. Before I upgraded and recreated the list, these two links would default to the server 'porky.devel.redhat.com' (yes, I'm running RH9) and nothing I could do would change that. Searching via Google, I found no real info on how to change it, but quite a few sites out there having the same problem. Is this a bug, a consistency problem, or something obvious that I'm missing? -Don Levey -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
RE: [Mailman-Users] missing port number :8000 in the list overviewURL.
I just ran into a similar problem, using non-standard ports. What I was finding was that changing the formats/values affected *some* links but not others. Here's what I've got that now works (fix_url is your friend!): DEFAULT_EMAIL_HOST = 'domain.tld' DEFAULT_URL_HOST = 'www.domain.tld' DEFAULT_URL_PATTERN = 'http://%s:7080/mailman/' MAILMAN_URL = 'http://www.domain.tld:7080/' PUBLIC_ARCHIVE_URL = 'http://%(hostname)s:7080/pipermail/%(listname)s' VIRTUAL_HOSTS.clear() add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) The FAQ works, and is helpful - but the archive URL hint is a little burried for the impatient or over-confident. -Don -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Richard Barrett Sent: Thursday, July 24, 2003 5:32 AM To: Nicolas C. Cc: [EMAIL PROTECTED] Subject: Re: [Mailman-Users] missing port number :8000 in the list overviewURL. see about half way down this FAQ page for how to deal with this issue: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.029.htp On Thursday, July 24, 2003, at 09:11 AM, Nicolas C. wrote: > Hi, > > I have this in the mm_cfg.py: > DEFAULT_URL_HOST= 'my.machine.domain.com:8000' > DEFAULT_EMAIL_HOST = 'my.machine.domain.com' > add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) > > on the URL: > http://my.machine.domain.com:8000/mailman/listinfo > > The link of 'the list admin overview page'in the sentence "List > administrators, you can visit the list admin overview page to find the > management interface for your list. " > > the link is pointing towards: > http://my.machine.domain.com/mailman/admin > > why the :8000 is missing, I use mailman 2.1.2 ? > > regards, -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/don_mailman%40the-levey s.us -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Re: OSIRUSOFT
-Original Message- -- Message: 5 Date: Wed, 27 Aug 2003 13:25:42 -0500 From: Paul H Byerly <[EMAIL PROTECTED]> Subject: [Mailman-Users] Osirusoft blocking all IPs To: [EMAIL PROTECTED] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="us-ascii"; format=flowed I realize this is not a Mailman issue, but it may be causing some Mailman systems to reject all mail. If you are using relays.osirusoft.com it's rejecting all e-mail. <>< Paul, who has his mail flowing again * Osirusoft has been under a VERY heavy DDoS attack for a while now. In order to reduce traffic, Joe set things up so that legitimate users of his service would cease - all that leaves left is the terrorist attack, which can now be analysed. The underlying lists from which he drew his information are still there: SPEWS, for one, is still in operation. I personally salute Joe for his valiant effort over the past few years; making these lists available has meant that I've blocked many thousands of spam messages, with only one false-positive in the bunch. There are some who ignorantly blame Joe for problems in their own server, their ISP, or the listing criteria on the lists he used; they fail to see that we as mail server operators have the final say on who uses our resources. Lists such as the Osirusoft relay list have had a significant impact on spam; otherwise, they'd never have been hit as hard as they are, because the spammers wouldn't be afraid. Keep in mind also that it's these criteria that have given Mailman some of the features that allow it to be a good netizen - in particular, the confirmation option. No-one should ever be added to a mailing list without their knowledge and consent. It's the lists that DON'T do this that get their IPs blacklisted. The spammers and electronic terrorists perpetrating this attack have failed to foresee two things: the rise of multiple alternate lists, and the reactivation of individual blocklists. It's much easier to get off of one centrally-maintained list than it is to get off of thousands of individually-maintained lists, especially when the admins are overworked and vindictive... -Don -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] RE: OSIRUSOFT
-Original Message- -- Message: 5 Date: Wed, 27 Aug 2003 13:25:42 -0500 From: Paul H Byerly <[EMAIL PROTECTED]> Subject: [Mailman-Users] Osirusoft blocking all IPs To: [EMAIL PROTECTED] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="us-ascii"; format=flowed I realize this is not a Mailman issue, but it may be causing some Mailman systems to reject all mail. If you are using relays.osirusoft.com it's rejecting all e-mail. <>< Paul, who has his mail flowing again * Osirusoft has been under a VERY heavy DDoS attack for a while now. In order to reduce traffic, Joe set things up so that legitimate users of his service would cease - all that leaves left is the terrorist attack, which can now be analysed. The underlying lists from which he drew his information are still there: SPEWS, for one, is still in operation. I personally salute Joe for his valiant effort over the past few years; making these lists available has meant that I've blocked many thousands of spam messages, with only one false-positive in the bunch. There are some who ignorantly blame Joe for problems in their own server, their ISP, or the listing criteria on the lists he used; they fail to see that we as mail server operators have the final say on who uses our resources. Lists such as the Osirusoft relay list have had a significant impact on spam; otherwise, they'd never have been hit as hard as they are, because the spammers wouldn't be afraid. Keep in mind also that it's these criteria that have given Mailman some of the features that allow it to be a good netizen - in particular, the confirmation option. No-one should ever be added to a mailing list without their knowledge and consent. It's the lists that DON'T do this that get their IPs blacklisted. The spammers and electronic terrorists perpetrating this attack have failed to foresee two things: the rise of multiple alternate lists, and the reactivation of individual blocklists. It's much easier to get off of one centrally-maintained list than it is to get off of thousands of individually-maintained lists, especially when the admins are overworked and vindictive... -Don -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
