[Mailman-Users] Mailman + Sendmail

2005-09-12 Thread Rich West
I've had mailman running for years and have only recently started having some delivery problems with it. I originally chalked it up to a particular set of users within the one list that I am on (we host a bunch of lists for others), but, after some investigation, I have been unable to narrow

Re: [Mailman-Users] Mailman + Sendmail

2005-09-12 Thread Rich West
I did some further analysis and discovered that the messages (with the same message ID) were showing up in the ps output as processing from queue. Digging a little further, I tried killing off the sendmail processes that were processing those requests, and I saw the following appear in the

Re: [Mailman-Users] Posts Not Going Through

2004-10-24 Thread Rich West
Well, a couple of places to look would be in: /var/mailman/logs/smtp /var/mailman/logs/smtp-failure /var/mailman/qfiles/out, in, shunt /var/log/maillog If things are backed up, you should see the outbound messages piling up in the out folder. Any errors, for what they are, should be in

Re: [Mailman-Users] Posts Not Going Through

2004-10-24 Thread Rich West
Damn Gentoo stuck it elsewhere. Searching. I know what you mean.. Fedora sticks 'em in /var/log/mailman.. For key tools such as this one (mailman), I tend to lean towards rolling my own.. smtp-failure shows the following: Oct 07 07:57:24 2004 (6344) All recipients refused: {'[EMAIL

Re: [Mailman-Users] Odd smtp-error

2004-10-23 Thread Rich West
Mark Sapiro wrote: o In the sendmail logs, I get (just do the normal replacements for the words at and dot): Oct 23 21:26:08 cranium sm-mta[13718]: i9O1Q8EF013718: from=test-bounces+rich dot west=wesmo dot [EMAIL PROTECTED] dot wesmo dot com, size=1421, class=0, nrcpts=0, proto=ESMTP,

[Mailman-Users] Mailman under Fedora Core 2

2004-10-22 Thread Rich West
I migrated our main server from Fedora Core 1 (running our own built version of mailman 2.1.5) to another server running a fresh install of Fedora Core 2 (running our own built version of mailman 2.1.5) about two weeks ago. Since that time, we have had continual problems with our mailman

[Mailman-Users] Odd smtp-error

2004-10-22 Thread Rich West
Interesting.. in investigating another problem, I noticed the following in the smtp-error file: Oct 22 12:14:49 2004 (4223) All recipients refused: {'[EMAIL PROTECTED]': (550, '5.1.1 [EMAIL PROTECTED]... User unknown')}, msgid: [EMAIL PROTECTED] Oct 22 12:14:49 2004 (4223) delivery to [EMAIL

Re: [Mailman-Users] Odd smtp-error

2004-10-22 Thread Rich West
on.. Not sure where else to look... -Rich Rich West wrote: Interesting.. in investigating another problem, I noticed the following in the smtp-error file: Oct 22 12:14:49 2004 (4223) All recipients refused: {'[EMAIL PROTECTED]': (550, '5.1.1 [EMAIL PROTECTED]... User unknown')}, msgid: [EMAIL PROTECTED

Re: [Mailman-Users] Mailman under Fedora Core 2

2004-10-22 Thread Rich West
left? On Fri, 2004-10-22 at 12:09, Rich West wrote: I migrated our main server from Fedora Core 1 (running our own built version of mailman 2.1.5) to another server running a fresh install of Fedora Core 2 (running our own built version of mailman 2.1.5) about two weeks ago. Since that time, we

Re: [Mailman-Users] Odd smtp-error

2004-10-22 Thread Rich West
on.. Not sure where else to look... -Rich Rich West wrote: Interesting.. in investigating another problem, I noticed the following in the smtp-error file: Oct 22 12:14:49 2004 (4223) All recipients refused: {'[EMAIL PROTECTED]': (550, '5.1.1 [EMAIL PROTECTED]... User unknown')}, msgid: [EMAIL PROTECTED

Re: [Mailman-Users] Mailman + htDig

2003-08-14 Thread Rich West
Assuming you are using en as the list language and standard templates, can you take a look at the file $prefix/templates/en/archtoc.html line 16 should read: %(htsearch)s Yup.. it is there.. This is where the results of the quick_maketext() on TOC_htsearch.html, that is the

Re: [Mailman-Users] Mailman + htDig

2003-08-14 Thread Rich West
Can you confirm you mean that the per-list htdig directories of the following form are being created: $prefix/archives/private/listname/htdig are being created and that inside each of them there is a file named listname.conf Is there also a file called rundig_last_run and a bunch of ,db

[Mailman-Users] Mailman + htDig

2003-08-14 Thread Rich West
I realize this has come up often in the list, but hit a snag and was not sure where else to turn. I couldn't find much in the archives that addressed this, but if it is a duplicate, please accept my apologies. I've applied the htDig patches :

Re: [Mailman-Users] Mailman + htDig

2003-08-14 Thread Rich West
, though. Now, I just have to go through and migrate the existing lists. :) Hopefully, that won't be too difficult. :) Thanks for all of your help! -Rich Rich West wrote: Ok.. I blew away my test list, set USE_HTDIG=1, restarted the qrunner, created the list with newlist, ran blow_away_htdig test

[Mailman-Users] RPM/SRPM for Mailman 2.1

2003-01-06 Thread Rich West
I have finally nailed down the SPEC file for proper full installation of mailman 2.1. For those that want the binary, it can be grabbed from: ftp://ftp.wesmo.com/pub/redhat/i386/mailman-2.1-1.i386.rpm The Source RPM can be grabbed from here:

[Mailman-Users] Upgrade to 2.1 with Sendmail not mailing to list?

2003-01-02 Thread Rich West
This is probably a quick one, but I thought I would mail it out to the list. I did check the archives, but didn't have much luck. We are running 2.0.13 and I took on the task of upgrading to 2.1. Our RH-based server is running Sendmail (8.12.7) and happily chugging along managing a few dozen

Re: [Mailman-Users] Mailman rpm for RedHat 7.3?

2003-01-02 Thread Rich West
I rolled an RPM earlier today. If anyone finds it useful, feel free to use it. ftp://ftp.wesmo.com/pub/redhat/i386/mailman-2.1-1.i386.rpm ftp://ftp.wesmo.com/pub/redhat/SRPMS/mailman-2.1-1.src.rpm Now the idea of own responsibility might be a little shaky. :) -Rich DKP == David K Parker

Re: [Mailman-Users] Mailman using REDHAT Powertools RPM

2001-10-08 Thread Rich West
Just to close this out, the cronjobs get installed as part of the RPM installation which explains why it is not on the checklist. -Rich -- Richard Westmailto:[EMAIL PROTECTED] Sr. Systems Administrator Diva - Princeton, NJhttp://www.divatv.com

Re: [Mailman-Users] Sendmail 8.12.1 + MailMan

2001-10-05 Thread Rich West
running under a separate user (other than root), and the differentiation between processes that handle the receiving of mail and the delivering of mail certainly adds to the security of the system. :-) Thanks! -Rich Jon Carnes wrote: On Thursday 04 October 2001 12:03, Rich West wrote

Re: [Mailman-Users] Mailman using REDHAT Powertools RPM

2001-10-05 Thread Rich West
The docs usually get stored in /usr/share/doc/mailman-version.. But, besides that, you really just have to know where the installation is.. It should be installed in /var/mailman if you used the RPM, and the directory tree is essentially the same from there on out. I believe if you do a rpm

Re: [Mailman-Users] Mailman using REDHAT Powertools RPM

2001-10-05 Thread Rich West
Just to get ahead of the game, I didn't write it. :) And this doesn't mention crontabs? I think they just included the core things to get it up and running Does the RPM install really do the right thing? How can it know if I want news gatewaying or not?... Just to clarify: my

[Mailman-Users] Sendmail 8.12.1 + Mailman 2.0.6

2001-10-05 Thread Rich West
I posted recently about my troubles with getting sendmail 8.12.1 and Mailman 2.0.6 to work happily, and, surprisingly, I have managed to make some progress. Right now, the two are working happily together, BUT, mail to any of the lists keeps looping for ever and ever. I watched the qfile

[Mailman-Users] Sendmail 8.12.1 + MailMan

2001-10-04 Thread Rich West
This is going to sound stupid, but, with Sendmail's new MSP configuration, I have been unable to get sendmail + MailMan to work properly. I feel like I am in a catch-22 here: o Configure Defaults.py to use SMTPDirect, and sendmail starts seeing email from list (outgoing to queue members) as