Hello,
Just wanted to ask how you manage the following situation:
There is a list of people you keep in an sql database. This database is
edited/updated daily. From time to time you want to contact these people,
so you export them as a flat file and import into Mailman (for example by
using
Zbigniew Szalbot wrote:
Hello,
Just wanted to ask how you manage the following situation:
There is a list of people you keep in an sql database. This database is
edited/updated daily. From time to time you want to contact these people,
so you export them as a flat file and import into Mailman
Hi,
On Mon, 21 Apr 2008 09:29:57 -0700, Dragon [EMAIL PROTECTED]
wrote:
Zbigniew Szalbot wrote:
Hello,
Just wanted to ask how you manage the following situation:
There is a list of people you keep in an sql database. This database is
edited/updated daily. From time to time you want to
I promised I would report back on this issue, and can now confirm that
with the filtering settings suggested by Mark, the posts from office
man and those from excite man both get delivered by Mailman
correctly, although some MUAs have problems visualizing those from
office man.
Therefore, there
Zbigniew Szalbot wrote:
Hi,
On Mon, 21 Apr 2008 09:29:57 -0700, Dragon [EMAIL PROTECTED]
wrote:
Zbigniew Szalbot wrote:
Hello,
Just wanted to ask how you manage the following situation:
There is a list of people you keep in an sql database. This database is
edited/updated daily. From
[EMAIL PROTECTED]
[EMAIL PROTECTED] [EMAIL PROTECTED]
Message-ID: [EMAIL PROTECTED]
X-Sender: [EMAIL PROTECTED]
Received: from 77-254-86-54.adsl.inetia.pl [77.254.86.54]
with HTTP/1.1 (POST); Mon, 21 Apr 2008 20:18:25 +0200
User-Agent: RoundCube Webmail
Content-Type: text/plain;
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am happy to announce the release of Mailman 2.1.10.
This is a security and bug fix release and it is highly recommended
that all sites upgrade to this version. Mailman 2.1.10 also adds support
for three new language translations, Galician, Hebrew
On Mon, Apr 21, 2008 at 3:50 PM, Mark Sapiro [EMAIL PROTECTED] wrote:
Note: If you are not ready to upgrade, patches for these two issues
are available at
http://sourceforge.net/project/showfiles.php?group_id=103
in the 2.1.9 file list.
THANK YOU!
-Jim P.
Mark Sapiro wrote:
I am happy to announce the release of Mailman 2.1.10.
Now running on mail.python.org. Please let us know if there are any problems.
--
Brad Knowles [EMAIL PROTECTED]
LinkedIn Profile: http://tinyurl.com/y8kpxu
--
Mailmain is currently not sending traffic. But that's okay at the
moment. One of my users wants to cancel a message she's sent. Normally
I couldn't do this, because traffic goes out too fast for me to catch
it.
But since right now nothing's moving, I told her I'd try before I
re-started
Mark Sapiro wrote:
I am happy to announce the release of Mailman 2.1.10.
Congratulations!
I presume the usual upgrade instructions apply?
http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.014.htp
dn
--
Mailman-Users mailing list
McNutt Jr, William R wrote:
Mailmain is currently not sending traffic. But that's okay at the
moment. One of my users wants to cancel a message she's sent. Normally
I couldn't do this, because traffic goes out too fast for me to catch
it.
But since right now nothing's moving, I told her I'd
Mark Sapiro wrote:
I am happy to announce the release of Mailman 2.1.10.
This is a security and bug fix release and it is highly recommended
that all sites upgrade to this version. Mailman 2.1.10 also adds support
for three new language translations, Galician, Hebrew and Slovak and a
few new
David Newman wrote:
I presume the usual upgrade instructions apply?
http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.014.htp
For upgrading python.org, I made the mistake of leaving Mailman running even
though I had shut down postfix and apache, and it still worked okay. I'd
Brad Knowles wrote:
McNutt Jr, William R wrote:
Mailmain is currently not sending traffic. But that's okay at the
moment. One of my users wants to cancel a message she's sent. Normally
I couldn't do this, because traffic goes out too fast for me to catch
it.
But since right now
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 21, 2008, at 3:50 PM, Mark Sapiro wrote:
I am happy to announce the release of Mailman 2.1.10.
Congratulations Mark! Long live Mailman 2.2. :)
I will update the web sites.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 21, 2008, at 5:28 PM, Brad Knowles wrote:
Mark Sapiro wrote:
I am happy to announce the release of Mailman 2.1.10.
Now running on mail.python.org. Please let us know if there are any
problems.
Wow, awesome Brad. Thanks!
- -Barry
Brad Knowles wrote:
Remind me next time that we *MUST* upgrade to the betas and RCs on
python.org once you've made them available. The changes made to the code
which supports skipping unparseable messages means that mmdsr has to be
changed to suit, otherwise you could wind up with a daily
David Newman wrote:
I presume the usual upgrade instructions apply?
http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.014.htp
Those are really somewhat outdated. I probably should have just
replaced them, but I created a new FAQ
Mark Sapiro wrote:
Note that in addition to the logging change for unparseable messages,
they will now be saved in the shunt queue, so if you have a lot,
you'll have to deal with that too.
These are the *.psv files? Yeah, we've got almost 8000 of them on
python.org. Do you have any
Brad Knowles wrote:
Mark Sapiro wrote:
Note that in addition to the logging change for unparseable messages,
they will now be saved in the shunt queue, so if you have a lot,
you'll have to deal with that too.
These are the *.psv files? Yeah, we've got almost 8000 of them on
python.org. Do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Sapiro wrote:
|
| I think the best solution is to turn off the preservation of
| unparseable messages, and add an mm_cfg.py setting to turn it on. I
| can work up a patch.
|
A patch is attached. It doesn't turn off preservation by default
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 21, 2008, at 9:30 PM, Mark Sapiro wrote:
You could set up a cron to run every hour or some other interval to
efectively do
rm $var_prefix/qfiles/shunt/*.psv
The problem with that is there can occasionally be queue entries
preserved for
On 4/21/08, Barry Warsaw wrote:
We should probably have some kind of shunt queue culler cron script in
place, either that archives and deletes those files, or just expires
them after a certain amount of time.
That's easy enough to do with cron and find. You tell me what you
want, and
On 4/21/08, Mark Sapiro wrote:
If you could apply this patch (you can apply it directly to the
installation directory, by e.g.
cd /usr/local/mailman
patch -p0 path/to/2.1.10.patch.txt
Patch applied fine, no complaints.
and set
QRUNNER_SAVE_BAD_MESSAGES = No
Done.
in mm_cfg.py
On 4/21/08, Brad Knowles wrote:
I have applied the patch to my installation and I'm sure it's good, but
I haven't seen any unparseable messages.
I haven't seen any more unparseable messages in the last few minutes,
but let's see how things go.
We've now had a couple of unparseable
26 matches
Mail list logo
