Re: [Mailman-Users] Mailman-Users Digest, Vol 191, Issue 3
Thanks again, Mark!
My responses below.
> On 1/4/20 5:47 PM, Allan Hansen wrote:
>>
>> a. The server was set up with the wrong domain name (our fault), so I had to
>> add the ‘correct’ one. I had seen the command ‘Add Domain’ in
>> the UI and thought that would do it, but Brian kindly sent me a list of
>> additional instructions, which we then implemented. That made it possible to
>> create a list in the new domain, subscribe people and post messages.
>> However, messages are not archived. What extra step is needed to enable
>> archiving?
>
>
> What are the setytings in Postorius -> Settings -> Archiving?
Archive policy: Private archives
Archive archivers: hyperkitty, prototype
>
>
>> b. When go to the server using the new domain (both before and after logging
>> in), I see not just the lists I created in the new domain, but the lists
>> created in the old domain. These lists of lists are domain specific and
>> should not be listed together. That’s just IMHO, but not serious, as I will
>> soon get rid of anything in the old domain. So feel free to ignore this one
>> if this is intended, which I could see might be the case.
>
>
> Set
>
> FILTER_VHOST = True
>
> in settings_local.py
>
Yes, Brian told me to do the same. This is the what I wrote back:
hansen@rccrmail:/opt/mailman/mm$ sudo vi settings.py
Edited the setting to:
# Only display mailing-lists from the same virtual host as the webserver
FILTER_VHOST = True
Then Brian told me to restart qcluster:
hansen@rccrmail:/opt/mailman/mm$ sudo systemctl restart qcluster
I then logged in, but the same lists are showing. It either takes the system a
long time to reset or it has ignored the
setting.
Just tried it again, and the lists are all showing. Do I need to manually
recompile the file?
>
>> c. I then moved on to the templates and added a template for the message
>> text to send to new subscribers. That resulted in the following error
>> message when I went in as moderator to approve of a new subscription:
>>
>> Something went wrong
>> Mailman REST API not available. Please start Mailman core.
>
>
> Postorius is unable to access core's REST API. Is Mailman running?
Well, I was able to post to the lists, so I assume it is. Listing at processes,
I see a bunch of postgres, python3, nginx, django-adminp but
nothing explicitly with a ‘mailman’ string.
> If so, what's in /opt/mailman/mm/var/logs/mailmansuite.log or whatever it's
> called - defined as `filename` in the `file` handler in the LOGGING
> definition in settings(_local).py.
hansen@rccrmail:/opt/mailman/mm/logs$ tail -f mailmansuite.log
return Site.objects.get_current(request)
File
"/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py",
line 60, in get_current
return self._get_site_by_request(request)
File
"/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py",
line 45, in _get_site_by_request
SITE_CACHE[domain] = self.get(domain__iexact=domain)
File
"/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/manager.py",
line 82, in manager_method
return getattr(self.get_queryset(), name)(*args, **kwargs)
File
"/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/query.py",
line 408, in get
self.model._meta.object_name
django.contrib.sites.models.Site.DoesNotExist: Site matching query does not
exist.
[ABH] At this point I click to accept a subsription request:
ERROR 2020-01-06 07:32:41,439 699 postorius.middleware Mailman REST API not
available
Traceback (most recent call last):
File
"/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py",
line 672, in urlopen
chunked=chunked,
File
"/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py",
line 421, in _make_request
six.raise_from(e, None)
File "", line 3, in raise_from
File
"/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py",
line 416, in _make_request
httplib_response = conn.getresponse()
File "/usr/lib/python3.7/http/client.py", line 1321, in getresponse
response.begin()
File "/usr/lib/python3.7/http/client.py", line 296, in begin
version, status, reason = self._read_status()
File "/usr/lib/python3.7/http/client.py", line 265, in _read_status
raise RemoteDisconnected("Remote end closed connection without"
http.client.RemoteDisconnected: Remote end closed connection without response
So yes, the REST API is not there. How can I get it going?
Before we added the new domain, I was able to accept subscription requests to
the previous domain’s lists. No more.
Yours,
Allan
>
[Mailman-Users] MM3 startup issues
After having MM3 installed, I’m trying to get it setup up correctly for my lists. I have a couple of issues at this point: a. The server was set up with the wrong domain name (our fault), so I had to add the ‘correct’ one. I had seen the command ‘Add Domain’ in the UI and thought that would do it, but Brian kindly sent me a list of additional instructions, which we then implemented. That made it possible to create a list in the new domain, subscribe people and post messages. However, messages are not archived. What extra step is needed to enable archiving? The instructions we received were these: How to setup an additional domain to the Mailman 3 server: • Add the additional domain name to Django Sites and Mail domains via the Django admin panel. This will require superuser access. • Make sure the list admin(s) of any list is registered with Django. • Setup the new list domain in nginx (/etc/nginx/conf.d). You can copy and paste the existing record there to the new record. Just make sure you modify the server_name directive in the record to the new domain name. The record file name should be newdomainname.com.conf. This will need to be done via shell with sudo privileges. • Test nginx configuratin (nginx -t) • Reload nginx (nginx -s reload) • Generate LetsEncrypt Cert (certbot --nginx -d newdomainname.com) Before doing this make sure the appropriate DNS records are setup pointing the new list domain to your Mailman 3 server otherwise this part will fail. • Add the new list domain to /opt/mailman/mm/settings_local.py in the ALLOWED_HOSTS section. • Add list domain to Postorius. • Create the list in Postorius using the new list domain. b. When go to the server using the new domain (both before and after logging in), I see not just the lists I created in the new domain, but the lists created in the old domain. These lists of lists are domain specific and should not be listed together. That’s just IMHO, but not serious, as I will soon get rid of anything in the old domain. So feel free to ignore this one if this is intended, which I could see might be the case. c. I then moved on to the templates and added a template for the message text to send to new subscribers. That resulted in the following error message when I went in as moderator to approve of a new subscription: Something went wrong Mailman REST API not available. Please start Mailman core. Oh, and Happy New Year to all, Allan Hansen -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Mailman 3.0 Documentation
All, I have spent some time now trying to understand the list admin interface to Mailman 3.0. There is no context-sensitive help and looking around at the Mailman sites, I mostly find instructions on how to install Mailman 3.0, but no documentation on using it (other than for end users - which is much improved over MM2). I also looked in the FAQ. Is there such docs and, if so, where can I find them. It’s about terminology and how to mangle the headers, etc. Oh, and a big thanks to Brian Carpenter of EMWD for his help installing MM3, as I ran into a wall in my own attempt. MM3 appears to be a big end-user improvement over MM2. Thanks also, developers, for the work on MM3 development. I can see that it was a mountain of work to get that done. Yours, Allan -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Avoiding mangling in Mailman 3?
On Dec 10, 2019, at 10:27 , Stephen J. Turnbull wrote: > > Allan Hansen writes: > >> But Apple Mail puts the mangled address To: into the ‘Previous >> Recipients’ list to help with auto-completion later. > > I assume by "To" you mean "From”. [ABH] Yes, sorry. It takes the “From:” address and saves that, instead of the “ReplyTo:” address that is the new “To:” address. > > I don't see how we can do anything reliable about that. From is a > *required* field in RFC 5322 message syntax, and it *must* contain a > mailbox (perhaps along with a display name). Some possibilities > follow. [ABH] The “From:” should contain the author address, but if we want to keep our Yahoo/AOL subscribers… > We could put an "oopsie, did you mean to send to us" address at the > Mailman host in there that replies with explanation from Mailman, but > when you don't have the list in Reply-To, people who *intend* a reply > to list will have to copy/paste by hand (as mentioned earlier a link > in the footer will not have the features of a client-composed reply). > That might be OK for you, since you seem to really discourage replies > to list. [ABH] That’s not a bad idea, Stephen. I could try that. And yes, we are very protective of our lists, so “Reply-To:” is the author address. When I get Mailman 3 set up, I’ll put in an ‘oopsie’ address with an auto-responder. I’ll assume that Mailman 3 will be able to detect auto-responder infinite loops. :-) > > Another try would be a Rule that checks for the "via list-at-this- > server" formulation and automatically bounces the mail back > (regardless of any "don't at me" settings), with an explanation of why > the mail bounced and a suggestion to clean up Previous Recipients. > You could simulate this with the existing spam hold feature, but I'm > not sure that can be set to reject on a per recipe basis, and I don't > think it would allow for the explanation to differ across rejections. > > Of course that will fail if the user changes the display name. What > is your experience? Do these users just accept the display name with > "via list" attached, or do they tend to fix it while failing to notice > the unintended address? [ABH] The disasters all have had the full mangled display name, so no editing took place in those cases. I think the first suggestion above is better. > >> I do tell people to clean up their ‘Previous Recipients’ list, they >> eventually forget and this happens again. > > You're a hero! But this sucks for you. The point of an advanced list > manager is that you shouldn't have to do this kind of mechanical work. [ABH] I’m trying to get out of it, as you can see. :-) I very much appreciate your suggestions and help, and will let you and the list know how the autoresponder works out. I’m a bit red in the face that I did not think of that, but what are friends for! Yours Allan -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Avoiding mangling in Mailman 3?
Hi Stephen, Thank you a bunch for looking into this. I was trying to say that ReplyTo: works fine, for just the reasons you mention. No problem there. At first. ;-) But Apple Mail puts the mangled address To: into the ‘Previous Recipients’ list to help with auto-completion later. Here are the steps. I’m avoiding real addresses, as my mail client further mangled them with the auto-inserted ‘mailto:’ command confusing my message. Here goes: a. Subscriber receives message from the list. The From: is a mangled From: as recommended, and the ReplyTo: is the author’s emal address: From: Author Name (author.address) via list ReplyTo: author.address b. Subscriber replies to author. Sees correct To: address (the author.address) from the ReplyTo: header. So far all is apparently OK. However, to be ‘helpful’ with auto-completion later, Apple puts the mangled string “Author Name (author.address) via list ” into the mail client’s ‘Previous Recipients’ list!! To: author.address c. Subscriber much later tries to send a private message to the author and starts typing "Autho...". Apple at this point retrieves the mangled string from the ‘Previous Recipents’ list, but in their infinite wisdom, they hide the actual address, which is the list address. The subscriber does not suspect that things have gone awry because it looks fine. Well, not completely fine, but enough so. So he/she hits ’Send’ while seeing this and only this in their To: field: To: Author Name (author.address) via list d. People on the list receive a private message that was intended for the original author. Result: red faces all around and possibly private data exposed to the entire list. I just now happened to receive such a message from one of my lists! No real disaster this time, luckily, but confusing for the lists members. I do tell people to clean up their ‘Previous Recipients’ list, they eventually forget and this happens again. If this can’t be solved somehow, I will have to unsub all my AOL and YAHOO subscribers (a lot), as it’s too dangerous to have the mangling causing these privacy mishaps. They don’t really have to change their main email, just get another one that they use only for the lists. By the way, I have asked Brian to help with installing Mailman 3 and look forward to working with him and with the new system. Yours, Allan -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Avoiding mangling in Mailman 3?
Stephen et al., You’re right that using links instead of a Reply function is unattractive and not how email is supposed to work. On the other hand, the same surely goes for the To: mangling: I have set the ReplyTo: as the author, it’s not the immediate replying as such that is an issue, and the mangled string is factually correct. The issue comes when Apple Mail does auto-completion and hides the email address. A mangled From: address like this: "Allan Hansen (han...@rc.org <mailto:han...@rc.org>) via list" mailto:r...@mail.rc.org>> will show up as ‘Allan Hansen (han...@rc.org <mailto:han...@rc.org>) via list’ in Apple Mail with the address hidden by the mail client. Anyone sending to that string will assume that it goes to me. It does not. It goes to the list. So putting “Allan Hansen (hansen AT rc.org <http://rc.org/>)" in the description will not help this issue. Using it with auto-completion will still send it to the hidden list address. You’re right that if the author is sending HTML mail, adding a hyperlink to it is not likely to be successful at all. So maybe that’s not a good solution. On the other hand, if this is the case, it appears that the automatically inserted message footer added by Mailman is working fine (see next). Would anything prevent adding to this section? Can it be a REPLY button? -- Allan's mailing list al...@mail.rc.org <mailto:al...@mail.rc.org> <http://mail.rc.org/mailman/listinfo/allan <http://mail.rc.org/mailman/listinfo/allan>> I did the code change for the mangling long ago, on advice from this list. It worked for a while, until the auto-completion issue and hiding of the actual email addresses messed it up. I’d rather not have the same problems in Mailman 3, so I’m looking for something, anything - even if it’s not nice, that does not cause my subscribers to be confused or to send private messages to 1000 people without knowing it. Yours, Allan > On Dec 7, 2019, at 6:21 , Stephen J. Turnbull > wrote: > > Allan Hansen writes: > >> 1. Replace the From: address with a no-reply address on the list >> server. Don’t add the sender’s address in quotes. > > I believe this requires a change in the Mailman code. > > I guess you want the author's display name, if available, there? What > if there is no display name, or it doesn't identify the author? I > guess the best play would be the mailbox of the author. > > I guess some nontechnical users > might just copy that to an address field with less than amusing > results, but it might be useful in manual lookups in address books, > since most clients do not display Reply-To. > >> 2. Keep the ‘Reply-To:’ address as the sender’s address (that’s >> what I have it set to now - I don’t want people to reply to the >> lists). > > I believe this doesn't need a change to Mailman. > >> 3. Put HTML mailto: links for ‘Reply to Sender’ and Reply to List’ >> at the bottom of the message. > > A mailto link for the list is configurable. However, the link for > author would require changes to Mailman code I'm pretty sure. Also, > as explained below, it's probably very unreliable and unattractive to > try to use links to simulate a mail client's reply function. > > First of all, users expect a reply function to copy the text of the > original. mailto URLs don't provide a facility for that. We would > have to add code to copy the text to the URL. I'm not sure how > typical clients would react to that, and if the original is plain > text, the message's whole text would be visibly duplicated in the > footer of the message distributed to subscribers, which would likely > be displayed as is by most clients. This would be pretty distressing > to most subscribers, I think. Also, I expect most clients use the DOM > they have constructed to display the original mail to populate replies > they construct themselves, but Mailman can't know about that. Users > may not be pleased with replies constructed from a mailto URL; in > particular, it would not be displayed or transmitted as copied, but > rather as original text. > > Second, users expect replies to preserve threading. This would mean > adding References or at least In-Reply-To header fields to the mailto > URLs. This would be straightforward to implement, but would result in > large, unreadable plaintext footers, if some users are sending > plaintext mail. (Though it wouldn't be as bad as if you tried to > include the original text in the reply's composition window, I imagine > you'd get complaints.) Again, I'm not sure how typical clients would > deal with it, whether they would follow the RFCs or screw
[Mailman-Users] Avoiding mangling in Mailman 3?
All, One of my main gripes is the From: mangling that we had to use to allow AOL and Yahoo subscribers to send messages without messing everyone else up. I have now been informed that Mailman 3 does not solve this problem, but I’d like to move to Mailman 3 anyway. So what to do? How about this: 1. Replace the From: address with a no-reply address on the list server. Don’t add the sender’s address in quotes. 2. Keep the ‘Reply-To:’ address as the sender’s address (that’s what I have it set to now - I don’t want people to reply to the lists). 3. Put HTML mailto: links for ‘Reply to Sender’ and Reply to List’ at the bottom of the message. My other solution: Require subscribers from AOL/Yahoo and whichever other service with the same misguided policy to get another email address for the lists. Is there anyone on this who will be willing to help installing Mailman 3 for me on a Linux system. I have tried and I have had two experts try as well, but we have all run into difficulty. I’ll pay, of course. Yours, Allan Hansen -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mailman 3 Ready?
Hi all, Thank you for your responses, Stephen. Much appreciated. I have forwarded them to my friend. I don’t know if he is on this list, but I have recommended that he be, so we can get over whatever hump is getting in the way. I used the instructions on the Mailman 3 site on my own attempt. The fact that the mangling will continue is a disappointment. I’m inclined to tell all my AOL and Yahoo users and others in the same boat to find another email service. The problem is that my MacOS users are getting tripped up by the mangling, as it is hidden by the mail clients. I have instructed them to remove previous recipients regularly from the list of such, if they contain the ‘via list’ string. But they don’t read my emails, and we see many embarrassing email ssent to the lists that are meant for one-on-one communication. What is the best, easiest, guaranteed-to-work way to get this Mailman 3 up and running (OS, add-ons, options, etc.). When I tried myself, I saw a lot of options that I really did not really care to have because I did not know the consequences of each. I’m an application programmer, not a systems programmer. Yours, Allan Hansen allan_han...@icloud.com > On Nov 24, 2019, at 22:15 , Stephen J. Turnbull > wrote: > >> >> I’m ready and eager to move on to MM3 on a Linux box. > > The obvious "turn-key" installation is to use the Docker containers, > which Abhilash keeps fairly up-to-date. But see comment below about > universal working solutions. > > Which distro do you have? Are you using the distro's packages of > Mailman 3 (not yet a good idea, unfortunately), or installing from > source? > >> I have looked into it a few times now and I keep running into the >> same blocks. I don't see much moving either. I was hoping someone >> (Mailman developing community) would come up with a better working >> solution. > > It's email. There are no universal working solutions. > >> [Some third party wrote:] My concern is that the Mailman3 is not >> ready. There are too many dead ends and undocumented stuff. > > Who is this guy and has he consulted us? I'd like to do an archive > search if he's done so to see what the issues are. > >> For Mailman2 I have a working integration with iRedMail, that does >> not seem to work with 3. > > What's iRedMail? How does it fit into the community your lists serve? -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Mailman 3 Ready?
Dear all happy campers, I need to upgrade from Mailman 2.1 - my hardware needs upgrading (badly) and the address mangling is having my subscribers rip their hair out. I need to get this done before they start on my already thinning hair! I’m ready and eager to move on to MM3 on a Linux box. First I tried to install it myself. After all, I had installed MM2 and it worked fine until AOL and Yahoo messed it up, My computer (an iMac) presents with a black screen on startup and is apt to die at any moment. I ran into trouble some 4/5 through the installation - I simply got lost in jingo. I then hired a pro, but he had real-life issues that kept him distracted and he also had trouble with the installation. I switched to a second pro, a friend, who has tried valiantly for a few months (on and off) but has basically given up now. This is his latest comment on his efforts after I (gently) nagged him: * Hi Allan, I have looked into it a few times now and I keep running into the same blocks. I don't see much moving either. I was hoping someone (Mailman developing community) would come up with a better working solution. My concern is that the Mailman3 is not ready. There are too many dead ends and undocumented stuff. For Mailman2 I have a working integration with iRedMail, that does not seem to work with 3. So far I don't have anyone who knows how to make Mailman3 work integrated with iRedMail (or similar). Things I have tried and documented are not a conclusive working installation. ** So, is MM3 ready for the big screen? If so, is there some way/how/where/when that my friend can get help helping me with the installation other than the published installation docs, which did not work for us? I have looked for both free and commercial alternatives to MM, but, frankly, I don’t think that there is anything that comes close to what we have. One of my lists started out on LISTSERV many decades ago. I moved it to Appls’s list server and then I moved it to MM after Apple starting with OS/X. Apparently LISTSERV is still around and is being updated, but I’m not keen on going back there, and it’s very expensive too boot. Any help with this is greatly appreciated! Yours, Allan Hansen -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] DMARC hack
Hi Stephen,
You’re right. AOL does not accept these messages with ‘invalid’ at the end.
You’re recommending this:
name, addr = parseadder(msg.get('from'))
if addr.endswith('aol.com') or addr.endswith('yahoo.com'):
# I forget what happens if it's a bare address
name = %s (%s) via list % (name if name else Anonymous, addr)
addr = list-post address
del msg['from’]
msg['from'] = formataddr((name, addrs))
Can I copy this code directly into the file?
Is list-post address valid syntax? (I have 40+ lists)
Yours,
Allan
On May 24, 2015, at 6:10 , Stephen J. Turnbull step...@xemacs.org wrote:
Allan Hansen writes:
69,74d68
# Added to deal with DMARC issuej
name, addrs = parseaddr(msg.get('from'))
addrs += '.invalid'
This is known to be a bad idea, as it increases the spam score at many
sites (because the author's mail domain doesn't resolve). Subscribers
at such sites may have trouble receiving mail, and your list(s) may be
tagged as suspicious.
I would recommend the From-munging approach:
name, addr = parseadder(msg.get('from'))
if addr.endswith('aol.com') or addr.endswith('yahoo.com'):
# I forget what happens if it's a bare address
name = %s (%s) via list % (name if name else Anonymous, addr)
addr = list-post address
del msg['from']
msg['from'] = formataddr((name, addr))
Mark (or you) probably have better code, and in some cases you may
want to add the addr to the Reply-To field.
del msg['from']
msg['from'] = formataddr((name, addrs))
\ No newline at end of file
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] DMARC hack
Hi Stephen, Yes, there is a good reason. I’m using Mailman as it came with the OS X Server and am not prepared to replace it. Also, Mailman no longer comes pre-installed on the Apple platform, so I’m basically stuck. This is why I tried the simplest hack I could find. I have 44 busy lists and I’m weary of messing anything up, as I have basically no time or background to fix it. Yours, Allan On May 24, 2015, at 11:06 , Andrew Hodgson and...@hodgsonfamily.org wrote: Allan Hansen wrote: Stephen, Much appreciated. Checking for aol.com and yahoo.com here alone will not work. I have a bunch of other subscribers that have accounts with providers that are owned by Yahoo (mostly) and AOL, but whose addresses are not of this form. I would have to do this for all addresses, to be safe. Probably a good reason why you can't do this, but is there any way you can upgrade to the latest 2.1.20? It means the code for doing this is already there for you and will work by looking up the relevant domain's DMARC policy in DNS. I use it on all the lists here by default now by munging the From: header and it works when it needs to. Thanks. Andrew. -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] DMARC hack
I wonder why then I got a bunch of issues with btopenworld.com, which
apparently is Yahoo based.
I just checked btopenworld.com with the ‘host’ command and as you say, it has
no ‘reject’:
$ host -t TXT _dmarc.btopenworld.com
_dmarc.btopenworld.com descriptive text v=DMARC1\; p=none\; fo=1\;
rua=mailto:dmarc...@btinternet.com, mailto:dmarc_...@auth.returnpath.net\;;
$ host -t TXT _dmarc.yahoo.com
_dmarc.yahoo.com descriptive text v=DMARC1\; p=reject\; sp=none\; pct=100\;
rua=mailto:dmarc-yahoo-...@yahoo-inc.com, mailto:dmarc_y_...@yahoo.com\;”
Here is the reject notice:
Final-Recipient: rfc822; subscri...@aol.com
Original-Recipient: rfc822;subscri...@aol.com
Action: failed
Status: 5.2.1
Remote-MTA: dns; mailin-04.mx.aol.com
Diagnostic-Code: smtp; 521 5.2.1 : AOL will not accept delivery of this
message.
Date: May 13, 2015 at 07:52:17 PDT
From: sen...@btopenworld.com
To: list address
Subject: subject
Reply-To: sen...@btopenworld.com
And yes, as I just wrote, I have good reasons for keeping this as simple as I
possibly can. Upgrading is not simple, I suspect, though I’d love to move to
3.0, as I have a lot of lists, with subscribers on many lists simulteneously.
Yours,
Allan
On May 24, 2015, at 11:14 , Stephen J. Turnbull step...@xemacs.org wrote:
Allan Hansen writes:
Checking for aol.com and yahoo.com here alone will not work. I have
a bunch of other subscribers that have accounts with providers
that are owned by Yahoo (mostly) and AOL, but whose addresses are
not of this form.
Oddly enough, it turns out that they only use DMARC p=reject at their
principal domain (aol.com and yahoo.com). You can check for any given
domain by prepending _dmarc. and checking the TXT record. For
example, for aol.com it would be host -t TXT _dmarc.aol.com if you
have the host utility for doing DNS lookups.
I would have to do this for all addresses, to be safe.
If you're worried about safety and care about conforming to standards,
you really should upgrade to at least Mailman 2.1.18-1. That allows
you to be nonconformant only for authors whose addresses are in
troublesome domains, and handles the reply-to issue as well as
possible (making everybody happy isn't quite possible). I'm sure you
have good reason for not doing so *right* *now*, but keep it in mind.
If I do this and add the bit about the Reply-To, what would the
code look like?
If you do it for all mail, you just delete the if line and shift
everything left one dedent.
name, addr = parseaddr(msg.get('from'))
name = %s (%s) via list % (name if name else Anonymous, addr)
fromaddr = mlist.GetListEmail()
del msg['from']
msg['from'] = formataddr((name, addr))
# reply-to handling goes here
I'm not comfortable trying to say what to do about reply-to, because
it's quite complicated depending on how you want to handle each of a
large number of variations: what to do with a preexisting Reply-To and
whether to put the list and/or the from address there. See the
Mailman/Handlers/CookHeaders.py file in the Mailman distribution.
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] DMARC hack
Hi,
I have waited almost a year for AOL and Yahoo to admit that they messed up and
to remove their DMARC policy. My AOL and Yahoo subscribers are pretty upset at
me because I won’t let them post. A number now have two subscriptions, one for
posting (from GMail) and another for receiving the messages.
So against my better judgement, I included this hack in Cleanse.py;
22c22
from email.Utils import formataddr, parseaddr
—
from email.Utils import formataddr
69,74d68
# Added to deal with DMARC issuej
name, addrs = parseaddr(msg.get('from'))
addrs += '.invalid'
del msg['from']
msg['from'] = formataddr((name, addrs))
\ No newline at end of file
I found it in the discussion list.
I don’t get compile errors, but Cleanse.pyc is not being updated. I have
stopped and restarted Mailman and I have also rebooted, but same non-action. I
have not tried ‘compileall’ and am not eager to, either (permissions, where to
invoke, etc). Any suggestions?
The host OS is Mac OS X Server 10.5.8 with Mailman 2.1.14
Yours,
Allan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] DMARC hack
Never mind - it started working. I just had to leave the house and come back.
Mayby the issues at work can be done that way, too. :-)
Allan
Hi,
I have waited almost a year for AOL and Yahoo to admit that they messed up and
to remove their DMARC policy. My AOL and Yahoo subscribers are pretty upset at
me because I won’t let them post. A number now have two subscriptions, one for
posting (from GMail) and another for receiving the messages.
So against my better judgement, I included this hack in Cleanse.py;
22c22
from email.Utils import formataddr, parseaddr
—
from email.Utils import formataddr
69,74d68
# Added to deal with DMARC issuej
name, addrs = parseaddr(msg.get('from'))
addrs += '.invalid'
del msg['from']
msg['from'] = formataddr((name, addrs))
\ No newline at end of file
I found it in the discussion list.
I don’t get compile errors, but Cleanse.pyc is not being updated. I have
stopped and restarted Mailman and I have also rebooted, but same non-action. I
have not tried ‘compileall’ and am not eager to, either (permissions, where to
invoke, etc). Any suggestions?
The host OS is Mac OS X Server 10.5.8 with Mailman 2.1.14
Yours,
Allan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Digest option for Yahoo and AOL subscribers?
I just realized that setting the digest option could be a temporary solution for my Yahoo and AOL subscribers until things get sorted (hopefully by Yahoo and AOL stopping this nonsense). My Mailman installation comes with the system (Mac OS X). Maiman is 2.1.14 and the OS is 10.5.8. I have no plans to upgrade either any time soon. The idea of using the list address as the From: address is not good. It hides the sender and it messes up the archives. Yours, Allan Hansen Westminster, CA -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Digest option for Yahoo and AOL subscribers?
Well, never mind. I would have to do this for all users, not just these. A pain this is. Sorry. Allan I just realized that setting the digest option could be a temporary solution for my Yahoo and AOL subscribers until things get sorted (hopefully by Yahoo and AOL stopping this nonsense). My Mailman installation comes with the system (Mac OS X). Maiman is 2.1.14 and the OS is 10.5.8. I have no plans to upgrade either any time soon. The idea of using the list address as the From: address is not good. It hides the sender and it messes up the archives. Yours, Allan Hansen Westminster, CA -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Missing password reminders
I increased the logging level of the SMTP service and requested reminders for a couple of people that complained that they didn't get them. The logs shows that the messages are sent. I ask them then to let me know if they receive these messages. I guess that if they don't, they need to complain to their respective service providers. If they do, I'll see what happens next month when the big batch is sent out. Thank you for your (apparently) tireless presence, Allan At 8:43 AM -0800 1/12/11, Mark Sapiro wrote: Allan Hansen wrote: I run Mailman 2.1.13 under Mac OS X Server 10.5.8. The mail delivery works fine (so far), but some of my subscribers insist that they are not getting the password reminders. One uses Google Mail, another Earthlink, so it's not provider specific. They assure me that the password reminder is not in their spam folder. The lists have password reminders turned on and the users have password reminders turned on. For the users that complain, I don't have bounces resulting from the reminders. Other users of the same lists get password reminders just fine. Just a couple of remarks in addition to Larry Stone's advice. Password reminders are sent from the site (mailman) list. In Mailman 2.1.13, bounces of messages from the site list are sent to the owner(s) of the site list and not processed automatically. If the site list owner is not a deliverable address whose mail you receive, you won't see any password reminder bounces. Some ISPs may filter or even discard password reminders. They can be seen as spam because of the very large number of similar messages being sent at one time. Services like Vipul's Razor http://razor.sourceforge.net/ and Pyzor http://sourceforge.net/apps/trac/pyzor/ will generally flag password reminders. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Allan Hansen P.O Box 2423 Cypress, CA 90630 U.S.A. han...@rc.org +1-714-875-8870 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Missing password reminders
Hi all, I run Mailman 2.1.13 under Mac OS X Server 10.5.8. The mail delivery works fine (so far), but some of my subscribers insist that they are not getting the password reminders. One uses Google Mail, another Earthlink, so it's not provider specific. They assure me that the password reminder is not in their spam folder. The lists have password reminders turned on and the users have password reminders turned on. For the users that complain, I don't have bounces resulting from the reminders. Other users of the same lists get password reminders just fine. I looked through the archives and did not find anything indicating that I'm not the only one with this problem. Thus my message here. Thanks, Allan -- Allan Hansen P.O Box 2423 Cypress, CA 90630 U.S.A. han...@rc.org +1-714-875-8870 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] confirmation messages are rejected
Hi all, Several users have now complained to me that their address change confirmation messsages get rejected as follows (an example): -- Forwarded message -- From: mailto:women-boun...@mail.rc.orgwomen-boun...@mail.rc.org Date: 2009/6/7 Subject: The results of your email commands To: mailto:yvo...@gmail.comuser_n...@gmail.com The results of your email command are provided below. Attached is your original message. - Results: Ignoring non-text/plain MIME parts Invalid confirmation string. Note that confirmation strings expire approximately 3 days after the initial subscription request. If your confirmation has expired, please try to re-submit your original request or message. - Unprocessed: confirm ffc239cae5b91c5b2f50ec283ab33f0e1550544d - Done. -- Forwarded message -- From: User Name mailto:yvo...@gmail.comuser_n...@gmail.com To: mailto:women-requ...@mail.rc.orgwomen-requ...@mail.rc.org Date: Sun, 7 Jun 2009 21:38:58 +0200 Subject: confirm ffc239cae5b91c5b2f50ec283ab33f0e1550544d confirm ffc239cae5b91c5b2f50ec283ab33f 0e1550544d I searched the wiki for similar complaints, but did not find one, sorry. Mailman 2.1.9 (MacOS 10.5.6). Thanks, Allan -- Allan Hansen P.O Box 2423 Cypress, CA 90630 U.S.A. han...@rc.org +1-714-875-8870 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] confirmation messages are rejected
Thank you, Mark. You are a priceless resource for this community. Yes, the confirmation was submitted on the same day it was created. No, the address change had not happened when the user got the message. I also checked the system date on the server and it is correct. Allan At 5:33 PM -0700 6/7/09, Mark Sapiro wrote: Allan Hansen wrote: Several users have now complained to me that their address change confirmation messsages get rejected as follows (an example): -- Forwarded message -- From: mailto:women-boun...@mail.rc.orgwomen-boun...@mail.rc.org Date: 2009/6/7 Subject: The results of your email commands To: mailto:yvo...@gmail.comuser_n...@gmail.com The results of your email command are provided below. Attached is your original message. - Results: Ignoring non-text/plain MIME parts Invalid confirmation string. Note that confirmation strings expire approximately 3 days after the initial subscription request. If your confirmation has expired, please try to re-submit your original request or message. - Unprocessed: confirm ffc239cae5b91c5b2f50ec283ab33f0e1550544d - Done. -- Forwarded message -- From: User Name mailto:yvo...@gmail.comuser_n...@gmail.com To: mailto:women-requ...@mail.rc.orgwomen-requ...@mail.rc.org Date: Sun, 7 Jun 2009 21:38:58 +0200 Subject: confirm ffc239cae5b91c5b2f50ec283ab33f0e1550544d confirm ffc239cae5b91c5b2f50ec283ab33f 0e1550544d There are two confirmation commands in the above message. One in the subject and one in the body. While the one in the body is wrapped above, it appears it was not and was therefore OK in the original email. Have you verified that the confirmation was in fact submitted before it expired? Have you verified that the address change was not confirmed and the address wasn't changed? The above response is a normal response to a confirmation like the above if the confirmation was either expired or previously processed by web or email. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Allan Hansen P.O Box 2423 Cypress, CA 90630 U.S.A. han...@rc.org +1-714-875-8870 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Mailman crash during global address change
Dear list developers, A crash happened when a subscriber attempted to change his address with 'Apply Globaly' check box set. His subscriptions before the crash was: List1: o...@address.com List2: n...@address.com The crash happened the moment he attempted to confirm the change on the given web page. He was trying to change the address for List1 from o...@address.com to n...@address.com. I had him do the same thing again both with and without setting the 'Apply Globally' box. When the check was set, the crash happened again. When he did not check it, the address change did happen without a crash. How it possibly can get to this error is beyond me. His new address did not appear in List1 and his old address did not appear in List2 (I checked before I asked him to repeat). I've detected no adverse effects from this crash, so this message is for your information only. I searched the archives for MMAlreadyAMember, but did not find anything useful. Thanks, Allan Setup: Mailman 2.1.9 on Intel iMac 2.66 GHz Core 2 Duo with OS X Server 10.5.6 Traceback: Feb 01 12:01:43 2009 admin(14357): admin(14357): [- Mailman Version: 2.1.9 -] admin(14357): [- Traceback --] admin(14357): Traceback (most recent call last): admin(14357): File /usr/share/mailman/scripts/driver, line 101, in run_main admin(14357): main() admin(14357): File /BinaryCache/mailman/mailman-126.1~4/Root/usr/share/mailman/Mailman/Cgi/confirm.py, line 138, in main admin(14357): File /BinaryCache/mailman/mailman-126.1~4/Root/usr/share/mailman/Mailman/Cgi/confirm.py, line 521, in addrchange_confirm admin(14357): File /BinaryCache/mailman/mailman-126.1~4/Root/usr/share/mailman/Mailman/MailList.py, line 1217, in ProcessConfirmation admin(14357): File /BinaryCache/mailman/mailman-126.1~4/Root/usr/share/mailman/Mailman/MailList.py, line 1150, in ApprovedChangeMemberAddress admin(14357): File /BinaryCache/mailman/mailman-126.1~4/Root/usr/share/mailman/Mailman/OldStyleMemberships.py, line 251, in changeMemberAddress admin(14357): File /BinaryCache/mailman/mailman-126.1~4/Root/usr/share/mailman/Mailman/OldStyleMemberships.py, line 175, in addNewMember admin(14357): MMAlreadyAMember: n...@address.com admin(14357): [- Python Information -] admin(14357): sys.version = 2.5.1 (r251:54863, Apr 15 2008, 22:57:26) [GCC 4.0.1 (Apple Inc. build 5465)] admin(14357): sys.executable = /System/Library/Frameworks/Python.framework/Versions/2.5/Resources/Python.app/Contents/MacOS/Python admin(14357): sys.prefix = /System/Library/Frameworks/Python.framework/Versions/2.5 admin(14357): sys.exec_prefix = /System/Library/Frameworks/Python.framework/Versions/2.5 admin(14357): sys.path= /System/Library/Frameworks/Python.framework/Versions/2.5 admin(14357): sys.platform= darwin Allan -- Allan Hansen P.O Box 2423 Cypress, CA 90630 U.S.A. han...@rc.org +1-714-875-8870 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] A lot of unsubscribes
Hi all, I recently updated my server from Mac OS X 10.4 to 10.5, with the attendant upgrade of Mailman. Following that, the server suddenly unsubscribed some 300 subscribers from various lists. Is that to be expected or should I resubscribe them? Thanks, Allan -- Allan Hansen P.O Box 2423 Cypress, CA 90630 U.S.A. han...@rc.org +1-714-875-8870 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] A lot of unsubscribes
Closer examination has revealed that most if not all of these unsubscriptions are valid. The 'cron' explanation appears correct, because when I upgraded, I also found that the password reminders were suddenly being sent out, which they had not before. Looking at crontab, I found the cron job to do just that. I wonder if this is something Apple bungled when they stopped using cron jobs for their own scheduled tasks. In any case, the jobs are now running again. Thank you for the hint. Allan At 3:56 PM -0800 12/15/08, Mark Sapiro wrote: Allan Hansen wrote: I recently updated my server from Mac OS X 10.4 to 10.5, with the attendant upgrade of Mailman. Following that, the server suddenly unsubscribed some 300 subscribers from various lists. Is that to be expected or should I resubscribe them? It's not expected, but in order to know whether to resubscribe them, you need to know why they were unsubscribed. Here are some possibilities. Presumably the actual unsubscribes were of bouncing members by cron/disabled. Possibly cron/disabled was not being run before and the server/Mailman upgrade installed a new crontab for Mailman. Prior to Mailman 2.1.10, if bounce_score_threshold for a list was reduced, members with stale bounce info with scores = the new threshold would be disabled and/or unsubscribed. This wouldn't explain your situation unless you happened to reduce some bounce_score_threshold settings. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Allan Hansen P.O Box 2423 Cypress, CA 90630 U.S.A. han...@rc.org +1-714-875-8870 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Admin access restrictions in 2.1.9
Hi all, I just upgraded my system from Mailman 2.1.5 to 2.1.9. After this change I am no longer able to use the 'Change globally' options when helping my subscribers change their subscription addresses or such. I have used mmsitepass to set a site administrator password (to be sure that that is the password I'm using). Looking at SecurityManager.py (I'm no Python wizzard) I get the impression that that password should let me do things globally, and this was, indeed, the case in 2.1.5. I have searched both the Wiki and the archive for info, but was not successful in finding it if it is there, sorry. How can I restore this ability? Thanks, Allan System: Mac OS/X 10.5.5 Server on iMac -- Allan Hansen P.O Box 2423 Cypress, CA 90630 U.S.A. [EMAIL PROTECTED] +1-714-875-8870 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Promotion
I agree, and it's not harsh enough. My first reaction to this was Oh-My-God. My second reaction was to think that we needed an agreement among Mailman list users that Mailman not be used for spam. Then I realized that that would only inconvenience legit Mailman users and spammers would not care to lie, just as they don't care about how grievously they inconvenience and lie to everyone on their 1,000,000 long subscriber lists. So I suppose that the best response is to simply ignore requests such as this which so obviously is from a spammer. Allan At 10:34 AM +0100 1/24/08, Zbigniew Szalbot wrote: Hello, 2008/1/24, Khalil Abbas [EMAIL PROTECTED]: Hello mailman guys.. ok, I have a dedicated server .. and I use mailman to send a daily newsletter.. I recenly got a list of 1,000,000 email addresses that I want to use to promote my website and mailing list .. can I create another mailman installation and add these addresses to it and use it to send an invitation to visit my website and join my mailing list without the risk of getting blocked by hotmail or yahoo or others because these emails I bought will have many faulty ones and will generate excessive bounces.. is mailman programmed in a way to avoid getting blocked by hotmail and others?? or do u think it's better to buy another server and use it for promotion? I may sound harsh but you cannot just get a list of 1,000,000 just like that. I do not think Mailman creators wanted their product to be used as a tool for spammers. Unless, these people have volunteered to be sent offers. I am not suggesting any solution because I am very much against such practices. Zbigniew Szalbot -- Allan Hansen P.O Box 2423 Cypress, CA 90630 U.S.A. [EMAIL PROTECTED] +1-714-875-8870 -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Help a newbie out! How to list users of a specific list
I have a web page (password protected) with a form that accepts requests to have the membership lists sent to the requester via email. The forms' CGI Perl script generates files on the server with these requests. A cron job with the proper privileges checks the file content and then uses the Mailman API to generate the list and send the file to the requestor if the requestor email is verified against an internal list of approved addresses for each list. Another form lets certain people (who are not list admins) enter and remove subscriptions. This form works the same way as the above. Allan Hello, We host several lists here and I would like to know how to list users/subscribers list by list. Is there an easy way of doing that? Thank you, Matthew Smith Tampa Bay Library Consortium 813-622-8252 X229 [EMAIL PROTECTED] -- Allan Hansen P.O Box 2423 Cypress, CA 90630 U.S.A. [EMAIL PROTECTED] +1-714-875-8870 -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] no dupes across lists?
At 2:34 +0900 12/17/07, Stephen J. Turnbull wrote: Allan Hansen writes: That's interesting. I run Mailman 2.1.5 (Mac OS X 10.4) and have the 'problem' that when someone posts to two lists at a time, I get only one message. I actually do want to get both for archival purposes. If this is not a function of Mailman 2.1.5, I wonder where the other message is cut. :-) What do you mean by get? I get both messages in my system mailbox, but because I have duplicate suppression on in my MUA, I only see one. The MUA automatically skips any message with a Message-ID that it has already seen. More detail: One message from a subscriber's MUA goes to two lists in Mailman because that person is addressing it using To: [EMAIL PROTECTED], [EMAIL PROTECTED] The subscriber (who is not I) is subscribed to both lis1 and list2 (I verified this). I'm also subscribed to both list1 and list2 (also verified). Mailman is the actual recipient of this message. However, being a listserver, Mailman becomes the originator (literally) of two new messages, one for the subscribers of list1 and another for the subscribers of list2. It has to be two messages, because one message has additional headers and a footer added for list1 and the other has headers and a footer added for list2. In fact, Mailman even adds the Sender: header with the list as the sender. I'm subscribed to both list1 and list2, so I'll expect to see two different messages being picked up by my MUA. One message with Sender: [EMAIL PROTECTED] and another with Sender: [EMAIL PROTECTED] This, in fact, is how it worked in a previous list server (ListStar) that I used before Mailman. In Mailman I'm seeing only the message corresponding to list2. My MTA is Postfix and my MUA is Eudora (both running under Mac OS X 10.4.11). I cannot imagine my MUA comparing the two messages and throwing one out, as the message bodies are, in fact, different. Ditto for the MDA and MTA. Allan I would assume you've got a similar feature, perhaps not in your MUA but in the MDA or MTA. (No need for action from anyone - I was just mumbling aloud). Allan At 16:49 -0800 12/14/07, Mark Sapiro wrote: Gruver, Sandi wrote: Does the 'no dupes' option mean that members will not receive a messages sent to more than one list to which they are subscribed? No. It only means that a member will not receive the post from the list if (s)he in specifically addressed in To: or Cc: of the post. If you have lists with duplicate members which are frequently cross posted, the new sibling lists 'exclude' feature in Mailman 2.1.10 can be used to avoid these duplicate messages. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Allan Hansen P.O Box 2423 Cypress, CA 90630 U.S.A. [EMAIL PROTECTED] +1-714-875-8870 -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/stephen%40xemacs.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- Allan Hansen P.O Box 2423 Cypress, CA 90630 U.S.A. [EMAIL PROTECTED] +1-714-875-8870 -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] no dupes across lists?
That's interesting. I run Mailman 2.1.5 (Mac OS X 10.4) and have the 'problem' that when someone posts to two lists at a time, I get only one message. I actually do want to get both for archival purposes. If this is not a function of Mailman 2.1.5, I wonder where the other message is cut. :-) (No need for action from anyone - I was just mumbling aloud). Allan At 16:49 -0800 12/14/07, Mark Sapiro wrote: Gruver, Sandi wrote: Does the 'no dupes' option mean that members will not receive a messages sent to more than one list to which they are subscribed? No. It only means that a member will not receive the post from the list if (s)he in specifically addressed in To: or Cc: of the post. If you have lists with duplicate members which are frequently cross posted, the new sibling lists 'exclude' feature in Mailman 2.1.10 can be used to avoid these duplicate messages. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Allan Hansen P.O Box 2423 Cypress, CA 90630 U.S.A. [EMAIL PROTECTED] +1-714-875-8870 -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] (no subject)
You may also want to change add_members as follows: from mlist.setDeliveryStatus(member, ... to mlist.setDeliveryStatus(userdesc.address, ... in case you want to use that, too. (I had to make that change) Allan On vendredi 12 octobre 2007, Mark Sapiro wrote: Frédéric Mantegazza wrote: Using sync_members on a file containing names and addresses, I get : Traceback (most recent call last): File /usr/sbin/sync_members, line 286, in ? main() File /usr/sbin/sync_members, line 259, in main s = email.Utils.formataddr((name, addr)).encode(enc, 'replace') UnicodeDecodeError: 'ascii' codec can't decode byte 0xe9 in position 3: ordinal not in range(128) Is this script able to handle non-ascii chars? There is a problem with the script, however at the point of the above error, the user had already been added and it is only in formatting the name and address for printing in the 'Added :' message that the error occurs. I think you can simply change line 289 of sync_members to s = email.Utils.formataddr((name, addr)) to avoid this problem. Please try that and report. Yes, it works. There are 2 lines with this call; I also had to change the first one to make it work. Thanks. -- Frédéric http://www.gbiloba.org -- Allan Hansen P.O Box 2423 Cypress, CA 90630 U.S.A. [EMAIL PROTECTED] +1-714-875-8870 -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Mass subscription
Hello, I have happily noticed that mass subscription allows for a b [EMAIL PROTECTED] rather than just [EMAIL PROTECTED]. But I see two problems: 1. if a or b includes a letter with an accent, mailman says that the invitation/susbcription has failed. 2. the subscriber list for members includes email addresses only; there are no names. What version are you using? In my version, the names appear right under the email address in a text field. Mikael -- Allan Hansen P.O Box 2423 Cypress, CA 90630 U.S.A. [EMAIL PROTECTED] +1-714-875-8870 -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] text/html problem
Mailman Gurus, One of my list members is sending messages to one of my list as follows: MIME-version: 1.0 Content-type: text/html; format=flowed x-html!x-stuff-for-pete base= src= id=0 charset=iso-8859-1/macintoshhtml... At first, the message was rejected as having an unacceptable content. Adding text/html to the list of 'pass_mime_types' got her past that rejection. But now, while the message now got through, the message contents did not. Other text/html messages are passing through, but with charset= instead, so I assume that that might be part of the problem. The settings as they appear in the 'Content filtering' section are: Filter? Yes Remove attachments of matching content type: None Remove attachments not matching content type: multipart/mixed multipart/alternative text/plain text/html Convert text/html to plain text: Yes Action: Reject Mailman 2.1.5 on OS X Server Thanks in advance for any hints (yes, I searched for text/html, charset and iso-8859-1 in the archive, but found only stuff releated to footers. Allan -- _ | Allan Hansen, Ph.D. | |P.O. Box 2423, Cypress, CA 90630, U.S.A. | | | | Work: Home:| | Phone: +1-714/952-6015 +1-714/875-8870 | | Fax: +1-714/952-6746 | | Email: [EMAIL PROTECTED][EMAIL PROTECTED]| | WWW: http://www.ugs.com http://www.rc.org/ | | | |_Anything is possible with the right tools and right information_| -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] text/html problem
Aha! My installation didn't have Lynx. I now have installed it and pointed mm_cfg.py at the right program. I have notified my subscriber of this. I'll report back if it works (I could not get my own mail client to send the same kind of mail she did, but when I tried, it still had the xhtml stuff. Allan From Mark Sapiro: It seems you have convert html to plain text On in content filtering. The body is getting lost in this process. I don't know why. I tried converting the body of the second message with both lynx and links and it worked for me. What, if anything, do you have in mm_cfg.py for HTML_TO_PLAIN_TEXT_COMMAND? If you have nothing in mm_cfg.py, the default is HTML_TO_PLAIN_TEXT_COMMAND = '/usr/bin/lynx -dump %(filename)s' -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- _ | Allan Hansen, Ph.D. | |P.O. Box 2423, Cypress, CA 90630, U.S.A. | | | | Work: Home:| | Phone: +1-714/952-6015 +1-714/875-8870 | | Fax: +1-714/952-6746 | | Email: [EMAIL PROTECTED][EMAIL PROTECTED]| | WWW: http://www.ugs.com http://www.rc.org/ | | | |_Anything is possible with the right tools and right information_| -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Remove sender from list?
No, there's no such option, Alan. Allan At 9:33 +0200 5/5/06, Alan wrote: Ok, that is one option. Now is it possible to control it through some keywords in header of mail. Similar to putting Approved: password in the first line of post. I would like to avoid logging in to admin panel. Alan Allan Hansen wrote: Sure, Set the user's option to 'nomail', send the message and set the user's option back. You'll need admin access to do that, though, as moderators don't have access to the options. Allan At 9:11 +0200 5/4/06, Alan wrote: Is it possible to remove exclude someone form the list for just one time using some keywords or headers? Situation is: I have a list named 123 I have a user user1 in that list I get a mail from user1 and want to forward it to list 123 but would like to exclude user1 from the list for that one time I hope you understand what I mean :-) Alan -- _ | Allan Hansen, Ph.D. | |P.O. Box 2423, Cypress, CA 90630, U.S.A. | | | | Work: Home:| | Phone: +1-714/952-6015 +1-714/875-8870 | | Fax: +1-714/952-6746 | | Email: [EMAIL PROTECTED][EMAIL PROTECTED]| | WWW: http://www.ugs.com http://www.rc.org/ | | | |_Anything is possible with the right tools and right information_| -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Remove sender from list?
Sure, Set the user's option to 'nomail', send the message and set the user's option back. You'll need admin access to do that, though, as moderators don't have access to the options. Allan At 9:11 +0200 5/4/06, Alan wrote: Is it possible to remove exclude someone form the list for just one time using some keywords or headers? Situation is: I have a list named 123 I have a user user1 in that list I get a mail from user1 and want to forward it to list 123 but would like to exclude user1 from the list for that one time I hope you understand what I mean :-) Alan -- _ | Allan Hansen, Ph.D. | |P.O. Box 2423, Cypress, CA 90630, U.S.A. | | | | Work: Home:| | Phone: +1-714/952-6015 +1-714/875-8870 | | Fax: +1-714/952-6746 | | Email: [EMAIL PROTECTED][EMAIL PROTECTED]| | WWW: http://www.ugs.com http://www.rc.org/ | | | |_Anything is possible with the right tools and right information_| -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] error install MM on MAC OS x
Again, I was just trying to help a newbie user. And thank you, Dan, for clarifying the misinformation about Mailman on OS X Server. I thought that I had made it clear that the Mailman interfaces work just fine there and that as far as Mailman is concerned, there's no need for Apple support. Either you use the Apple custom management GUI with the Apple-modified versions of the old code, or you use the new code (with the new features and the security fixes) with the standard Mailman web or CLI management interface. This statement by Brad is simply hogwash. Allan -- _ | Allan Hansen, Ph.D. | |P.O. Box 2423, Cypress, CA 90630, U.S.A. | | | | Work: Home:| | Phone: +1-714/952-6015 +1-714/875-8870 | | Fax: +1-714/952-6746 | | Email: [EMAIL PROTECTED][EMAIL PROTECTED]| | WWW: http://www.ugs.com http://www.rc.org/ | | | |_Anything is possible with the right tools and right information_| -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] error install MM on MAC OS x
Celes, May I suggest that you get hold of Mac OS X Server and install that on you server instead. It comes with Mailman already installed and ready to go. It has a lot of other tools pre-installed that will be very useful to you. The Mac is a great platform for servers. That all said, you'll likely at some point need to install the Developer Tools anyway. Allan At 11:24 +0800 4/26/06, Celes Victoria wrote: thank u to reply (^_^)... no, i don't see it,.. are u forgot / misspell of afp458.com ? in there i just not find linked to mac... so the kind should i install from developer tools is FWIW? cos i'm newbie for mac os X i don't wanna get wrong to install it is apple.com provide the developer tools on it? can i download install it? thank you.. Yes, you must install the Developer Tools. FWIW, if you've already su'ed to root, there's no need for sudo. Have you seen the instructions at afp458.com? Dan Dan Phillips Associate Professor Rudi E. Scheidt School of Music University of Memphis [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Movies - Search movie info and celeb profiles and photos. http://sg.movies.yahoo.com/ -- _ | Allan Hansen, Ph.D. | |P.O. Box 2423, Cypress, CA 90630, U.S.A. | | | | Work: Home:| | Phone: +1-714/952-6015 +1-714/875-8870 | | Fax: +1-714/952-6746 | | Email: [EMAIL PROTECTED][EMAIL PROTECTED]| | WWW: http://www.ugs.com http://www.rc.org/ | | | |_Anything is possible with the right tools and right information_| -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] error install MM on MAC OS x
At 21:07 -0500 4/29/06, Brad Knowles wrote: At 4:24 PM -0700 2006-04-29, Allan Hansen wrote: May I suggest that you get hold of Mac OS X Server and install that on you server instead. It comes with Mailman already installed and ready to go. It has a lot of other tools pre-installed that will be very useful to you. The Mac is a great platform for servers. Using MacOS X Server is not necessarily the best idea if using Mailman is your goal. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq01.021.htp for more information, especially the links at the end. It appears that most people who want to use Mailman on MacOS X Server end up ripping out the Apple-supplied custom version and instead installing the standard version from our tarballs. If you're going to go that route, you might as well do that on MacOS X Client as opposed to spending lots of extra money for MacOS X Server. I agree that the Server Admin interface for Mailman is limited and too buggy to be of serious use. It can, however, allow someone new to the OS set up Mailman lists with not much ado, which was the situation at hand, Brad. Installing Mailman and other attendant server tools (in particular) is not, I believe a newbie's best path. Solutions should be tailored to the problems presented. Once Mailman is up and running, the administrator should, of course switch to web/command line tools. I have (so far) been successful setting up a workable system that allows my moderators to subscribe and unsubscribe and set member options. I run some close to 40 lists - granted not many but plenty to handle anyway. The server, lastly, does not cost lots of extra money for what you get. It's well worth it if you don't plan to be a full-time administrator. Allan -- _ | Allan Hansen, Ph.D. | |P.O. Box 2423, Cypress, CA 90630, U.S.A. | | | | Work: Home:| | Phone: +1-714/952-6015 +1-714/875-8870 | | Fax: +1-714/952-6746 | | Email: [EMAIL PROTECTED][EMAIL PROTECTED] | | WWW: http://www.ugs.com http://www.hansen-family.us/ | | | |_Anything is possible with the right tools and right information_| -- _ | Allan Hansen, Ph.D. | |P.O. Box 2423, Cypress, CA 90630, U.S.A. | | | | Work: Home:| | Phone: +1-714/952-6015 +1-714/875-8870 | | Fax: +1-714/952-6746 | | Email: [EMAIL PROTECTED][EMAIL PROTECTED]| | WWW: http://www.ugs.com http://www.rc.org/ | | | |_Anything is possible with the right tools and right information_| -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Little doubt
[EMAIL PROTECTED] wrote: The page I edit and gives problems is the Welcome email text file - a text file. As far as the html files, there's no problem. Citando Mark Sapiro [EMAIL PROTECTED]: [EMAIL PROTECTED] wrote: 2) When I edit the files to be showed to the user, the text one appears with funny characters when I use letters like ã, ô, à, á, ç, etc - they are used in portuguese. How can I prevent this of happening? Which files are you editing? How are you editing them? Where are you placing edited versions? Are you perhaps creating edited templates with, e.g., utf-8 encoding (pt templates need to be iso-8859-1 encoded)? Jonannes, Would it help to encode these special characters in the HTML text as follows: atilde; ocirc; agrave; aacute; ccedil; etc.? Allan -- _ | Allan Hansen, Ph.D. | |P.O. Box 2423, Cypress, CA 90630, U.S.A. | | | | Work: Home:| | Phone: +1-714/952-6015 +1-714/875-8870 | | Fax: +1-714/952-6746 | | Email: [EMAIL PROTECTED][EMAIL PROTECTED] | | WWW: http://www.ugs.com http://www.hansen-family.us/ | | | |_Anything is possible with the right tools and right information_| -- _ | Allan Hansen, Ph.D. | |P.O. Box 2423, Cypress, CA 90630, U.S.A. | | | | Work: Home:| | Phone: +1-714/952-6015 +1-714/875-8870 | | Fax: +1-714/952-6746 | | Email: [EMAIL PROTECTED][EMAIL PROTECTED]| | WWW: http://www.ugs.com http://www.rc.org/ | | | |_Anything is possible with the right tools and right information_| -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] (no subject)
In this gents case I KNOW of SIX, repeat SIX e-mails accounts he uses. Do I know the very FIRST letter of the account he uses for his subscription?? No. So I have to go thru entire ALPHABET [page per letter at a time] to find it instead of just being able to scroll down a 60 member page. Instead of looking up subscribers by address, use their names. And instead of using the Mailman interface, use your mail client (I use Eudora, which has a VERY fast and flexible search engine): All subscriptions to my lists (40 of them) go through a very simple web interface that requires a name and an address. (My moderators have access to this page, so that they can moderate and subscribe/unsubscribe without being admins - I hesitate giving anyone admin access, but they do need the subscribe/unsubscribe/list_members functionality). Mailman then sends emails to me with the subscription list, name and address. Eudora (my mail client) filters those into a separate folder. I can now search for a person's name in the Eudora mail box and see all his/her subscriptions over time. Mailman also sends unsubscriptions to me, filtered into a separate mailbox. These messages have only the subscriber address, which is fine by me. Finally, every month, a cron job sends the contents of all the lists to me. These contain the person's name and address both and get filtered by Eudora into yet another mailbox (containing 'current' subscriptions) (Whenever I get a batch of these, I purge last month's batch). This setup lets me quickly see what current subscriptions anyone has without going anywhere near the server's web interface and without knowing the person's multiple addresses. I just search for the name. Allan -- _ | Allan Hansen, Ph.D. | |P.O. Box 2423, Cypress, CA 90630, U.S.A. | | | | Work: Home:| | Phone: +1-714/952-6015 +1-714/875-8870 | | Fax: +1-714/952-6746 | | Email: [EMAIL PROTECTED][EMAIL PROTECTED]| | WWW: http://www.ugs.com http://www.rc.org/ | | | |_Anything is possible with the right tools and right information_| -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Accessing lists
At 14:53 -0500 4/10/06, Brad Knowles wrote: At 2:40 PM -0500 2006-04-10, Brad Knowles wrote: On the other hand, bin/find_member can search through all the lists hosted on python.org pretty quickly. There's another factor here -- we have plenty of subscribers who never have never posted to the list, and therefore would never show up in my Eudora archive, even if I had a complete list of every message ever sent to the lists. In that case, using the server-based tools are the only viable option. Please read my message again, Brad. I'm not looking at posts, but subscribe and unsubscribe messages. Allan -- _ | Allan Hansen, Ph.D. | |P.O. Box 2423, Cypress, CA 90630, U.S.A. | | | | Work: Home:| | Phone: +1-714/952-6015 +1-714/875-8870 | | Fax: +1-714/952-6746 | | Email: [EMAIL PROTECTED][EMAIL PROTECTED]| | WWW: http://www.ugs.com http://www.rc.org/ | | | |_Anything is possible with the right tools and right information_| -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Accessing lists
Well, I was just trying to help the poor soul who was struggling with the web interface, assuming that he could not get to the command-line tools. Allan -- _ | Allan Hansen, Ph.D. | |P.O. Box 2423, Cypress, CA 90630, U.S.A. | | | | Work: Home:| | Phone: +1-714/952-6015 +1-714/875-8870 | | Fax: +1-714/952-6746 | | Email: [EMAIL PROTECTED][EMAIL PROTECTED]| | WWW: http://www.ugs.com http://www.rc.org/ | | | |_Anything is possible with the right tools and right information_| -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] 1 email for multiple email-list recipients onsame server?
I run a bunch of lists and have set up a special 'all_subscribers' list that I maintain with a cron job that runs every night. The cron job runs the following script: the file list_of_all_lists contains the names of all the lists I want to include with this 'all_subscribers' list. #!/bin/bash touch /tmp/all_subs for i in $(cat list_of_all_lists) do /usr/share/mailman/bin/list_members -f --nomail=enabled $i /tmp/all_subs done cat /tmp/all_subs|sort -u /tmp/all_subs.sorted /usr/share/mailman/bin/sync_members -f /tmp/all_subs.sorted all_subscribers /dev/null rm /tmp/all_subs /tmp/all_subs.sorted ## Sending to this list causes the post to go to each subscriber of any list just once. I have another list that combines a subset of the lists similarly. Allan At 10:27 -0600 3/9/06, Matt England wrote: At 3/9/2006 10:20 AM, Mark Sapiro wrote: Now suppose it finds listb and listc in those headers. It would then have to look at the members of those lists and see if the current delivery candidate is a member of one of those lists, has delivery enabled on that list and is receiving messages and not digests from that list. ...yes... And then if it did all those things and decided not to deliver, presumably listb and listc would do the same thing and not deliver either and the user would receive 0 emails. ...and this seems to be the trickiest part: which list becomes the primary one. I can envision straightforward (even though they are not easy to implement solutions) to everything except this last point. :( See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.005.htp for some ideas about how to build unduplicated 'super lists' that can be used to post to the members of more than one list. Thanks for the reference, that's very helpful. -Matt -- _ | Allan Hansen, Ph.D. | |P.O. Box 2423, Cypress, CA 90630, U.S.A. | | | | Work: Home:| | Phone: +1-714/952-6015 +1-714/875-8870 | | Fax: +1-714/952-6746 | | Email: [EMAIL PROTECTED][EMAIL PROTECTED]| | WWW: http://www.ugs.com http://www.rc.org/ | | | |_Anything is possible with the right tools and right information_| -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] add_members
Mark,
Bingo!
The script from the sourceforge site works fine. Here are the
diffs between that version and the version that Apple is providing. Note the
change of address of Foundation and the ill-fated option in the Apple-supplied
version to disable mail for the new subscriber. ( is official version, is
Apple's version).
A bit of nosing around on the sourceforge site shows that the address was
changed on the main cvs branch from version 2.16 to version 2.17 on 8/17/05.
The copyright notice on both 2.17 and Apple's version are both 1998-2003.
None of the versions 2003 and later has Apple's changes, as you also noted.
So Apple's version does, indeed, appear to be an Apple hack gone awry.
I suppose it could be fixed by extracting the address before sending
the member to setDeliveryStatus, but I'll refrain from that.
Thank you for the sourceforge reference. It will simplify my scripts.
Allan
The differences:
17c17
# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301,
USA.
---
# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
54a55,58
--enable-mail=y|n
-e y|n
Enable user mail deilvery options.
79a84
from Mailman import MemberAdaptor
127c132
def addall(mlist, members, digest, ack, outfp):
---
def addall(mlist, members, digest, ack, outfp, enable):
137a143,146
if enable == 1:
mlist.setDeliveryStatus(member, MemberAdaptor.ENABLED)
else:
mlist.setDeliveryStatus(member, MemberAdaptor.BYADMIN)
146a156,160
if enable == 1:
mlist.setDeliveryStatus(member, MemberAdaptor.ENABLED)
else:
mlist.setDeliveryStatus(member, MemberAdaptor.BYADMIN)
149d162
153c166
'a:n:r:d:w:h',
---
'a:n:r:e:d:w:h',
154a168
'enable-mail=',
168a183
enable_mail = 1
184a200,206
elif opt in ('-e', '--enable-mail'):
if arg.lower()[0] == 'y':
enable_mail = 1
elif arg.lower()[0] == 'n':
enable_mail = 0
else:
usage(1, _('Bad argument to -3/--enable-mail: %(arg)s'))
235c257
addall(mlist, nmembers, 0, send_welcome_msg, s)
---
addall(mlist, nmembers, 0, send_welcome_msg, s, enable_mail)
238c260
addall(mlist, dmembers, 1, send_welcome_msg, s)
---
addall(mlist, dmembers, 1, send_welcome_msg, s, enable_mail)
256d277
At 22:20 -0800 2/27/06, Mark Sapiro wrote:
Allan Hansen wrote:
I'm starting with an empty list called Test and a file, Long,
with a subscriber (me) in long format, and another file, Short,
with a subscriber (me) in short format:
// Empty list
$/usr/share/mailman/bin/list_members -f Test
nothing
// The files Long and Short
$cat Long
Allan Hansen [EMAIL PROTECTED]
$cat Short
[EMAIL PROTECTED]
// Here's the traceback from add_members:
$add_members -r Long Test
Traceback (most recent call last):
File /usr/share/mailman/bin/add_members, line 277, in ?
main()
File /usr/share/mailman/bin/add_members, line 257, in main
addall(mlist, nmembers, 0, send_welcome_msg, s, enable_mail)
File /usr/share/mailman/bin/add_members, line 157, in addall
mlist.setDeliveryStatus(member, MemberAdaptor.ENABLED)
File /usr/share/mailman/Mailman/OldStyleMemberships.py, line 338, in
setDeliveryStatus
self.__assertIsMember(member)
File /usr/share/mailman/Mailman/OldStyleMemberships.py, line 113, in
__assertIsMember
raise Errors.NotAMemberError, member
Mailman.Errors.NotAMemberError: Allan Hansen [EMAIL PROTECTED]
This is apparently some Apple modified add_members script. The line
numbers don't correlate with any distributed Mailman 2.1.x, and the
standard script does not call the setDeliveryStatus() method at all.
snip
// Now, let's try removing same. We have a problem:
$/usr/share/mailman/bin/remove_members -f Long Test
No such member: Allan Hansen [EMAIL PROTECTED]
Yes, I mentioned this previously. remove_members does not accept the
'long' format, but then if you're removing a member, you probably
don't care about the 'name'.
The above shows that 'add_members' and 'remove_members' don't understand
the long format that is readily accepted by 'sync_members' and output by
'list_members'.
Well, my add_members does. I think Apple broke yours. You might try
getting a recent add_members from
http://cvs.sourceforge.net/viewcvs.py/mailman/mailman/bin/add_members,
and see if that works for you.
--
Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
_
| Allan Hansen, Ph.D. |
|P.O. Box 2423, Cypress, CA 90630, U.S.A
Re: [Mailman-Users] add_members
Thank you for clarifying, Mark. I do not yet have the knowledge to fix it, thus my comment. I do appreciate the fix, though, because a number of my subscribers do want to be subscribed inactive from a second address that they use for posts (and they don't want duplicates). So I'll use your version. Allan At 9:18 -0800 2/28/06, Mark Sapiro wrote: Mark Sapiro wrote: Allan Hansen wrote: So Apple's version does, indeed, appear to be an Apple hack gone awry. I suppose it could be fixed by extracting the address before sending the member to setDeliveryStatus, but I'll refrain from that. Yes, but why? Upon rereading my post, I see the above but why doesn't say what I meant. It appears that I'm saying but why refrain from fixing the hack? This is definitely not what I meant to say. I meant to say but why fix it?, just the opposite of how it comes out. I did indicate how you could fix it, but I also tried to say that I didn't see a real need for the botched option in the first place. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- _ | Allan Hansen, Ph.D. | |P.O. Box 2423, Cypress, CA 90630, U.S.A. | | | | Work: Home:| | Phone: +1-714/952-6015 +1-714/875-8870 | | Fax: +1-714/952-6746 | | Email: [EMAIL PROTECTED][EMAIL PROTECTED]| | WWW: http://www.ugs.com http://www.rc.org/ | | | |_Anything is possible with the right tools and right information_| -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] add_members
At 8:13 -0800 2/27/06, Mark Sapiro wrote: Allan Hansen wrote: add_members -r file list crashes with a traceback when given a file in the above format. The crash appears to happen in OldStyleMemberships.py add_members appears to strip all whitespace from the file. Please provide a traceback for analysis. (Note that despite the perhaps misleading comment, line.strip() only strips leading and trailing whitespace, not all whitespace.) Sure, Mark (my apologies for misinterpreting what line.strip() does. Here goes: I'm starting with an empty list called Test and a file, Long, with a subscriber (me) in long format, and another file, Short, with a subscriber (me) in short format: // Empty list $/usr/share/mailman/bin/list_members -f Test nothing // The files Long and Short $cat Long Allan Hansen [EMAIL PROTECTED] $cat Short [EMAIL PROTECTED] // Here's the traceback from add_members: $add_members -r Long Test Traceback (most recent call last): File /usr/share/mailman/bin/add_members, line 277, in ? main() File /usr/share/mailman/bin/add_members, line 257, in main addall(mlist, nmembers, 0, send_welcome_msg, s, enable_mail) File /usr/share/mailman/bin/add_members, line 157, in addall mlist.setDeliveryStatus(member, MemberAdaptor.ENABLED) File /usr/share/mailman/Mailman/OldStyleMemberships.py, line 338, in setDeliveryStatus self.__assertIsMember(member) File /usr/share/mailman/Mailman/OldStyleMemberships.py, line 113, in __assertIsMember raise Errors.NotAMemberError, member Mailman.Errors.NotAMemberError: Allan Hansen [EMAIL PROTECTED] // The command did not add the address: $/usr/share/mailman/bin/list_members -f Test nothing // Now let's use the sync instead. No problem here: $/usr/share/mailman/bin/sync_members -f Long Test Added : Allan Hansen [EMAIL PROTECTED] // The address is indeed added: $/usr/share/mailman/bin/list_members -f Test Allan Hansen [EMAIL PROTECTED] // Now, let's try removing same. We have a problem: $/usr/share/mailman/bin/remove_members -f Long Test No such member: Allan Hansen [EMAIL PROTECTED] // Indeed, the command failed: $/usr/share/mailman/bin/list_members -f Test Allan Hansen [EMAIL PROTECTED] // But we can use the short format. There's no output from this command. $/usr/share/mailman/bin/remove_members -f Short Test nothing // But the command did succeed: $/usr/share/mailman/bin/list_members -f Test nothing The above shows that 'add_members' and 'remove_members' don't understand the long format that is readily accepted by 'sync_members' and output by 'list_members'. Allan -- _ | Allan Hansen, Ph.D. | |P.O. Box 2423, Cypress, CA 90630, U.S.A. | | | | Work: Home:| | Phone: +1-714/952-6015 +1-714/875-8870 | | Fax: +1-714/952-6746 | | Email: [EMAIL PROTECTED][EMAIL PROTECTED]| | WWW: http://www.ugs.com http://www.rc.org/ | | | |_Anything is possible with the right tools and right information_| -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Can't Delete Corrupt Subscriber Address
How about: bin/list_members -f list|grep -v -e [EMAIL PROTECTED] list bin/sync_members -f list list Allan Tim wrote: We have a subscriber address that has /t on the end of it ([EMAIL PROTECTED]/t) which can only be seen when dumping the lists config file. The subscriber address looks normal [EMAIL PROTECTED]) when looking for it using any other method (list members, etc). Do you mean '\t', i.e. a tab character? Is the difference between '\t' and '/t' a typo here or does it have something to do with your lack of success? If you try the '-f' option with list_members, you might actually see the tab between 'xxx.com' and the terminating ''. I've tried to use reg exps using remove member with no luck Do you mean bin/remove_members? It doesn't accept regexps, only literal addresses, and it won't accept a '\t' escape - you'd need to give it an actual tab character. You could try bin/remove_members listname '[EMAIL PROTECTED]tab' where tab represents an actual tab character and tried using the method described in the FAQ (3.13. How do I remove a user name or email address with an illegal character in it?) with no luck either. Try bin/withlist -l listname and then at the '' prompts type adr = '[EMAIL PROTECTED]'(this should be the actual address of course) m.removeMember(adr) If that throws an exception, try del m.members[adr] Then in any case type m.Save() in order to save the changed list, and finally type control-D to a prompt to end the interactive session. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- _ | Allan Hansen, Ph.D. | |P.O. Box 2423, Cypress, CA 90630, U.S.A. | | | | Work: Home:| | Phone: +1-714/952-6015 +1-714/875-8870 | | Fax: +1-714/952-6746 | | Email: [EMAIL PROTECTED][EMAIL PROTECTED]| | WWW: http://www.ugs.com http://www.rc.org/ | | | |_Anything is possible with the right tools and right information_| -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Can't Delete Corrupt Subscriber Address
If you maintain people's names on the list, then the same procedure can be used to remove someone based on some string in the name, in case you know the name but not the address (I often get such requests): bin/list_members -f list | grep -e string| wc count check bin/list_members -f list | grep -v -e string list bin/list_members -f list list All this can, of course, be worked into a simple script that also does the count check and that will return 'ambiguous', 'OK', 'not found' as appropriate. Then you should be able to remove someone with just delete_member list some_string_of_characters As for adding to the FAQ, I'll respectfully bow out and leave it to more experienced users to do if they deem the above an appropriate addition. Yours, Allan At 9:42 -0500 2/26/06, Tim wrote: Excellent! Worked like a charm. This should be in the FAQ. Thanks much! Tim At 07:43 AM 2/26/2006, Allan Hansen wrote: How about: bin/list_members -f list|grep -v -e [EMAIL PROTECTED] list bin/sync_members -f list list Allan Tim wrote: We have a subscriber address that has /t on the end of it ([EMAIL PROTECTED]/t) which can only be seen when dumping the lists config file. The subscriber address looks normal ([EMAIL PROTECTED]) when looking for it using any other method (list members, etc). -- _ | Allan Hansen, Ph.D. | |P.O. Box 2423, Cypress, CA 90630, U.S.A. | | | | Work: Home:| | Phone: +1-714/952-6015 +1-714/875-8870 | | Fax: +1-714/952-6746 | | Email: [EMAIL PROTECTED][EMAIL PROTECTED] | | WWW: http://www.ugs.com http://www.hansen-family.us/ | | | |_Anything is possible with the right tools and right information_| -- _ | Allan Hansen, Ph.D. | |P.O. Box 2423, Cypress, CA 90630, U.S.A. | | | | Work: Home:| | Phone: +1-714/952-6015 +1-714/875-8870 | | Fax: +1-714/952-6746 | | Email: [EMAIL PROTECTED][EMAIL PROTECTED]| | WWW: http://www.ugs.com http://www.rc.org/ | | | |_Anything is possible with the right tools and right information_| -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] add_members
Problem: list_members -f -o file list generates a file of members in the following format: name_of_subscriber email_of_subscriber sync_members -f file list takes a file of members in the above format. add_members -r file list crashes with a traceback when given a file in the above format. The crash appears to happen in OldStyleMemberships.py add_members appears to strip all whitespace from the file. Do I have a mixed bag of incompatible scripts or is this the expected behavior at this time. I'm running Mac OS X 10.4.5 The above is not terribly critical, as I can combine list_members and sync_members to do what I otherwise would do with just add_members. Thanks, Allan -- _ | Allan Hansen, Ph.D. | |P.O. Box 2423, Cypress, CA 90630, U.S.A. | | | | Work: Home:| | Phone: +1-714/952-6015 +1-714/875-8870 | | Fax: +1-714/952-6746 | | Email: [EMAIL PROTECTED][EMAIL PROTECTED]| | WWW: http://www.ugs.com http://www.rc.org/ | | | |_Anything is possible with the right tools and right information_| -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] add_members
Thank you, Patrick, but I do need the subscriber names in the lists. Cutting them out would not work. Using bin/list_members, Perl and bin/sync_members lets me do what I need to do. I was just wondering about the apparent inability of add_members to accept names. The help for the command does not indicate a way to input names, and the Python code itself appears to actively reject the notion. Allan At 23:18 -0600 2/26/06, Patrick Bogen wrote: I don't know the answer, but you could always use a bit of perl glue to convert the first format to something add_members will understand more readily... If I knew what the second part was, I'd offer a script to do so. As a stopgap, you can get just a list of addresses by: cat file | cut -d'' -f 2 | cut -d'' -f 1 (Append this with ' file' without quotes if you want to save it back to some file) - Patrick Bogen On 2/26/06, Allan Hansen [EMAIL PROTECTED] wrote: Problem: list_members -f -o file list generates a file of members in the following format: name_of_subscriber email_of_subscriber sync_members -f file list takes a file of members in the above format. add_members -r file list crashes with a traceback when given a file in the above format. The crash appears to happen in OldStyleMemberships.py add_members appears to strip all whitespace from the file. Do I have a mixed bag of incompatible scripts or is this the expected behavior at this time. I'm running Mac OS X 10.4.5 The above is not terribly critical, as I can combine list_members and sync_members to do what I otherwise would do with just add_members. Thanks, Allan -- _ | Allan Hansen, Ph.D. | |P.O. Box 2423, Cypress, CA 90630, U.S.A. | | | | Work: Home:| | Phone: +1-714/952-6015 +1-714/875-8870 | | Fax: +1-714/952-6746 | | Email: [EMAIL PROTECTED][EMAIL PROTECTED]| | WWW: http://www.ugs.com http://www.rc.org/ | | | |_Anything is possible with the right tools and right information_| -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/pdbogen%40gmail.com Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- - Patrick Bogen -- _ | Allan Hansen, Ph.D. | |P.O. Box 2423, Cypress, CA 90630, U.S.A. | | | | Work: Home:| | Phone: +1-714/952-6015 +1-714/875-8870 | | Fax: +1-714/952-6746 | | Email: [EMAIL PROTECTED][EMAIL PROTECTED]| | WWW: http://www.ugs.com http://www.rc.org/ | | | |_Anything is possible with the right tools and right information_| -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Moderator permissions or rights
Thank you, Mark, for you response and the incredible amount of support you provin on this list. In this case my own preference is also not to give the list moderator full admin access but to allow subscribes/unsubscribes. I thus will have to do it with homebrew scripts that provide just the right access. Allan At 22:41 -0800 2/18/06, Mark Sapiro wrote: Allan Hansen wrote: I have this same requirement. I was thinking of writing some CGI scripts that take commands from the moderator and then apply them to the lists via the mailman command line interface. My own reason for this is that some moderators are handling many lists, and going into each one with a password is taking too long. Instead, I'll let them in with a single password, and then have a dialog that lets them subscribe/unsubscribe/change address for multiple people/lists at a time. Your approach is certainly viable, but here's another idea that may help in a case like yours. If the moderator uses a browser like Firefox for example that can remember passwords for a web site and can open a bookmark folder in tabs, she can create a bookmark folder containing links to the admindb pages for all the lists. Then if she selects the folder-open in tabs, this opens all the lists admindb pages at once, each in its own tab. Further if the password is saved and automatically fill and submit selected, the login is automatic. The one potential drawback is it generally requires all the moderator passwords for her lists to be the same, as passwords are remembered by site, not by page, at least in Firefox. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- _ | Allan Hansen, Ph.D. | |P.O. Box 2423, Cypress, CA 90630, U.S.A. | | | | Work: Home:| | Phone: +1-714/952-6015 +1-714/875-8870 | | Fax: +1-714/952-6746 | | Email: [EMAIL PROTECTED][EMAIL PROTECTED]| | WWW: http://www.ugs.com http://www.rc.org/ | | | |_Anything is possible with the right tools and right information_| -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
