Hello.
I'm trying to make Mailman to work with Mysql database. I followed this
instructions: http://goo.gl/QkTso and in mail log this is the last line:
postfix/local[13381]: AA4B9B38235: to=cl...@x.xx, relay=local,
delay=0.39, delays=0.02/0.04/0/0.34, dsn=2.0.0, status=sent (delivered
Klemen Humerca wrote:
But emails are not send to list members. If I change it back to file
based db (remove extend.py) mails are delivered.
I'm using Mailman version 2.1.9 on CentOS. There is nothing in the
Mailman logs. I can see that queries in mysql are executed and I also
tested
Yes, web admin interface works and extend.py is in the place
(/var/lib/mailman/lists/list-name). And I've been checking logs in
/var/log/mailman. I've added this line to mm_cfg.py:
MYSQL_MEMBER_DB_VERBOSE = 4
and I've found this in error log:
Aug 31 13:03:14 2011 (16396) Uncaught runner
On 8/31/2011 12:15 PM, Klemen Humerca wrote:
Yes, web admin interface works and extend.py is in the place
(/var/lib/mailman/lists/list-name). And I've been checking logs in
/var/log/mailman. I've added this line to mm_cfg.py:
MYSQL_MEMBER_DB_VERBOSE = 4
and I've found this in error log:
kphamilton wrote:
I have actually accomplished this! Woohoo! I did upgrade as you said to
MysqlMemberships.py.
I accomplished the rest in a different manner than you suggested, so I will
share if others attempt this.
I used export in the /bin folder to export all list data in xml format.
I used the bin/export before I added the extend.py to any of the lists and it
retrieved all of the necessary information.
Mark Sapiro-3 wrote:
kphamilton wrote:
I have actually accomplished this! Woohoo! I did upgrade as you said to
MysqlMemberships.py.
I accomplished the rest in a
kphamilton wrote:
I used the bin/export before I added the extend.py to any of the lists and it
retrieved all of the necessary information.
OK. That makes sense.
BTW, just for curiousity, I actually tried a partial test on the
withlist suggestion I posted, and I found problems. In case anyone
Hello,
I am attempting to migrate from using Mailman's flat file to store
information about members towards a MySQL database backend instead. I have
successfully configured it so that when I add a new member or change a
member, it changes appropriately with the database table. The problem is
kphamilton wrote:
I am attempting to migrate from using Mailman's flat file to store
information about members towards a MySQL database backend instead. I have
successfully configured it so that when I add a new member or change a
member, it changes appropriately with the database table. The
Mark Sapiro wrote:
from Mailman import mm_cfg
from Mailman import OldStyleMemberships as OSM
def move_members(mlist):
if not mlist.Locked():
mlist.Lock()
for member in OSM.getMembers(mlist):
if
I have actually accomplished this! Woohoo! I did upgrade as you said to
MysqlMemberships.py.
I accomplished the rest in a different manner than you suggested, so I will
share if others attempt this.
I used export in the /bin folder to export all list data in xml format.
I then wrote a python
Mailman,
Does it have support to have the user base in an mySQL backend? I could
not find anything describing this on you site.
Thanks
--will
--
Mailman-Users mailing list
[EMAIL PROTECTED]
Has anyone on this list ever tried to get Mailman to interface with a
SQL database for storage of member addresses and such.
Was just wundering from the perspective that it would be easyer to
intergrate a mailing list in to a site if you could simply dump new
members in to a MySQL table, or
At 11:38 AM -0800 1/1/01, J C Lawrence wrote:
Although the discussion has faltered recently
I don't think taking a break for the holidays qualifies as faltering.
Some of us have been off with family and taking a bit of a holiday
from pretty much everything... (and using the time to try to
14 matches
Mail list logo
