Con Wieland wrote:
>It seems I have a loop going on but I don't understand the error. I
>have multiple similar messages:
It's not a loop.
>Here's an excerpt from the /opt/nsp/mailman/logs/error
>
>Dec 16 17:22:02 2009 (817) SHUNTING: 1261012921.337497
>+ef91a103dec2273f323d2758d
>097a1357d
It seems I have a loop going on but I don't understand the error. I
have multiple similar messages:
Here's an excerpt from the /opt/nsp/mailman/logs/error
Dec 16 17:22:02 2009 (817) SHUNTING: 1261012921.337497
+ef91a103dec2273f323d2758d
097a1357db67d3a
Dec 16 18:11:34 2009 (817) Uncaught ru
Jeff Bernier wrote:
>
>I did however, notice that after I change permissions (I'm doing this from a
>Windows SCP tool), my changes don't appear to "stick". I'm logging in as root.
>
>Should I be changing permissions another way?
>What should be the file and directory permissions in the Archives
Thank you Mark for your help.
I found my Mailman logs, and discovered that in fact the problem was due to
permissions. A few of the files in shunt were messages to a list that no longer
exists. I deleted these out manually, corrected the file permissions, then ran
unshunt. The archive now show
Jeff Bernier wrote:
>
>I 've noticed several files in my shunt folder. when I run show_qfiles, I see
>that they are messages to one of my lists. I have contacted the list
>owner/moderator, and this person tells me messages to the list are going out
>just fine... although I do not see any recent
Hello,
I have a couple of newbie questions...
I 've noticed several files in my shunt folder. when I run show_qfiles, I see
that they are messages to one of my lists. I have contacted the list
owner/moderator, and this person tells me messages to the list are going out
just fine... although
Josh Greenberg wrote:
>
>I'm completely unfamiliar with this shunting process and its kind of
>disturbing that mailman would quietly discard a perfectly good message
>that had been sent by an approved sender and not throw any errors except
>this cryptic line in the error log. I can't find any go
Earlier today one of my users sent a message out to a list but it never
got there. It took a long time to figure out what happened to this
message but when we finally found it, it had been shunted. There was an
entry in the mailman error log that read "Mar 09 11:26:51 2007 (9048)
SHUNTING: 1173
At 7:43 PM -0400 2005-05-14, Charles Sprickman wrote:
> The perms look OK, but I do remember many months ago that the "smtp"
> logfile would sometimes revert to being owned by root rather than
> mailman. Very odd.
Are the logs being automatically rolled by a cron job? That
might expl
On Sat, 14 May 2005, Brad Knowles wrote:
> At 5:14 PM -0400 2005-05-14, Charles Sprickman wrote:
>
>> Now, does anyone have any clue what the error messages below mean?
>> Judging by the number of shunted messages, this happens fairly often. The
>> "I/O error" leads me towards permsissions, bu
At 5:14 PM -0400 2005-05-14, Charles Sprickman wrote:
> Now, does anyone have any clue what the error messages below mean?
> Judging by the number of shunted messages, this happens fairly often. The
> "I/O error" leads me towards permsissions, but on what?
I'd have to check the code,
On Fri, 13 May 2005, Charles Sprickman wrote:
> Hello,
>
> While exploring the "qfiles" directories, I found that "shunt" had about
> 47MB of ".pck" files in it. The FAQ entry I found recommended running
> "unshunt", so I did. Not a good idea, I found. Apparently this requeued
> some very old m
At 5:57 PM -0400 2005-05-13, Charles Sprickman wrote:
> I'm also a bit lost at this point as to what the recommended production
> release is. The website points to 2.1.5 as "stable", but it seems like
> most folks posting here are using a 2.1.6 snapshot. Which is preferred
> for production u
Hello,
Please bear with me as I try and get my Mailman skills in order,
previously I was just babysitting this thing, but now I'm trying to dig in
and make sure everything is actually working as it should be.
While exploring the "qfiles" directories, I found that "shunt" had about
47MB of ".pc
John Poltorak wrote:
>
>I tried subscribing to my test list and get a file created in the shunt
>queue.
>
>What is this queue for and how do I process it? qrunner --runner=All
>doesn't seem to get rid of it.
The shunt queue is where things are set aside for reprocessing later
(manually). See the
I tried subscribing to my test list and get a file created in the shunt
queue.
What is this queue for and how do I process it? qrunner --runner=All
doesn't seem to get rid of it.
--
John
--
Mailman-Users mailing list
Mailman-Users@python
OK... Just found that post in the mailman-developers list that did the
trick:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg06317.html
"Barry, as was noted in a private email to ya - the problem was solved
with
the following patch (courtesy of Mohammed Elzubeir),
--- Scrubber.py.orig 2003-08-
Hello,
We are having some serious problem with a 2.1.2 mailman install. Some
messages get transferred to qfiles/shunt and stay there forever. I am
calling on your help on this one.
I understand from previous mailing list posts that the shunt directory
is used by mailman if:
o messages are too
I'm running mailman 2.1.2; debian package version is 2.1.2-6. I'm using
Sendmail for mail.
The traceback below showing up in my error log. Running check_perms
says "no problems found." The directory in question looks like this:
drwxrws---2 root list 4096 Aug 1 13:00 database
19 matches
Mail list logo
