On Apr 08, 2013, at 12:10 PM, Chris Cargile wrote:
>..what if we could invite/reach out to administrators who've chosen to host
>their apache project-lists using 'mod_mbox approach' to consider MM3 as a
>replacement solution?
Please note too that MM3 supports an IArchiver interface, for which mul
On Apr 08, 2013, at 11:00 AM, Stephen J. Turnbull wrote:
>Ooh, tasty! How about a Mailman Raspberry Pi?
>
>Seriously, Barry, ya think it's possible?
>
>This would solve the environment problem for students! Dunno if it's
>strictly better than an AWS instance, but I bet many would prefer it.
It'
On Apr 08, 2013, at 04:07 PM, Surya Kasturi wrote:
>Since no one had so far configured mailman on windows, I guess, I can try
>it (not now but.. later on). Why not we build an executable for windows
>(.exe) for users to install? This could take sometime to port and solve
>conflicts.. but at the en
On Apr 08, 2013, at 07:02 AM, Richard Wackerbarth wrote:
>Although we would like for MM3 to run on Python 3, I don't think that all of
>our dependency libraries are ready for that yet. I am running MM under
>Python 2.7
We're down to two dependencies: restish and storm. I took a crack at restish
On Apr 08, 2013, at 01:59 PM, Richard Wackerbarth wrote:
>Well, the Django ORM does run on python 3. So, even if it isn't "the best",
>it is a possibility.
Is it usable outside of Django?
-Barry
signature.asc
Description: PGP signature
___
Mailman-De
On Apr 10, 2013, at 11:05 AM, Elias Assarsson wrote:
>I do not know if it is a good idea but I am thinking that using Augeas
>http://augeas.net might be a way to handle the migration of configuration
>from one format to another.
Definitely investigate these tools, although my suspicion is that th
On Apr 11, 2013, at 02:22 PM, Elias Assarsson wrote:
>> * MM2's configuration file is a Python file which really must be imported
>> in order to get a valid set of values. MM3's configuration file is a stack
>> of .ini-style files.
>I am trying to find and understand the configuration files so t
On Apr 11, 2013, at 07:02 PM, Richard Wackerbarth wrote:
>I encourage any GSoC candidates to actively discuss design issues on this
>list. Many aspects of MM3 remain only partially defined and still require
>design in addition to the coding that will follow. Although some might expect
>the mentors
On Apr 12, 2013, at 01:44 AM, Stephen J. Turnbull wrote:
>A couple of people have mentioned anti-spam, and it's a frequently
>requested feature. Nevertheless, I don't think we should spend Google
>money and mentor time on it.
>From the core's perspective, I tend to agree that there is some inter
On Apr 12, 2013, at 08:28 AM, Patrick Ben Koetter wrote:
>I think it would be real nice to have a MILTER interface at LMTP server level
>to allow mail modification as required. Mailman runs in large environments and
>all the 'large organizations' I have worked asked my team and me to customize
>ho
On Apr 11, 2013, at 01:52 PM, Terri Oda wrote:
>Writing individual pipelines may be trivial, but making a user interface for
>managing said pipelines is non-trivial. Right now, our pipeline management
>interface is "there's a text box in postorius that lets you choose a
>pipeline. It's not even
On Apr 12, 2013, at 12:50 PM, Stephen J. Turnbull wrote:
>... is *convenient access to logs via the admin interface*.
+1. Can you add that to the wiki page?
-Barry
___
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.or
On Apr 12, 2013, at 01:28 PM, Mark Sapiro wrote:
>Does anyone know?
Probably not .
-Barry
___
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/A
On Apr 15, 2013, at 12:04 PM, Elias Assarsson wrote:
>I have had a look through bin/withlist, mm_cfg.py and Defaults.py to get a
>feel for the format of the configuration. Why is bin/withlist relevant for
>configuration migration? In that it is way to learn about configuration?
Yes.
>I guess con
On Apr 15, 2013, at 01:05 PM, Sreyanth wrote:
>Just hide the boilerplate in the email, giving a link to click. When clicked,
>use js to unhide the boilerplate. This would not anyhow require separate
>storage. Suggest me something if this is bad!
A problem you would have to work out with this
On Apr 14, 2013, at 12:49 AM, Sneha Priscilla wrote:
>Why don't you try re-branching the repository again and start over? Plus
>buildout instruction needs sudo access as far as I know, so make sure
>you're doing that.
You shouldn't need root to do a buildout and run the tests. You can probably
e
On Apr 14, 2013, at 09:34 AM, Avik Pal wrote:
>actually I think the following is behind all these...
>
>*Download error on http://ish.io/projects/show/restish: [Errno -2] Name or
>service not known -- Some packages may not be found!*
Buildout should be able to grab restish from PyPI:
https://pyp
On Apr 15, 2013, at 08:19 PM, Karl-Aksel Puulmann wrote:
>Sadly I haven't heard anything about those merge requests I made a week ago.
Yes, sorry, I've been swamped.
-Barry
___
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.p
On Apr 16, 2013, at 06:49 PM, Stephen J. Turnbull wrote:
>In more detail, here's something I drafted at the Mailman Sprint.
>I can say that Terri got a kick out of it, but remember, it's not
>official, it's just my opinion. (I really should put it on the wiki,
>but I'm not sure where or even how
On Apr 17, 2013, at 12:43 AM, Avik Pal wrote:
>also I would like to propose an idea of my own. Many of us set the preference
>in mailman to get all the emails of a day batched together, but sometimes
>this means we miss important mails(though we get it at the end of the day but
>we miss the moment
On Apr 18, 2013, at 10:32 PM, Patrick Ben Koetter wrote:
>And that handler would be - excuse my ignorance I don't program - a Python
>function to handle a Python program? Could the handler pass a message over to
>e.g. SpamAssassin (Perl) or openDKIM (c code) or any other non Python program
>withou
On Apr 18, 2013, at 01:10 PM, Chris Cargile wrote:
>The cause in both cases seems to stem from failing at the SMTPLayer, where
>it shows: [Error98] Address already in use.
This almost always means that some runner process from a previous test didn't
exit. I've tried to bulletproof the process ma
On Apr 18, 2013, at 01:56 PM, Rahul Gaur wrote:
>Talking about authentication, django-restframework has a wrapper for OAuth2
>out of the box, but I will have to check how to use non form data sources.
I keep hearing terrible things about OAuth2.
OAuth1 is nice and simple and there are plenty of
On Apr 19, 2013, at 02:40 AM, Patrick Ben Koetter wrote:
>My original point was that we should use MILTERs because we shouldn't reinvent
>what already has been implemented very well and we shouldn't come up with a
>proprietary solution, because that will make it harder to expand Mailman and
>also
Terri, thanks for kicking off this discussion!
On Apr 18, 2013, at 01:34 PM, Terri Oda wrote:
>On 13-04-18 2:28 AM, Stephen J. Turnbull wrote:
>> Main comment: Sounds like LDAP to me.
>Actually, this is a really important comment. I was sort of wondering that
>too when I started writing the des
On Apr 19, 2013, at 10:28 AM, Stephen J. Turnbull wrote:
>Barry Warsaw writes:
>
> > I still think this wouldn't be a handler, but a rule.
>
>Is this distinction implemented and enforced by the API?
It is. There are two distinct interfaces, IHandler and IRule, with diff
On Apr 19, 2013, at 11:48 AM, Ian Eiloart wrote:
>I think Mailman supports SMTP/LMTP calls to discover whether a sender is
>permitted to post to a list, doesn't it?
MM3's LMTP server currently only does a limited sanity check on the messages.
E.g. does the To: field name an existing mailing list[
On Apr 19, 2013, at 07:18 AM, Richard Wackerbarth wrote:
>Are you starting to come around to the concept that I have been advocating
>for a long time?
It's always been part of my thinking, and it's most evident in the use of
interfaces internally. Time will tell whether we've accomplished that o
My main suggestion for now is to be very careful and not over-engineer the
user database component. Provide something minimal that fits the bill and has
a minimum of security, e.g. basic-auth over localhost, and possibly https.
For now, I think it would be fine as a Django app if that makes thing
On Apr 18, 2013, at 10:26 AM, Terri Oda wrote:
>I thinks case, case we have to be *much* more conservative about
>dependencies. I think Django would be right out as a dependency for Mailman
>core, for example. Plus, we're going to have to care a lot more about speed
>and all.
Definitely. Howev
On Apr 18, 2013, at 09:39 PM, Florian Fuchs wrote:
>I think in this case it makes sense to spend a more time on the API as
>seen from the outside (urls, methods, json responses) than the actual
>implementation. If the API is good, it's totally acceptable if the
>underlying implementation will be r
On Apr 19, 2013, at 10:22 AM, Stephen J. Turnbull wrote:
> > 2) use some other authentication method.
>
>What's wrong with HTTPS + Basic Auth?
Oh, one thing about HTTPS + Basic Auth. Right now, MM3 core has only one
admin user and password for access to its REST API. So it can't be used to
auth
On Apr 24, 2013, at 01:54 AM, Stephen J. Turnbull wrote:
>Chris Cargile writes:
>
> > test_not_enough_parameters
> > (mailman.rest.tests.test_users.TestLogin)
>
>Either the test or the code is borked. Last I heard (at the sprint),
>we didn't know why. Comment out that test so that the rest of th
On Apr 22, 2013, at 06:24 AM, Richard Wackerbarth wrote:
>I echo Stephen's comments. Although I try to lurk on the #mailman channel
>most of the time, being half a world away from him, I am most likely to be at
>the keyboard after 1100 UTC and before 0200 UTC.
We chatted on #mailman a few days ag
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Apr 26, 2013, at 02:09 PM, Stefan Schlott wrote:
>- disk queue. I don't remember if mailman persists received (but not
>yet sent) mails on disk.
>
>Addressing the last point, you can either choose to decrypt the mail
>in a later stage, or (if thi
On May 02, 2013, at 04:03 PM, Spamm Azz wrote:
>I wrote a function in C language that customizes an email body. My target is
>to integrate this function inside mailman 3 to customize the email for each
>recipient. To manage an input email is possible inserting an handler, but I
>don't know how t
On May 08, 2013, at 10:31 AM, Richard Wackerbarth wrote:
>I agree with Steve. One of the advantages of Django is its "mix and match"
>capability. Actually, I see two possible apps. One would integrate with
>HK. The other would be simpler, just providing a posting mechanism that
>provides authenti
On May 07, 2013, at 06:58 PM, Richard Wackerbarth wrote:
>I was comparing what a consumer of the Postorius interface might like to see
>that is not just a proxy forwarding the MM-core interface.
>
>As an example, rather than all of the lists, just those lists for which the
>represented user is the
On May 13, 2013, at 10:52 PM, varun sharma wrote:
>1. Suspend emails in vacation and post from multiple email ids:
>IMember interface present in interfaces/member.py is already providing the
>delivery_status enum in _client module via rest api but the user.save() is
>currently not functional, so t
On May 17, 2013, at 04:58 PM, Richard Wackerbarth wrote:
>Would it be easier if we just treated owners and moderators as a couple of
>additional mailing lists.
>
>In other words, for list x...@example.com, we also have virtual lists
>@example.com and @example.com Where the list
>names are accessib
On May 19, 2013, at 11:26 AM, varun sharma wrote:
>I think the owner or moderators also should be allowed to use the in vacation
>suspension of mails from the mailing lists they moderate or own, given all
>the administrative tasks that need their attention must be added to their
>ToDo queue.
One
On May 19, 2013, at 10:08 PM, varun sharma wrote:
>2. The second thing is some moderators might be interested in knowing
>the administrative changes done in their absence. So they should
>receive a summary of the tasks done(eg. users added) in their absence
>once they come back from vacation.This
On May 20, 2013, at 11:31 AM, varun sharma wrote:
>So, I think the overlapping vacation may be handled in two ways:
>1. Follow up the procedure as written above , i.e: If there are multiple
>moderators going on vacation for same span of time, then the tasks will
>remain pending in their ToDo list
On May 20, 2013, at 06:39 AM, Richard Wackerbarth wrote:
>It is easy to say "He will receive an email about the tasks done in his
>absence". However, how do you propose to compose that email? Where and how
>is the information used to construct the email stored while the moderator is
>on vacation.
Stephen's already given a very good response, so I'll just add a few more
thoughts.
On Jun 15, 2013, at 11:12 AM, Abhilash Raj wrote:
>* How to ensure the keys belong the email it says it does?
>
> One method proposed for this was to send a confirmation email to the email
> address, but what if
On Jun 16, 2013, at 01:48 AM, Stephen J. Turnbull wrote:
> > * the message is queued in incoming queue
> > * the incoming runner wakes up, finds the message and calls a few
> > functions to verify the signature of the message(assuming the function
> > already has public key of the user from so
On Jun 16, 2013, at 03:42 PM, Stephen J. Turnbull wrote:
>Barry Warsaw writes:
>
> > I know this is a little backwards, but it's probably the best match
> > for the current rule/chain model.
>
>I have a smallish problem with this model. Specifically, for a list
>w
On Jun 15, 2013, at 09:09 PM, Paul Boddie wrote:
>It's been a couple of months or so since my last update, and I finally got
>round to doing some more work on the content migration from Confluence to
>MoinMoin.
>
>As always, the results can be found here:
>
>http://mmwiki.boddie.org.uk/
It's lo
On Jun 16, 2013, at 08:17 PM, Paul Boddie wrote:
>> * Once we migrate we can probably get rid of the spaces. I think that's a
>> Confluence-ism that doesn't translate as well to Moin. That should be
>> easy enough to do manually, right?
>
>The only apparent purpose of the spaces is to separate
On Jun 17, 2013, at 06:57 PM, Paul Boddie wrote:
>I'm not sure these tiny links are in the Confluence dump, but if there's an
>algorithm to generate them, then maybe we can provide a similar mapping
>resource.
Just as a general feature request, it would be cool if Moin supported tiny
urls. I u
On May 30, 2013, at 06:37 PM, Richard Wackerbarth wrote:
>OK. Then a "roster" represents the distribution list for a "feed" of outgoing
>messages. The "mailinglist" represents the reception point(s) for the
>incoming messages and the directives for handling the processing of those
>messages.
>
>T
On May 31, 2013, at 04:45 PM, Stephen J. Turnbull wrote:
>Barry Warsaw writes:
>
> > Here's where it gets interesting. Rosters are not modeled as rows
> > in a table, they are modeled as queries. [...]
> >
> > One of the use cases for rosters that I've al
I just saw this come across python-announce. Would this at all be helpful for
Postorius or Hyperkitty?
http://peterhudec.github.io/authomatic/index.html
http://peterhudec.github.io/authomatic/examples/django-simple.html
-Barry
signature.asc
Description: PGP signature
__
Hi Nghia,
On Jun 25, 2013, at 02:07 AM, Nghia Vu Truong wrote:
>Hi everyone, I am currently doing a project of expanding Mailman features.
>However, I am a newbie, so I want to understand the structure of Mailman
>coding files. Could any one know about this please help me, or please let me
>know
All great questions. Let me just add this.
On Jun 28, 2013, at 01:03 PM, Stephen J. Turnbull wrote:
>There does need to be a way for list owners to take complete control of key
>management, and there does need to be convenience in management. I think
>that the "key signed by list-owner's list-k
On Jun 29, 2013, at 10:33 PM, Chris Cargile wrote:
>FWIW, I'd also like very much if anyone could provide a few lines recap of
>the activity on the ModernArchiving topic under "initiatives and proposals"
>as I feel my thoughts on searching/archiving tie into the
>objectives/requirements listed the
On Jul 02, 2013, at 01:04 PM, Stephen J. Turnbull wrote:
>No, in Mailman 3 it is not, and cannot be, internal to OpenPGP because
>addresses are *not* Users. There is a many-to-one (address-to-User)
>mapping (I hope; if it's many-to-many, we can probably dodge that
>bullet by allowing sets of User
On Jul 02, 2013, at 12:44 AM, Patrick Ben Koetter wrote:
>Before we take out to write code, I would like to ask mailman-developers how
>it should be done to fit best into Mailman's architecture. Here are the DMARC
>features that should go into Mailman 3:
>
>- don't allow email that comes from a do
On Jul 06, 2013, at 11:02 PM, Murray S. Kucherawy wrote:
>I'm all for experimentation and being adaptive as new things come along,
>and I'm obviously supportive of the DMARC effort. That said, I hope that
>these are going to be configurable options, defaulted "off" for backward
>compatibility. T
On Jul 08, 2013, at 02:26 AM, Franck Martin wrote:
>2) mailman has one option: reply to poster or reply to list. I think the
>first one is default, but as mentioned, many list admins, enable reply to
>list.
Actually, Reply-To munging is a bit more complicated.
There is a boolean flag that indica
On Jul 06, 2013, at 09:00 PM, Franck Martin wrote:
>Similarly, I'm interested to offer the option to list administrators to
>transition to a behavior that makes the lists safe/working/compatible with
>DMARC. As Patrick explained, there are about 3 possibilities, while I'm
>interested more in some
On Jul 11, 2013, at 03:23 AM, Stephen J. Turnbull wrote:
>Barry Warsaw writes:
>
> > For #1 you would have a rule that can answer the question of DMARC
> > disposition. Rules output binary results,
>
>This is somewhat problematic. DMARC results are potentially
>triva
On Jul 12, 2013, at 11:56 AM, Stephen J. Turnbull wrote:
> > Yep. There is some limited ability to do additional checking at LMTP time,
> > but this isn't pluggable currently.
>
>Does LMTP provide the necessary ability to reject?
Not reject in the Mailman sense of sending a bounce message (possi
On Jul 12, 2013, at 12:54 PM, Mark Sapiro wrote:
>On 07/12/2013 11:13 AM, Rob Lingelbach wrote:
>> As a long-time user of Mailman, running a list of 2000+ subscribers, thank
>> you Mark for all your work. Is there any pertinent
>> news regarding a new major release of Mailman?
>
>Work on Mailm
On Jul 14, 2013, at 03:52 PM, Terri Oda wrote:
>I've started a new "things left to do before Mailman 3 releases" list over at
>http://wiki.list.org/display/DEV/Mailman+3.0
Thanks Terri. I'll spend some time pouring over that page w.r.t. the core,
updating it, removing old to-do items, and fillin
On Jul 15, 2013, at 11:28 PM, Stephen J. Turnbull wrote:
>There are no deployments I know of, although Barry may. (I'm leaving
>out people who are playing with betas; by "deployment" I mean
>"supporting real work".) The GSoC mentors and students are discussing
>setting one up that we can experim
On Jul 15, 2013, at 01:21 PM, Stephen J. Turnbull wrote:
>The only thing I can think of offhand for core is Exim support.
>(Sendmail support, I suppose, but nobody I know uses Sendmail, and I
>can't do it. Exim on the other hand is on my personal list.)
I'd very much love to have Exim and Sendma
On Jul 19, 2013, at 01:15 AM, Paul Boddie wrote:
>Once again, I've had some time to push the wiki migration along. As always,
>the results can be found here:
>
>http://mmwiki.boddie.org.uk/
>
>I've updated the archived content to that of 16th July, so the translated
>content should reflect the e
On Jul 26, 2013, at 02:05 PM, Mark Sapiro wrote:
>> I can tell you though that my motivation to garden the current wiki is
>> pretty low, and I think I'd be more motivated to clean it up after the Moin
>> migration. If the other wiki editors feel the same way, then we should
>> seize the opportun
On Jul 26, 2013, at 02:55 PM, Mark Sapiro wrote:
>Sounds good. Re: timing, I am off line much of now through Aug 30, so
>for me at least, 'Test, test, test' shouldn't begin before September.
Works for me too. What I'll do in the meantime is get the ball rolling with
infrastructure, try to get an
On Jul 31, 2013, at 06:17 PM, Daniel Kahn Gillmor wrote:
>I'm excited to see this work, Abhilash!
Me too!
>On 07/31/2013 02:43 AM, Abhilash Raj wrote:
>> * Signature verification using `python-gnupg` was a PITA to me for
>> sometime. The way it accepts the string and signature for detached
>> si
On Aug 02, 2013, at 05:49 PM, Abhilash Raj wrote:
>Now as the signing part is almost done except for to-be-able-to-select
>the key for signing(now python-gnupg signs using the first found key in
>the secret keyring) we need the proper infrastructure for the key
>management. Where will the public k
I agree with everything written elsewhere by Steve and Richard.
On Aug 14, 2013, at 05:35 PM, Stephen J. Turnbull wrote:
>[1] Has anybody else noticed that both gpg's UI and its documentation
>seem designed to make it as hard to use as possible?
Sadly, I think this is one of the biggest reasons
On Aug 18, 2013, at 04:43 PM, Abhilash Raj wrote:
>I had a few doubts regarding the project, I din't see any reply on
>mm-dev so I mailed separately. Firstly what address should be used to
>create the keys for the lists? I was of the opinion that list' posting
>address should be used like 'mailman
On Aug 20, 2013, at 11:52 AM, Stephen 'Humble is my middle name' Turnbull wrote:
Actually, it seems like "Humble is my middle name" is your middle name. :)
>I agree now. The point made in an earlier post is that in most cases
>people will use their keyrings to store keys, and addresses are the
>
On Aug 16, 2013, at 03:13 PM, Abhilash Raj wrote:
>> > Also one more thing while running tests i noticed many other tests are
>> > breaking as initially a simple message could pass though
>> > "default-posting-chain" but now we need a multipart/signed message. So
>> > should I worry about chan
On Aug 16, 2013, at 03:12 PM, Abhilash Raj wrote:
>2) RSA or DSA keys?
>
>DSA can only be used for signing but is faster than RSA, although for
>now our scope is limited to signing later on we "will" add encryption so
>I think we should stick to RSA?
RSA probably. I don't think the difference in
On Aug 23, 2013, at 01:51 AM, Abhilash Raj wrote:
>I actually don't have the remember the count but some 10 or so doctests
>were failing.
If possible, you can just ignore these for now. Let's take a more detailed
look when I land the nose2-based tests in trunk.
-Barry
__
On Aug 21, 2013, at 12:42 PM, Daniel Kahn Gillmor wrote:
>larsi is also the mad genius responsible for most of gmane.org, for
>which many of us are very grateful :)
I hope at some point we'll have a plugin to allow for direct integration with
Gmane (e.g. register-this-list, an IArchiver to feed i
Hello everyone,
I want to mention a few things related to wiki.list.org.
First and most immediately, our currently wiki hosting provider Contegix, is
in the process of a major infrastructure update which will cause some downtime
for wiki.list.org. Contegix has been hosting our wiki gratis for se
Hey everyone,
A while ago I mentioned that I was trying to get rid of zc.buildout to build
Mailman 3 and zope.testing to test it. This work is now complete and pushed
to trunk. My thanks to the awesome nose2 project and Jason Pellerin for his
help in answering my questions along the way.
Update
On Sep 12, 2013, at 10:44 PM, Franck Martin wrote:
>Unfortunately some list admins cannot edit mm_cfg.py (like CPANEL type
>install), therefore it would be nice to remove ALLOW_AUTHOR_IS_LIST or set it
>to Yes by default to let the list admin decide how he/she wants the list to
>behave. Otherwise
On Sep 14, 2013, at 04:49 AM, Stephen J. Turnbull wrote:
>I have no idea what MUAs would do with that, though. :-(
Me neither, but experience indicates it wouldn't be pretty. :/
-Barry
___
Mailman-Developers mailing list
Mailman-Developers@python.org
h
On Sep 15, 2013, at 08:24 AM, Mark Sapiro wrote:
>Because the issue remains controversial, I will soon release 2.1.16
>final with the feature disabled by default, and will consider the
>message encapsulation approach or other possibilities based on
>experience with 2.1.16 for a 2.1.17 release perh
On Sep 20, 2013, at 12:46 PM, Aurelien Bompard wrote:
>What do you think? Bad timing? Any existing work I'm missing?
I think it's a *great* idea.
No, perfect timing.
Not that I know of! :)
What we've said in the past is that we weren't going to promise conversion
scripts from 2.1 to 3.0, partl
On Sep 18, 2013, at 05:04 PM, Stephen J. Turnbull wrote:
>I don't read German, but I don't see anything that looks like data,
>nor is there room for "analysis." Nor does the blog by Patrick
>Koettner referenced therein. (The Google translations confirm that.)
>Please show us something that looks
On Oct 21, 2013, at 03:03 PM, Ian Eiloart wrote:
>Presumably, with some lists on 2.1, and others on 3.0.
That's the goal. I think it's really important to allow sysadmins to migrate
lists in phases so they can gain confidence and experience with the new system
without committing to it whole hog.
On Oct 29, 2013, at 05:35 PM, Terri Oda wrote:
>1. Need a Postorius interface for associating multiple email addresses with a
>single account. This is probably going to require either an email
>verification, so we might want to have that as part Mailman Core rather than
>doing it directly in Post
On Oct 30, 2013, at 02:49 PM, Aurélien Bompard wrote:
>I've also created a branch and a pull request in Launchpad with lots of
>modifications to the import script.
I'm slowly working my way through this branch. I'll have some time this
weekend to hopefully finish it up.
Cheers,
-Barry
signatu
On Oct 30, 2013, at 05:52 PM, Stephen J. Turnbull wrote:
>Of course it will be MTA-specific. I haven't done it on Postfix, but
>for Exim you just add a Mailman3 router and transport ahead of the
>Mailman2 router (I've already submitted the docs for that -- they're
>very generic -- don't know if B
On Nov 02, 2013, at 04:06 PM, Stephen J. Turnbull wrote:
> > So this feature in particular, if Postorius can do all the
> > necessary confirmations, I can much more easily provide an API that
> > Postorius can call to associate an email address with a given user.
>
>I'm getting that ol' sinking fe
On Nov 07, 2013, at 02:50 PM, Colin Fleming wrote:
>I'm interested in using Mailman to set up a mailing list for my product.
>I'd like to have it be fully integrated into my website, so I'm planning to
>use Mailman 3 and the REST API. I've checked out mailman.client and poked
>around, and also loo
On Nov 09, 2013, at 06:10 PM, Colin Fleming wrote:
>Thanks for the comments, Steve - can you clarify what you mean by a
>"write-only API"? As far as I can tell I could use that to insert messages
>that Mailman now considers "posted to the list" into my own DBMS and then
>present them however I lik
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Nov 13, 2013, at 02:39 PM, Florian Fuchs wrote:
>What we could do though (possibly as part of the migration routine) is
>to auto-generate rewrite rules for major web servers like
>Apache/nginx/... redirecting MM2-style URL requests to the new one
On Dec 02, 2013, at 03:42 PM, nicolas wrote:
>Solved, setting up environment MAILMAN_CONFIG_FILE fixed that point
That will work, although it should *also* work to pass `-C ` to `mailman
start`. A custom configuration file should get passed down to all the
subprocess runners.
-Barry
___
Does anybody here have experience with Pecan?
http://pecanpy.org/index.html
-Barry
signature.asc
Description: PGP signature
___
Mailman-Developers mailing list
Mailman-Developers@python.org
https://mail.python.org/mailman/listinfo/mailman-developers
M
On Feb 02, 2014, at 04:17 PM, Tim Marx wrote:
>I got Mailman running without errors but I can't change the IP address the
>REST server binds to. I would like to bind the REST server for development to
>the address 0.0.0.0 to access it from outside of the VirtualBox with Port
>Mapping.
0.0.0.0 is
On Feb 04, 2014, at 02:49 PM, Stephen J. Turnbull wrote:
>(WSGI is not a webserver, it is an interface between Python and a real
>webserver)
Right, but the wsgiref stdlib module does provide a WSGI-compliant HTTP
server, which is what Mailman's REST runner uses currently.
-Barry
signature.asc
On Feb 06, 2014, at 01:49 PM, Geoff Shang wrote:
>On Thu, 6 Feb 2014, Kevin Ratnasekera wrote:
>
>> While i create new list with mailman rest api i receive this error,
>> sh: 1: /usr/sbin/postmap: not found
>> sh: 1: /usr/sbin/postmap: not found
>
>Looks like Mailman is expecting to find a Postfix
On Feb 06, 2014, at 07:11 PM, Florian Fuchs wrote:
>1. A continuous integration tool for the Mailman suite.
Very much +1.
I like the development model where we have a gatekeeper against merges to the
trunk better than post-merge buildbot-style validations. That way, we know
that only merges tha
101 - 200 of 2113 matches
Mail list logo
