Hi,
It looks like config_list isn't working yet in Mailman 3.0, and there seems to be quite a lot of work to do to get it working.
In the meantime, how can I configure accept_these_nonmembers for a list? I need to test LMTP qrunner code that uses this value.
I can do an SQL update, which is probably the easiest way to create a value, but I'm not sure what the value of the field should be.
-- Ian Eiloart IT Services, University of Sussex x3148
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Jul 17, 2008, at 5:58 AM, Ian Eiloart wrote:
It looks like config_list isn't working yet in Mailman 3.0, and
there seems to be quite a lot of work to do to get it working.In the meantime, how can I configure accept_these_nonmembers for a
list? I need to test LMTP qrunner code that uses this value.I can do an SQL update, which is probably the easiest way to create
a value, but I'm not sure what the value of the field should be.
Hi Ian,
I'll look into config_list, but in the meantime with_list should
work. You should be able to fire that up, change the value, then do
config.db.commit() to save your changes.
- -Barry
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSICVXnEjvBPtnXfVAQLGPgP9HvEoqYikobzWNp3hYRINZuvqWTNErvKC 1xbCy/zcM2HtGx6CIfMLqrWnCxWg+M5CsFYAYxulaseLI+df+ozMzZ3JFeDJ/fH7 7Gb+pCCMhru4kukqSXpxEZ5ZPOMH2f9NPsqpOUh8Lqp6KD9sOHAtHdyaTgPtKiEk Jc9Rrb8mbrg= =GSNK -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Jul 18, 2008, at 9:06 AM, Barry Warsaw wrote:
On Jul 17, 2008, at 5:58 AM, Ian Eiloart wrote:
It looks like config_list isn't working yet in Mailman 3.0, and
there seems to be quite a lot of work to do to get it working.In the meantime, how can I configure accept_these_nonmembers for a
list? I need to test LMTP qrunner code that uses this value.I can do an SQL update, which is probably the easiest way to create
a value, but I'm not sure what the value of the field should be.I'll look into config_list, but in the meantime with_list should
work. You should be able to fire that up, change the value, then do
config.db.commit() to save your changes.
BTW, I opened bug 249855 on this.
https://bugs.launchpad.net/bugs/249855
- -Barry
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin)
iEYEARECAAYFAkiAnKEACgkQ2YZpQepbvXE+zQCfX/Nni9w9dkCSu1LUvfqEU4Iw kb4AmwQuy/tW/dw6yyy8BvzZBITSLgd7 =O6lo -----END PGP SIGNATURE-----
participants (3)
-
Barry Warsaw -
Barry Warsaw -
Ian Eiloart