One of my top priorities has been to port Mailman 3 (core) to Python 3. This
work is now complete, and ready to be merged into trunk. No doubt bugs still
lurk, but at least the entire test suite is passing. My intent is to merge
this to trunk and do another beta release before the end of the
On Dec 12, 2014, at 07:52 AM, Andrew Stuart wrote:
I want to run the REST tests against my live Mailman server with its Postfix
mail server and Postgres database, via:
nose2 -v -P rest
After many (many) hours of digging deep and figuring out how it works, I
suspect at this stage that maybe the
On Dec 12, 2014, at 08:35 AM, Andrew Stuart wrote:
I’m writing an authenticating proxy for the Mailman REST API and want to make
sure everything works as expected against real infrastructure
(Postgres/Postfix/Sqlalchemy/Falcon).
We definitely want such a proxy. It's always been our intent that
Yes. Both ports have landed in trunk.
Cheers,
-Barry
___
Mailman-Developers mailing list
Mailman-Developers@python.org
https://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives:
On Dec 07, 2014, at 01:23 PM, Abhilash Raj wrote:
And coming to your problem, since mailman is still in development the default
layout is `dev` which helps developers as `var` directory is stored right in
front of them. Once it is packaged and released for production you can expect
some default
On Dec 07, 2014, at 01:48 AM, Stephen J. Turnbull wrote:
@Barry: would it be impossible/a bad idea to have mailman info -v
output usable config files?
Not `mailman info` but for `mailman conf` it would make a lot of sense to have
a switch to dump an ini-file compatible format.
Cheers,
-Barry
On Dec 02, 2014, at 11:26 AM, Aurelien Bompard wrote:
I kinda think so too, so I tried removing the conversion to unicode in get()
and __getitem__(): I have about 20 failures in the whole test suite, and a
couple UnicodeWarnings from SQLAlchemy. I'm going to try and fix these
failures and the
On Dec 01, 2014, at 05:45 PM, Aurelien Bompard wrote:
I'm really interested in any insight on this issue. Thanks for reading all
that :-)
To be honest, mailman.email.message.Message should really go away. It's a
terrible, and old, hack. A few things *are* useful, such as pickle support
On Nov 26, 2014, at 02:30 PM, Abhilash Raj wrote:
I am working on porting mailman3 to python3. There are few doubts I have
which may sound stupid, but I have a little knowledge about encoding and
charsets which I think is important for the port. Also this is my first time
working on python3 so
On Nov 25, 2014, at 08:59 PM, Mark Sapiro wrote:
MM 2.1 does have an additional capability in the web UI, namely the
ability to set all members mod bits on or off with an off/on radio
selection and a single click. Thus, an admin can change
default_member_moderation to No or Yes and with a couple
On Nov 26, 2014, at 07:18 AM, Mark Sapiro wrote:
On 11/25/2014 10:20 PM, Andrew Partan wrote:
Say you have a list where a large argument breaks out. I want to
change the list to moderated for a while until everyone calms down.
Then change it back to unmoderated. There are some people who are
On Nov 25, 2014, at 11:46 AM, Aurelien Bompard wrote:
As a result, unless I'm missing something changing, the list's
default_moderation_action has no effect on existing members. Do I
understand correctly?
That is correct. As Steve points out, the intent is that this setting is
initialization
I'm happy to say that with Kurt Griffiths' release of Falcon 2.0b1 to PyPI, I
have merged the MM3 falcon branch to trunk. This means the Mailman internal
dependency transitions are complete. Along with the SQLAlchemy transition,
our trunk should now only depend on Python 3 compatible libraries.
Thanks very much for sending this around.
On the core, I don't have a formal list of blockers (I should add tags), but
what I think must be done include:
- Port the REST framework to falcon. This is essentially done, and is just
waiting for an upstream falcon release to land on trunk. I
On Nov 03, 2014, at 10:59 PM, Guillaume Libersat wrote:
I've just tried the branch and wanted to point out that I had to add :
from __future__ import print_function
at the beginning of:
- src/mailman/bin/checkdbs.py
- src/mailman/bin/bumpdigests.py
otherwise it would complain about using
Hi Developers!
In honor of the penultimate Mailman Day of 2014, I wanted to announce a
significant transition in the implementation of Mailman 3 and call out the
contributions of two of our members.
For a long while now we've used Storm as the ORM layer in MM3. ORM, meaning
object relational
On Oct 31, 2014, at 02:53 PM, Phil Budne wrote:
This may be of greatest interest to FreeBSD MacOS port
maintainers.. I've been running these patches to mailman
mailman-2.1.18.1 to use kqueue to watch the queue directories since
August.
It looks like the inotify facility on Linux might do the
Hi Mailman Hackers!
I wanted to let you know about some very cool work that Abhilash Raj has been
doing, and to request your help to review and test it.
You might know that for a long time, Mailman 3's ORM (Object Relational
Mapper) layer was provided by Storm[1]. There were a lot of things to
On Sep 16, 2014, at 03:20 PM, Paul Wise wrote:
From our discussions at DebConf14 it sounds like Barry Warsaw is
working on this but I don't think it will be ready in time. I also
think it is far too early to package mailman3 in a stable distro
release at this time.
I wouldn't say working
As you know, I'm keen on porting Mailman 3 to Python 3. I can't even start
this effort until all of our dependencies are compatible with Python 3. We
have two big blockers, restish (which provides the framework for the REST
administrative API), and Storm (our ORM). Development for both
On Aug 07, 2014, at 03:30 PM, Stephen J. Turnbull wrote:
Of course. I didn't explain myself well. What you have now is
mailman/ -+- client/ -+- _client.py
+- docs/
+- tests/
+- cli/ -+- client.py
On Jul 29, 2014, at 10:13 AM, Aurelien Bompard wrote:
I'm interested in helping port MM3 to SQLAlchemy, I've had some experience
with it in the past. But first I'll add some tests to my patch, then I'll
port KittyStore to SQLAlchemy, so I'll make less mistakes porting MM3, which
is a
On Jul 27, 2014, at 03:59 AM, 'ML mail' via barry wrote:
Yes, I guess something like a -m option would be good to specify that the
e-mails being added with the -a option are moderators. Right now I have
switched to using the REST API as it has all features I need, great work btw!
Probably a more
On Jul 25, 2014, at 01:37 PM, 'ML mail' via barry wrote:
I am trying to find out all possible REST API parameters but can't find any
documentation listing them all. For example I want to create a new mailing
list using the following REST API URL:
http://localhost:8001/3.0/list
in the
On Jul 16, 2014, at 08:20 AM, 'ML mail' via barry wrote:
Thanks for the details but actually I was now only asking in which table are
stored the e-mail addresses of a mailing's list subscribers? I thought they
would be stored in the user table but I can't see any e-mail addresses
there, neither
On Jun 17, 2014, at 11:28 AM, Stephen J. Turnbull wrote:
Were we (on dmarc@ietf) talking all along about OpenID when we wrote
OAuth? They're different, although I don't know exactly how or why
(and neither RFC made obvious mention of the other :-( ).
I haven't been keeping up with the latest
On Jun 17, 2014, at 09:34 AM, Joshua Cranmer wrote:
The problem with OAuth is that a lot of its details are left up to the whims
of the implementor, such as the location of its various endpoints or even
what elements in the query are mandatory. Figuring out how to go from email
address to OAuth
On Jun 14, 2014, at 10:15 PM, John Levine wrote:
AOL and Yahoo both have OAUTH APIs, but they are not the same, and I
see no likelihood that the APIs will converge, or that the next large
webmail provider to DMARC us will be compatible with either. But
everyone has a SUBMIT server.
Mailman has
On Jun 12, 2014, at 02:18 PM, John Levine wrote:
* Forwarding signature
The IETF DMARC list is discussing a mutant weak DKIM signature from a
sending system (e.g. Yahoo and AOL) that would survive forwarding, but
contains a list of forwarding target domains. It's only considered
valid if it's
On Jun 13, 2014, at 12:11 AM, John R Levine wrote:
When a user at a p=reject signs up for a list, you demand an OAUTH API
token if the the provider supports it, otherwise their host system
password.
-1 on the password thing. It's too close to phishing, imposes serious
privacy issues on
On Jun 13, 2014, at 01:46 PM, Stephen J. Turnbull wrote:
If you want real irony, look no farther than Yahoo! Groups' From:
header field. Yahoo! is using DMARC to get yahoo.com out of the
From: field in list traffic, and Groups is putting it right back in.
I'm on a few Yahoo! Groups and the From
On Jun 13, 2014, at 07:02 AM, Stephen J. Turnbull wrote:
This is just the evil kind of thing we *want* to do to AOL!
That's not the evil thing I *really* want to do. I want to just reject all
posts from p=reject sites. But I know we can't get away with that.
-Barry
On Jun 02, 2014, at 12:56 PM, Rajeev S wrote:
I was in an idea to follow the one class per file style, especially when
the classes tend to grow large in size as in the tests.(It was mentioned in
the Barry's style guide, and so is a common coding guideline.)
Should I change that?
I intend to
I'm really sorry I haven't had time to catch up on the various DMARC threads,
but I'm hoping to do so early next week.
On May 30, 2014, at 10:35 AM, Murray S. Kucherawy wrote:
What's the expertise on the idea of adding footers in a new MIME text/plain
part rather than just bolting it onto the
On May 29, 2014, at 05:20 PM, Patrick Ben Koetter wrote:
Deleting a list/domain requires an (internal) scheduler. Does Mailman have
one? A broom job that can be called via cron?
Sort of, but the way these are handled currently are individual scripts that
each have to be added to cron.
... and
On May 30, 2014, at 03:41 AM, Stephen J. Turnbull wrote:
Probably scripts should not be using commands that need multiple
confirmations, though.
Agreed!
-Barry
___
Mailman-Developers mailing list
Mailman-Developers@python.org
Although I haven't had time to go through the code, I'm liking what I'm seeing
here on the mailing list. Just a quick comment.
On May 27, 2014, at 12:27 PM, Abhilash Raj wrote:
Since this tool is meant for the users, you should write better
documentation. Like in using.txt
Ideally, because
On May 14, 2014, at 12:19 PM, Stephen J. Turnbull wrote:
Barry Warsaw writes:
I just want it to be consistent, easily described, and easily understood by
users. If it makes sense for the mmclient CLI to different from the
shell-access mailman command, then we at least need
On May 13, 2014, at 01:45 AM, Stephen J. Turnbull wrote:
In the model Rajeev has shown so far, the scope argument (list,
domain, user) hasn't been optional.
If it's truly non-optional in the sense that there's no default, and the scope
is required, then maybe it's okay. It just doesn't look
On May 13, 2014, at 03:27 PM, Rajeev S wrote:
Further there is a possibility of the user specifying multiple scopes,
mmclient show --list --listname l...@domain.org --domain
Would --list be implied by seeing a `--listname=l...@example.com`? E.g. would
this be just as useful, and a little
On May 11, 2014, at 10:37 PM, Rajeev S wrote:
I doubt the usability of a common option `name`. As per the above snippet,
you have used a `in-domain` to specify the domain name. There are many such
instances where you would have to use more than one `name`, for instance
adding moderators for a
On May 11, 2014, at 10:37 PM, Rajeev S wrote:
I have modified the CLI to use English like commands and hence will
use them hereafter.
*list*
The command lists the entities and should be available for users,mailing
lists and domains.
mmclient list list [l...@domain.org] [-v for verbose]
On May 04, 2014, at 01:26 PM, John Levine wrote:
I realize I'm a bit late to this party, but this is a technique that I
don't think has been addressed here. On my lists I've fixed the DMARC
bounces by rewriting From: lines of DMARC'ed domains like this on the
way out:
From: Marissa
On May 03, 2014, at 09:59 AM, Tom Browder wrote:
Using the latest cli commands as shown in Rajeev's
/src/mailmanclient/cli/docs/using.txt would be for the default list
style:
test_one = example.create_list('test-one')
Then, for other styles, we could use something like (pardon my pseudo
On May 01, 2014, at 06:25 AM, Tanstaafl wrote:
? Not fully supporting the most popular (mysql/mariadb)?
Contributions welcome!
the-obvious-response-ly y'rs,
-Barry
___
Mailman-Developers mailing list
Mailman-Developers@python.org
On May 02, 2014, at 06:36 AM, Rajeev S wrote:
3.The code has been verified with pep8 *and* flake8 tools. It also passes
most of the guidelines mentioned in Barry's styleguide. Some of the
guidelines are yet to be met, like the licensing block
and stuff like __all__. Also the ^L at major sections
Hi Varun, welcome to Mailman GSoC!
On Apr 30, 2014, at 12:24 PM, varun sharma wrote:
Thanks for giving me opportunity to work with mailman community this
summer. I'm an undergraduate student from Manipal Institute Of Technology,
India and i'll be working on project CI tool for the Mailman suite
On Apr 30, 2014, at 09:38 PM, Tim Marx wrote:
I'm using mailman 3.0.0b4 (with mailman-bundler) and ran into the same
problem as described above. Luckily I found this bug report and could manage
to fix it with the patches above.
May I ask anybody (with more bazar-knowledge than me) to merge this
On Apr 25, 2014, at 04:55 PM, Aurelien Bompard wrote:
I'm trying to create a User in Mailman 3 from an existing Address. If I were
using the Python interface, that would be very easy: just create the user
with no address and then link the existing address to it.
So the address is currently
On Apr 25, 2014, at 06:31 PM, Aurelien Bompard wrote:
Interesting. I'll look into that at some point, but I have a few more
urgent things to do, so if someone wants to beat me to it feel free...
;-)
Can you open a bug?
-Barry
___
Mailman-Developers
Hello Mailman enthusiasts!
Time and motion
Wind and sun and rain
Days connect like boxcars in a train
Another Pycon has come and gone and with it, another fantastic sprint among
the core developers. We accomplished quite a bit, and now we'd like to share
the results with you. On
On Mar 28, 2014, at 12:01 AM, Kẏra wrote:
I keep hearing about the need for migration scripts, but all indicates that
these do not exist yet (via blocking bug for the next MM3 beta). Is that
true?
Is there a way to keep tabs on the progress towards the beta 4 release?
looking at launchpad, it
On Mar 26, 2014, at 07:44 AM, Máirín Duffy wrote:
I think they will make the recordings available since they have last years'
up now, but I don't know when they'll come online. The slides I used are
here:
http://duffy.fedorapeople.org/presentations/libreplanet%202014/
When the video is
On Mar 20, 2014, at 01:17 PM, Ian Eiloart wrote:
For me, the big win for spam prevention with mailing lists is the restriction
on posters: it’s what keeps mailing lists relatively spam free. Most sites
don’t like to bounce messages that they’ve previously accepted, so that means
that the spam
On Mar 18, 2014, at 11:17 AM, Máirín Duffy wrote:
Just a head's up that this weekend I'm going to be giving a presentation
about Mailman 3 - mostly focused on Hyperkitty - at LibrePlanet in Boston
this coming weekend. I'm going to give an overview of the design process, the
implementation
On Mar 17, 2014, at 07:59 PM, Aurelien Bompard wrote:
On Mailman3, every message held notification has XXX as the reason. This
comes from the HoldChain class in mailman/chains/hold.py, where XXX is
hardcoded. I'd like to fix that. I think there could be a list in the
message metadata to which
On Mar 17, 2014, at 02:34 PM, Stephen J. Turnbull wrote:
I don't understand what you're trying to say here. Are you saying
that rules should not have a rules_to_run_before_this_rule field,
but it's OK if a chain rule_B, rule_A is buggy because rule_A should
be run before rule_B? Of course we
On Mar 13, 2014, at 05:06 PM, Stephen J. Turnbull wrote:
I expressed myself poorly. The parameters of the decision logic given
the list of senders are different for the two rules so both rules are
needed. But I really think that determining the sender should be done
in one place by one set of
On Mar 15, 2014, at 11:29 AM, Terri Oda wrote:
Sorry! I know our official stance for regular contributors is use whatever
as long as you can submit a launchpad merge request but for GSoC students,
you're on a short timeline that's going to be busier at the end than the
beginning and experience
On Mar 11, 2014, at 12:55 PM, Stephen J. Turnbull wrote:
Barry isn't official in GSoC, but he's head of the Mailman project and
a ranking demi-god in the Pytheon. Also crazy busy, so you may get a
polite brushoff. OTOH, he can probably solve Mailman problems in half
the time of anybody else.
On Mar 12, 2014, at 01:43 PM, Stephen J. Turnbull wrote:
Offhand I'd say that having both a Member rule and a NonMember rule is
a bad idea. There should be one conceptual test: can we identify a
member as the originator of this post? Having Member and NonMember
rules that can both succeed is
On Mar 11, 2014, at 11:28 AM, Aurelien Bompard wrote:
I wonder where this link is supposed to lead. I did not find such an
endpoint in Postorius, and the Mailman REST API is not public anyway.
Am I missing something?
Not really - you've noticed a holdover from Mailman 2.1 that hasn't been
On Mar 11, 2014, at 06:25 PM, Aurelien Bompard wrote:
What do you think about all that? Do you agree there's actually an
issue there? Any idea how to solve it? For example, make the NonMember
rule exit if a member is found amongst the senders (which would simply
be equivalent to making it yield
On Mar 08, 2014, at 12:14 PM, Abhilash Raj wrote:
I was in a conversation with Barry yesterday to setup a unofficial git
mirror for mailman since there are large number of people who use git as
their primary vcs.
Let me just state my official position for Mailman core: we'll switch to git
some
On Mar 08, 2014, at 09:00 PM, Patrick Ben Koetter wrote:
Seems we have an inofficial git repo now. Are there any opinions on who should
be in control of the code, e.g. handle merge requests, etc.? AFAIK Barry has
the last word on what gets to become Mailman 3 at the moment. I'd like to move
on
On Mar 08, 2014, at 01:33 PM, Patrick Ben Koetter wrote:
As for the workflow: Wars have been waged to etablish the right way [tm] to
do this. I suggest whatever we do, make it easy to adopt or people will turn
away because they need to spend too much work on project administration.
See my
On Mar 08, 2014, at 03:01 PM, Paul Wise wrote:
https://bugs.debian.org/714038
Subscribed!
-Barry
___
Mailman-Developers mailing list
Mailman-Developers@python.org
https://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ:
On Mar 07, 2014, at 10:07 AM, Stephen J. Turnbull wrote:
Usually Postfix is configured to route mail with a set of sendmail-
like aliases files, so you just define different alias files for each
Mailman installation and configure Postfix to look at them with the
alias_database directive in
On Mar 06, 2014, at 05:24 PM, Patrick Ben Koetter wrote:
* Tom Browder tom.brow...@gmail.com:
Can I use essentially the same settings I used for Postfix and Apache
for my MM 2 installation with MM 3?
No, you can't. MM3 provides an LMTP Server. Configure a transport that routes
messages for a
On Mar 05, 2014, at 09:06 AM, Bhargav Golla wrote:
files in mailman, I found that the default username and password for admin
is restadmin and restpass. Tried that and was out of luck there too. Could
you help me with the default username and password details?
That's only the default username
On Mar 03, 2014, at 09:30 PM, Mark Sapiro wrote:
and this time all was well except two tests failed. The only thing I can
think of is at one point, not realizing this was a 32-bit OS, I rsync'd
the virtualenv from the 64-bit machine. I thought I had cleaned that all
up, but there may have been
On Mar 03, 2014, at 07:00 PM, Mark Sapiro wrote:
On the other machine with Ubuntu 12.10 32 bit, I again have a virtualenv
with packages up to date, and python setup.py develop runs fine, but
nose2 -v dies immediately with the attached traceback. Both
zope.component and zope.interface are the same
On Feb 26, 2014, at 02:39 PM, Mark Sapiro wrote:
I moved zope.interface-4.0.5 aside and reran setup and it was happy this
time.
Looks like upstream released zope.interface 4.1.0, but this hasn't been pulled
into Debian or Ubuntu yet. This breaks other dependencies referenced by
On Feb 28, 2014, at 10:36 AM, Bhargav Golla wrote:
2. Can I assume that all mailing lists built by Mailman support the REST
interface? Also, I have tried to see if I can get JSON responses and I am
unable to by adding a HTTP Accept Header to take application/json. Am I
doing anything wrong or is
On Mar 01, 2014, at 10:05 PM, Terri Oda wrote:
I'm still not 100% sure I'll be going, but I'll probably have to make a
commitment on plane tickets this week (I have hotel and conference ticket,
but I was holding off on flights because there may be a work conflict for
me.)
I hope it works out!
On Feb 28, 2014, at 02:38 AM, Tejas Shah wrote:
However, starting the mailman server using mailman start, when i try to
test using nose2 -v , it gives me o/p:
As Mark says, you should not start the mailman server before running the
tests. 'mailman start' is there to start the server for
On Feb 26, 2014, at 09:21 PM, Mark Sapiro wrote:
You have to put/or enable something in sitecustomize.py (On Ubuntu a symlink
to /etc/python2.7/sitecustomize.py) to get it to use the locale.
Have you changed your sitecustomize.py file?
You're right that sys.getdefaultencoding() gets initialized
On Feb 26, 2014, at 02:45 PM, Stephen J. Turnbull wrote:
I have no idea what to do next,
This is clearly a bug, although I think it's relatively recent, so it might be
worth seeing if earlier revisions avoid the problem. Yes, I can reproduce it.
The interesting thing is that the test is in
On Feb 26, 2014, at 02:39 PM, Mark Sapiro wrote:
which encountered one error before hanging apparently with a locked
sqlite3 database.
This is my fault. I had a couple of revisions sitting in my local branch that
I hadn't pushed to Launchpad. Please pull the latest trunk revision (r7234),
On Feb 26, 2014, at 04:57 PM, Mark Sapiro wrote:
The error (failed test) was due to the default encoding in this Python
installation being UTF-8 rather than ascii. Changing sitecustomise.py to
not set UTF-8 allowed the test to succeed.
Hmm. My locale is UTF-8 and I don't see this failure.
On Feb 24, 2014, at 09:54 PM, Florian Fuchs wrote:
The good news: The Python Software Foundation was more successful
(congrats to Terri!), so we'll be able to participate under their
umbrella again. \o/
Much thanks to Terri and all involved. Looking forward to some great GSoC
students again
Hello sprinters!
Once again, the GNU Mailman project will be sprinting at Pycon, this time the
2014 conference in Montreal. I've created a placeholder page for adding ideas
about what you would like to work on, as well as our priorities. We'll be
filling out details over the next few weeks, but
On Feb 21, 2014, at 08:15 AM, Mark Sapiro wrote:
2. Is MM going to have a presence at O'reilly's OSCON 2014 in July?
I don't plan to be there, but others may. There will be a number of us
at PyCon in April https://us.pycon.org/2014/.
I won't be at OSCON either. We'll be sprinting on Mailman
Welcome Shubham and Emily (and all prospective GSoC students).
On Feb 20, 2014, at 08:48 AM, Emily Dunham wrote:
You're on the right track by getting into IRC and posting on the mailing
list! On IRC, it helps to ask a specific question and then wait about 8
hours for a reply, since the
On Feb 20, 2014, at 12:07 PM, Lindsay Haisley wrote:
I'm running Mailman 2.1.15 on a Ubuntu server, feeding into Courier MTA,
running Python 2.7.3. I track security updates and install them
promptly when they're issued by Ubuntu. Yesterday I updated the Linux
kernel from 3.2.0-58-generic
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
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 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 a
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 like. I'll
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 looked
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 feeling.
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
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
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
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 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 like
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,
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
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 perhaps
301 - 400 of 1843 matches
Mail list logo
