In a message of Thu, 17 Apr 2014 15:54:19 +0200, Laura Creighton writes:
>In a message of Thu, 17 Apr 2014 05:41:15 -0700, Mark Sapiro writes:
>>The issue is msg_footer is assumed to be in the character set of the
>>list's language, us-ascii by default for English. I don't think Mailman
>>does the right thing in this case.
>>From my perspective, the problem is that by having these things
>defined in mm_cfg.py, all mailman administrators are stuck with
>whatever decisions their mailman host made for whatever language
>they chose as the default language for their list. But you and I
>could quite easily both want English(USA) as the default language
>for our lists, but you also want us-ascii while I want utf-8. The
>way things stand now, we cannot both use the same mailman host, and
>both get what we want, correct?
>Now that my problem has gone from 'getting the EP footers to work' to
>'understanding what exactly is going on here'. And right now I do not
>see why the charset for the lists' language has to be hard coded in
>mm_cfg.py, nor why there has to be exactly one value for any given language
>which mailman supports.
>Thank you for your patience,
>Still trying to understand here,
Sorry about this note -- mail is arriving in an odd order here. The mail
where you explained this perfectly arrived after your other mail, so I
was still confused when I wrote this note.
I've searched the list and found enough related posts that this looks
like it should be simple just reinstall, hopefully with the original
PREFIX settings and probably diff the old and new mm_cfg.py files just
to catch all the changes/new features/etc.
I have visual problems so my eyes often go fuzzy if I do too much
computer work at one time.
However I find there may be a complication from a problem made from the
initial install of 2.1.14.
The initial install was done as user mailman, group mailman. When I
reboot the server it seems to set mailman to user list, group list and I
have to go an fix permissions and ownership back to mailman:mailman.
If I install 2.1.17 over 2.1.14 and use list:list for user:group will
this fix the 'problem'? Are there any gotchas I should be aware of?
I've found that at least with the current install (not done by me) that
fixing all the bin/checkperm problems will actually break mailman on the
If relevant we are using postfix.
I was thinking of upgrading to MM3, but I don't see any final release
version and no software to upgrade from 2.1.x to 3.x.
Thanks in advance.
I am trying to understand how charset encoding works, and I get the
distinct idea that I must be missing one small, vital piece of
Background: The problem arose as follows:
Somebody changed the footer of the EuroPython Mailing list which is hosted
at python.org to be:
EuroPython 2014 \x96 Berlin, 21th\x9627th July
Note the two \x96 s. The intent was almost certainly to have this string
interpreted by the windows-1252 charset, where \x96 means a en dash. But
the Europython mailing list is configured so that its messages come out
Content-Type: text/plain; charset="us-ascii"
Since \x96 is an unrecognised character in us-ascii, my mailer complained
bitterly every time I read an EP message. Being a list admin, this
bothered me, and I thought it would be my job to fix things.
I thought I would change the charset to utf-8. After all, most European
languages do not fit into "us-ascii" in any event. What if the conference
had been held in my home town of Göteborg, for instance?
But unless I have overlooked something, there is no way to make a charset
change on a per-list basis through the mailman administrative interface.
Instead you have to edit mm_cfg.py
Even if I had root access on python.org, I wouldn't really want to inflict
utf-8 on everybody else just because it makes things more convenient for
the EuroPython mailing list.
But needing to edit mm_cfg.py strikes me as a very odd design choice, odd
enough that I figure either a) this isn't so and I have overlooked something,
or b) it absolutely must be done this way for a reason I do not understand.
Can somebody please explain this?
Thank you very much,
Isn't this DMARC issue a bellwether for the end of email lists as we know them? It seems to me that the means of production (the internet backbone, the mail servers, etc) are now owned by Big Media (Comcast, Walt Disney, CBS, Viacom, Time Warner) and it is in their interest to make sure they can sell as much advertising as possible to the cattle.
People who operate Mailman servers (you guys) are just the little guys who are helping people facilitate non-advertisable communication between the masses.
This seems like a poignant example of the fiction of the distributed network. The last 15 years of the internet history (indeed, the first 15 years of internet history) has been the story of the consolidation of control into the hands of the few, not the open and egalitarian peer-to-peer network utopia that the internet was touted to be in populist culture.
If I really have something to say to someone, I write it using ink and paper, put it in an envelope, put a stamp on it and drop it into an actual post box. This way I know the NSA can't see it.
We are using the services from ultrahost.us There is no response from
Ultrahost team in spite of our several tickets loged. Is anyone
confronting the similar issue with them?
I think now we may again have to change the service provider where we
can get unlimited traffic with mailman as per the requirement.
Do we have any hosting provider in India or Asia region? IN US we do
face gap in communication when it comes to get the solution.
These days our list is out of function due to their server updation and all.
[Using Mailman 2.1.14 on a hosted service]
I have a large list (7600 addresses), and when I search for a list of users of a popular domain (e.g. yahoo.com), I of course get a large result set back - sometimes more than 50 beginning with a particular letter. On those addresses with more than 50 starting with a common letter, they are of course split up, but when I click on another of the sub-letter lists, the “Find” string disappears in the search results and I’m back to a subset of the whole list, not the searched list. Is there any way around this? Thanks much.
Don’t tweet our secrets
I used the following when setting up Mailman 2.14:
./configure --prefix=ZZZ/mailman --with-mail-gid=daemon --with-cgi-gid=www --with-username=ZZZ --with-groupname=users --with-python=ZZZ/bin/python
To upgrade PHP from 5.2 to 5.3 the website hosts have to enable suexec (I don't quite understand this but bear with me!) which breaks Mailman, I think because it runs as a different user to before.
Can I reconfigure Mailman using this?
./configure --prefix=ZZZ/mailman --with-mail-gid=daemon --with-cgi-gid=users --with-username=ZZZ --with-groupname=users --with-python=ZZZ/bin/python
This is the with-cgi-gid setting that the hosting people suggest, but I would be grateful for confirmation from someone on this expert list.
What else would I need to do?
Thanks very much in anticipation.
This morning at 9 AM CDT one of FMP's lists here saw another mass
unsubscription event - 51 subscribers with the usual ESP addresses:
hotmail, yahoo, comcast, bellsouth, etc. Checking the list archive,
there have been no posts to the list from yahoo.com since the 13th.
Someone else must be publishing a DMARC p=reject record. Any insight on
I've told the list admins that putting all yahoo.com subscribers on
moderation so that they can read list traffic but not post would put a
band-aid on the problem, but apparently this isn't the case.
Is there a delay inherent in Mailman's bounce processing that would
cause the unsubscriptions today rather than on the 13th when the last
yahoo.com post was received by the list? Posts that have come to the
list today are from:
Lindsay Haisley | "Everything works if you let it"
FMP Computer Services |
512-259-1190 | --- The Roadie