On 08/26/2016 05:24 PM, The Mailing List Server Admin wrote:
>
> I ended up having the same error happen. Looking at the Mailman logs,
> I can't see any difference before or after my submission. In the
> HTTPD logs, I see:
>
>>> [Fri Aug 26 19:59:23 2016] [warn] [client 132.177.215.132]
Dear Mailman Cognoscenti,
I'm helping one of my list owners send out 5K plus invitations to
students to subscribe to his mailing list. Our current configuration:
Mailman v2.1.20
RHEL v5.11
Semdmail v8.13.8
Apache v2.2.3
Since this was the first time doing this, I suggested
On Aug 26, 2016, at 11:53 AM, Mark Sapiro wrote:
>Still, most users considering MM 3 would probably do best by waiting for
>the official MM 3.1 release.
Which I am hoping will happen in the latter half of September, early October.
Although HyperKitty isn't tracking milestones yet, core and
On 08/25/2016 12:28 PM, Matt Morgan wrote:
>
> I decided to set it up to clean out the cruft fast, and then I'd temper it
> back a little. So I set it up like this:
>
> bounce_processing: yes
> bounce_score_threshold: 2.0
> bounce_info_stale_after: 63
> bounce_you_are_disabled_warnings: 0
>
On 08/26/2016 09:17 AM, Stephen J. Turnbull wrote:
>
> Also, Postorius (and possibly HyperKitty) are going to have to undergo
> substantial upgrades in the near future, because they currently use
> Mozilla Persona for authentication. We've decided what to do about
> that and the work is underway
I recently took over a lot of pre-existing mailman lists for a new client.
At least one list was pretty messy. They had automatic bounce processing
turned on, but the threshold was high, and reset time was shorter than the
typical length of times between postings (it's an announce-only list that
Russ Housley writes:
> I am interested in the internationalization capabilities of Mailman
> 3, but I thought that it was not ready for production use. In that
> not right?
That depends on your use case. The basic facilities are quite robust
and in production use by several organizations.
> I am interested in hiring a consultant to install Mailman 3 on a Dreamhost
> server and migrate a bunch of existing Mailman 2.1.17 mailing lists to
> Mailman 3. If you are interested, or you know someone that might be able to
> provide this service, please contact me off list.
I am
I am interested in hiring a consultant to install Mailman 3
on a Dreamhost server and migrate a bunch of existing
Mailman 2.1.17 mailing lists to Mailman 3. If you are
interested, or you know someone that might be able to
provide this service, please contact me off list.
Thanks
Jason Glazer
