On Thu 2003-07-10 15:21:44 -0400, Barry Warsaw wrote:
On Thu, 2003-07-10 at 15:12, David Birnbaum wrote:
It's easy enough to add members to the list and remove them from an
external source, but it would be really nice if we could have Mailman call
a program of our choice, with some
Hi,
I'm hoping to use Mailman, but have a few requirements which may not be
addressed 'out of the box'. In particular, I'm integrating with another
system and would like to store the foreign system's user IDs in Mailman so
that I can correlate our users with Mailman subscribers. This will then
On Tuesday, July 8, 2003, at 06:19 AM, Chris Boulter wrote:
I'm hoping to use Mailman, but have a few requirements which may not be
addressed 'out of the box'. In particular, I'm integrating with another
system and would like to store the foreign system's user IDs in
Mailman so
that I can
On Thu 2003-07-10 09:20:20 -0700, Donn Cave wrote:
On Tuesday, July 8, 2003, at 06:19 AM, Chris Boulter wrote:
Does Mailman support the storage of any sort of user metadata? If not,
would it be easyish to add? I'm not terribly familiar with Python, but it
looks like I could add attributes to a
On Tue, 2003-07-08 at 09:19, Chris Boulter wrote:
Does Mailman support the storage of any sort of user metadata? If not, would
it be easyish to add? I'm not terribly familiar with Python, but it looks
like I could add attributes to a class and then have them persisted by
Python's
On Thu, 10 Jul 2003, Chuq Von Rospach wrote:
This sounds interesting. So you're suggesting that rather than storing
email addresses of subscribers in Mailman, we store our external system
UIDs, then have sendmail resolve those into email addresses just
before the
mail gets sent?
On Thu, 2003-07-10 at 15:05, Chuq Von Rospach wrote:
you risk turning mailman into yet another CMS, rather than allowing
mailman to interconnect with all of the existing CMS's... the latter is
a much easier and more powerful task.
...and is /definitely/ the direction Mailman 3 is going in.
On Thursday, July 10, 2003, at 11:50 AM, Chris Boulter wrote:
...
Yes, I can imagine others might be also interested in storing data in
addition to subscribers' email addresses - having external system UIDs
would
help with 'single sign-on' integration too, which I've seen discussed
here.
Right.
On Thu, 2003-07-10 at 15:12, David Birnbaum wrote:
It's easy enough to add members to the list and remove them from an
external source, but it would be really nice if we could have Mailman call
a program of our choice, with some arguments/environment variable/STDIN
whenver it reacts to a
Chuq's right on the money here. I'd be happy to do stuff on the PHP
interface side. This would allow connectivity with PHP-Nuke, Postnuke,
Xaraya, and any other PHP-based CMS.
Barry, continuing our recent conversation, I'd be happy to try to do
something on the PHP side but I'll need to get some
On Thursday, July 10, 2003, at 12:19 PM, Barry Warsaw wrote:
friendly with both of those, it'd likely work easily with any CMS.
and/or Zope hint, hint.
Zope should be one of the interfaces, definitely, but I really think
it's time Mailman is interfaced with some non-Python tools so it can
play
On Thu, 2003-07-10 at 15:37, Chuq Von Rospach wrote:
Zope should be one of the interfaces, definitely, but I really think
it's time Mailman is interfaced with some non-Python tools so it can
play better with the world beyond Python. It'll help it become that
much more accepted Out There...
On Thu, 10 Jul 2003, Barry Warsaw wrote:
It's easy enough to add members to the list and remove them from an
external source, but it would be really nice if we could have Mailman call
a program of our choice, with some arguments/environment variable/STDIN
whenver it reacts to a bounce or
On Thu, 2003-07-10 at 17:37, David Birnbaum wrote:
Somewhat expensive, perhaps...BUT it has the advantage of being pretty
quick to write and very simple for those who don't have the time,
knowledge, or resources (#1 and #3, in my case) to build something more
complicated. And, how many
On Thursday, July 10, 2003, at 02:48 PM, Chuq Von Rospach wrote:
...
4) write a script that processes ~mailman/logs/bounce once a day and
feeds bounce data back to the subscription management program.
That might be the key point - if the information he needs is in
logs/bounce,
then something can
On Thu, 10 Jul 2003, Barry Warsaw wrote:
Somewhat expensive, perhaps...BUT it has the advantage of being pretty
quick to write and very simple for those who don't have the time,
knowledge, or resources (#1 and #3, in my case) to build something more
complicated. And, how many requests
16 matches
Mail list logo
