[Mailman-Users] Mailman + Sendmail
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 down the source of the problem. Essentially, we have users A, B, C, and D. AB have accounts local to the mailman/mail server and CD have accounts elsewhere. Now, when any user emails to the list, mailman receives the message, then spawns off 4 (right now, I have nodupes deselected for everyone) messages in the sendmail queue. If sendmail had just recently been started (aka: within the past 5 minutes), the message will go through just fine. However, in most cases, the messages (all with the same message ID) hang in the queue forever.. or, at least, until sendmail gets restarted at which time all of the messages get delivered. At this point, one would say It's sendmail, as did I. I dug, and dug, but could not repeat the scenario without mailman in the loop. I could send email to each user directly, I could create an alias called 'test' with each of the users in the alias, and then have any one of them mail to test to have it successfully send that out to everyone. I looked in the logs on mailman, and saw nothing out of the ordinary. I'm pretty much at a loss as to where else to turn. I tried deleting the list and re-adding it, I tried deleting the list and creating one under a different name.. I tried upgrading to Mailman 2.1.6. So far, everything is consistent. I was thinking of trying to set mailman to send only one message per connection or something just to see if the other messages would process and just leave the hanging ones out there (not sure how to set this, though). I searched the archives, too, but didn't have much luck there as I was not sure how to narrow down the search enough (I couldn't come up with good search terms). Any ideas/help/pointers would be much appreciated! Thanks! -Rich -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Mailman + Sendmail
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 mailman log: Sep 12 20:53:28 2005 (24387) Low level smtp error: (4, 'Interrupted system call'), msgid: [EMAIL PROTECTED] So.. that got me thinking that Mailman was somehow not ending the connection properly OR that my sendmail install really didn't like handling multiple messages in one stream (I'm blanking as to why). With all of that in mind, I set : SMTP_MAX_SESSIONS_PER_CONNECTION = 1 MAX_DELIVERY_THREADS = 0 SMTP_MAX_RCPTS = 1 And things started working. Odd.. Now, I know that this is definitely NOT ideal or optimal.. But, what could be going wrong? I tried reducing the SMTP_MAX_SESSIONS_PER_CONNECTION to 0 for my tests, and the problem crept back. I moved that back to 1, then set SMTP_MAX_RCPTS to 0, and the problem crept back. Only the config above seemed to work.. My mind is a jumbled mess thinking about this, but if anyone has any ideas.. I'm all ears. :) -Rich 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 down the source of the problem. Essentially, we have users A, B, C, and D. AB have accounts local to the mailman/mail server and CD have accounts elsewhere. Now, when any user emails to the list, mailman receives the message, then spawns off 4 (right now, I have nodupes deselected for everyone) messages in the sendmail queue. If sendmail had just recently been started (aka: within the past 5 minutes), the message will go through just fine. However, in most cases, the messages (all with the same message ID) hang in the queue forever.. or, at least, until sendmail gets restarted at which time all of the messages get delivered. At this point, one would say It's sendmail, as did I. I dug, and dug, but could not repeat the scenario without mailman in the loop. I could send email to each user directly, I could create an alias called 'test' with each of the users in the alias, and then have any one of them mail to test to have it successfully send that out to everyone. I looked in the logs on mailman, and saw nothing out of the ordinary. I'm pretty much at a loss as to where else to turn. I tried deleting the list and re-adding it, I tried deleting the list and creating one under a different name.. I tried upgrading to Mailman 2.1.6. So far, everything is consistent. I was thinking of trying to set mailman to send only one message per connection or something just to see if the other messages would process and just leave the hanging ones out there (not sure how to set this, though). I searched the archives, too, but didn't have much luck there as I was not sure how to narrow down the search enough (I couldn't come up with good search terms). Any ideas/help/pointers would be much appreciated! Thanks! -Rich -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Posts Not Going Through
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 smtp-failure and should give you, at the very least, a starting point. -Rich Joseph A. Nagy, Jr. wrote: I know my MTA works, you folks get all my mail, my question is, why all ofa sudden mail to my mailman lists is not going through, not even mail from myself (my mail acocunt is on the same machine as the list). The first dozen or so posts went through and then *poof* no more deliveries. One post finally went through a little over 12 hours after it was sent and now nothing. ): -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Posts Not Going Through
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 PROTECTED]
s': (550, 'Verification failed for
[EMAIL PROTECTED]\nUnk
nown user\nSender verify failed')}, msgid:
mailman.0.1097153842.21728.rifts-pbe
[EMAIL PROTECTED]
Oct 07 07:57:24 2004 (6344) delivery to [EMAIL PROTECTED] failed
with
code 550: Verification failed for [EMAIL PROTECTED]
Unknown user
Sender verify failed
which is wrong because it's included in my alias file.
*nod* However, that does tend to lead to a MTA (sendmail, postfix, etc)
error as opposed to a problem with Mailman. You may want to confirm
your settings in Mailman/mm_cfg.py with regards to your mailhost and such.
What mail server software are you running? And does it reside on the
same, or different, machine?
There is no maillog file.
Not sure where gentoo would put it, but you might have to check in your
/etc/syslog.conf to see where it puts all of the mail.* notifications,
and then check that file to see what is being logged there.
I'm still as lost. Here's the relevant entries for that file:
The aliases look good (I see you're not using smrsh with your email
server). You're actually not as lost as you think you are.. at least
you know that mailman is trying to send the emails, but failing
miserably. Now you need to dig through and find out why its
communication with the mail server is failing.. The mail server logs
should help you there..
-Rich
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Odd smtp-error
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, daemon=MTA, relay=localhost [127.0.0.1] The above envelope from is VERP like. ..snip.. Weird.. I never had to alter [the value of SMTP_MAX_SESSIONS_PER_CONNECTION] before... Will that have a negative impact on things in any way?! Yes, but not too much. The VERP like address above is used for enhanced bounce detection and is controlled by VERP_DELIVERY_INTERVAL and other options. I went through the Defaults.py file and read up on VERP to get better acquainted. :) ..snip.. This is the big performance hit with VERP like envelope from because the message text must be repeated for each recipient as opposed to non-personalized, non-VERP which may have just one MAIL FROM:, a bunch of RCPT TO: and one DATA. In your case, setting SMTP_MAX_SESSIONS_PER_CONNECTION = 1 takes the above SMTP session with multiple transactions and puts QUIT, get disconnected, reconnect, EHLO between each message. This adds some impact, but not alot compared to the impact of doing the VERP like addressing at all...snip.. It seems like there is some problem with your MTA accepting multiple transactions per session or possibly with the way Mailman sends them. Possibly.. I went looking through my mm_cfg.py and, at the end, the following VERP options had been enabled: VERP_PASSWORD_REMINDERS = 1 VERP_PERSONALIZED_DELIVERIES = 1 VERP_DELIVERY_INTERVAL = 1 VERP_CONFIRMATIONS = 1 Basically, everything was turned on. For sanity sake with regards to the testing, I set the value for SMTP_MAX_SESSIONS_PER_CONNECTION back to 0 in the Defaults.py file (since I really should have set it in mm_cfg.py anyhow), commented out the above values in the mm_cfg.py, recompiled, restarted mailman, and shot off a test email. It came through with no problems. So, I guess it is a toss up as to having VERP enabled with one SMTP connection per transaction or disabling VERP and setting the SMTP max sessions per connection to 0 (unlimited)... Recommendations/suggestions? :) -Rich -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] Mailman under Fedora Core 2
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
installation.
Our installation is pretty vanilla, and it handles about 30+ lists with
some lists having low membership and others having hundreds of addresses.
Anyhow, on the FC1 machine, everything ran fine since we rolled that in
to production back in January of this year, and previously, under RedHat
9, things ran seamlessly as well.
Since we have upgraded to Fedora Core 2, we're getting some odd problems
that are just frustrating the living daylights out of me.
The problem shows itself when we get a report of no activity on any of
the lists. Quick investigation shows that /var/mailman/qfiles/out is
full of pending messages. Unsure as to why they are pending, we quickly
restart the mailman daemon. Unfortunately, two of the processes don't
die (mailmanctl -s start and OutgoingRunner), so they have to be
killed manually. Bringing mailman back on-line begins the processing
again, but I am not certain that it is even processing correctly.
On our test list, it does seem to send to *some* of the test users, but
not all.
The smtp-error log periodically shows a gazillion Low level SMTP error:
(111, 'Connection refused') messages followed by a gazillion Low level
smtp error: please run connect()first and finally a gazillion delivery
to emailaddress failed with code -1: please run connect() first
I've gone through and insured that my mm_cfg.py contained all of the
right information, and I have even gone through the effort to compile it
up (not sure if this is even necessary, but I am running out of ideas)
via : python -c import compileall;
compileall.compile_dir('/var/mailman/Mailman', ddir='/var/mailman/Mailman')
The mail server is working fine for all other types of delivery
(confirmed easily). I'm at a complete loss at this point.. Is there any
way to turn up the debugging information to see what host it is getting
the Connection refused message from?
Also, I'm monitoring the qfiles/out directory.. I've been watching it
for about a half hour and have watched the directory's contents
continually grow after a fresh restart of mailman. It just doesn't seem
to send. :(
Argh! Totally frustrating as we never had any problems with mailman
before.. Any help, ideas, comments, etc, would be wonderful!!
-Rich
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] Odd smtp-error
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 PROTECTED] failed with
code 550: 5.1.1 [EMAIL PROTECTED]... User unknown
Oct 22 12:18:22 2004 (4223) All recipients refused:
{'[EMAIL PROTECTED]': (550, '5.1.1 [EMAIL PROTECTED]... User
unknown')}, msgid: [EMAIL PROTECTED]
Oct 22 12:18:22 2004 (4223) delivery to [EMAIL PROTECTED] failed with
code 550: 5.1.1 [EMAIL PROTECTED]... User unknown
Now, that is just plain strange since that is *my* account. :) And it
is (and has been for a LONG time) defined in /var/mail/virtusertable...
Weird.. any ideas as to why that is popping up?
-Rich
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Odd smtp-error
Like I said, it works fine via smtp and the only app complaining is
mailman. :)
I don't know how to 'turn up' the logging on mailman in order to dig
further to see what it is doing..
Also, the email you sent was direct, via SMTP, to the server.. the same
server that mailman sits 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]
Doesn't look like a mailman problem,
looks like a smtp problem.
I tried sending directly to this account
via smtp, and it worked fine.
Will need more verbose logging to figure this
out.
Are you sending via the correct relay (wesmo.com)
?
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Mailman under Fedora Core 2
Using Sendmail, SMTPDirect, on the same machine as mailman.. nothing
logged in /var/log/maillog aside from normal email processing.. And
nothing in /var/log/messages, and plenty of disk space all around..
All of our mailman logs are in /var/mailman/logs, and that's my only
indication of the problems I attached initially..
However.. I did find something of interest. It seems that the major
backlog of messages I had were about 80-100 bogus messages. What I
mean, is that they were all dated about 3-5 months old. I removed them
completely (they kept appearing in the out directory, then they would
get moved to the shunt directory, then back again depending upon
restarts).
Additionally, I set up Nagios to monitor the number of items in the
out directory just to see if anything gest hung.. things look good so
far..
-Rich
Did you look for errors in /var/log/maillog?
Which SMTP method are you using in mailman? Direct?
What is your MTA? Is it local?
Did you look for errors in /var/log/messages?
I assume you looked at all the log files in /var/log/mailman, including
the errors log, other than what you saw in the smtp log did you see
anything else?
Do you have disk space 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 have had continual problems with our mailman
installation.
Our installation is pretty vanilla, and it handles about 30+ lists with
some lists having low membership and others having hundreds of addresses.
Anyhow, on the FC1 machine, everything ran fine since we rolled that in
to production back in January of this year, and previously, under RedHat
9, things ran seamlessly as well.
Since we have upgraded to Fedora Core 2, we're getting some odd problems
that are just frustrating the living daylights out of me.
The problem shows itself when we get a report of no activity on any of
the lists. Quick investigation shows that /var/mailman/qfiles/out is
full of pending messages. Unsure as to why they are pending, we quickly
restart the mailman daemon. Unfortunately, two of the processes don't
die (mailmanctl -s start and OutgoingRunner), so they have to be
killed manually. Bringing mailman back on-line begins the processing
again, but I am not certain that it is even processing correctly.
On our test list, it does seem to send to *some* of the test users, but
not all.
The smtp-error log periodically shows a gazillion Low level SMTP error:
(111, 'Connection refused') messages followed by a gazillion Low level
smtp error: please run connect()first and finally a gazillion delivery
to emailaddress failed with code -1: please run connect() first
I've gone through and insured that my mm_cfg.py contained all of the
right information, and I have even gone through the effort to compile it
up (not sure if this is even necessary, but I am running out of ideas)
via : python -c import compileall;
compileall.compile_dir('/var/mailman/Mailman', ddir='/var/mailman/Mailman')
The mail server is working fine for all other types of delivery
(confirmed easily). I'm at a complete loss at this point.. Is there any
way to turn up the debugging information to see what host it is getting
the Connection refused message from?
Also, I'm monitoring the qfiles/out directory.. I've been watching it
for about a half hour and have watched the directory's contents
continually grow after a fresh restart of mailman. It just doesn't seem
to send. :(
Argh! Totally frustrating as we never had any problems with mailman
before.. Any help, ideas, comments, etc, would be wonderful!!
-Rich
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Odd smtp-error
I *think* I might have found my problem.. :)
After doing some searching in /var/log/messages, I came across that
particular message ID, and saw the corresponding DSN error.
I then hit the net searching with regards to the DSN error, and came
across a number of postings suggesting that a hostname might be missing
from the local-host-names file with regards to sendmail.
I checked mine, and low-and-behold, the name of my mailing list server
that I defined in my mm_cfg.py file was NOT there. duh.
I'm going to keep a close eye on it, but I think I'm ok now..
Thanks to all for your help!
-Rich
Like I said, it works fine via smtp and the only app complaining is
mailman. :)
I don't know how to 'turn up' the logging on mailman in order to dig
further to see what it is doing..
Also, the email you sent was direct, via SMTP, to the server.. the
same server that mailman sits 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]
Doesn't look like a mailman problem,
looks like a smtp problem.
I tried sending directly to this account
via smtp, and it worked fine.
Will need more verbose logging to figure this
out.
Are you sending via the correct relay (wesmo.com)
?
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Mailman + htDig
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 search form, get inserted into the list TOC page. This line should have been inserted into archtoc.html by the htdig-2.1.2-0.4.patch One possibility is that you may be using site, host or list specific templates and you generated these from the standard installed templates before applying the mailman-htdig and kindred patches. If so then these will not have been/could not be patched by the htdig-2.1.2-0.4.patch. In this case you will have to take a look at the htdig-2.1.2-0.4.patch file for the template changes made by the patch and apply these by hand to your local variants of the templates. The patch file is a unified diff format and quite human legible. Wait a sec... if I am reading that correctly, then existing lists would have been created using the standard templates which did not, obviously, have the htdig patch. Newly created lists would be created against the now-patched htdig templates, and they should work properly. Existing lists would have to have their templates patched accordingly. Is that right? If so, then it is likely that my installation IS working as expected. I will have to delete my test list and recreate it, then run some tests and observe the results. I'll let you know if I have any troubles there. Thanks for your help!! -Rich -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mailman + htDig
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 files
in any of these per list directories?
Yes, all of that did get created.
and if I manually perform a search (htsearch -c blah)
While htsearch is used for index searching, it is not called directly
from the form on the list TOC page with the integration but via the
$prefix/Mailman/Cgi/mmsearch.py script.
When you run htsearch -c are you specifying the configuration file
path as:
$prefix/archives/private/listname/htdig/listname.conf
Yes.
, I do get output and results.
How have the search indexes being used by htsearch when you run it by
hand been built? Did you run nightly_htdig by hand?
Yes.
What form do the URLs of search hits in the response returned by
htsearch take?
Well, they look like:
htsearch -c htdig/test.conf
Enter value for words: test
Content-type: text/html
Enter value for format:
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.0 Transitional//EN
htmlheadtitleSearch results for 'test'/title/head
body bgcolor=#eef7ff
snip
hr noshade size=1
img src=/htdig/star.gif alt=*img src=/htdig/star.gif
alt=*img src=/htdig/star.gif alt=*img src=/htdig/star.gif
alt=* stronga
href=http://lists.wesmo.com/mailman/htdig/test/2003-August/29.html;[Test]
test /a/strongbr
snip
However, I am not getting the search form at the top of the
index.html page as is supposed to happen. So, as expected, I cannot
search via the web interface. :(
The trigger for this form to be added to a list's archive TOC page is
a new message being sent to that particular list. And until
nightly_htidg has been run (which can be done from the command lien
as well as by cron) no per-list search indexes will be in existence.
Are these criteria being met and yet still the form does not appear
on a list's archive TOC page?
Yes. I first added the following to my mm_cfg.py:
USE_HTDIG = 0# 0 - don't use integrated htdig, 1 - use it
HTDIG_FILES_URL = '/htdig/'
HTDIG_CONF_LINK_DIR = os.path.join(VAR_PREFIX, 'archives', 'htdig')
HTDIG_HTSEARCH_PATH = '/usr/bin/htsearch'
HTDIG_RUNDIG_PATH = '/usr/bin/rundig'
Then I changed USE_HTDIG to 1 and restarted the qrunner (just for the
sake of sanity. :). I then sent a message to the test list. At once I
got the message that was sent to the test list, I checked out the
archives/private/test directory and saw that the timestamp on index.html
was updated, that a directory called htdig was created, and there were a
bunch of files (db.*, rundig_last_run, and test.conf) in that htdig
directory.
Does line 757 (or thereabouts) of
$prefix/Mailman/Archiver/HyperArch.py contain the following text:
d[htsearch] = quick_maketext('TOC_htsearch.html', dict=h,
This is the code that generates the form that is added to the html of
the list's TOC page a few lines further on. If this line is missing
then the patching has failed somehow.
I just checked, and it is there. Is the TOC_htsearch.html file supposed
to be in a particular location? It is in templates/en/ right now...
I *believe* I followed the htdig docs to the letter,
Do you mean the INSTALL.htdig-mm document in the Mailman build
directory?
Yup.. that, and the docs on the website.
I swear it seems like I missed something simple (and stupid) here.. I
even confirmed that the permissions on the directory and all files were
set correctly (owner group, too!).
Thanks!
-Rich
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Mailman + htDig
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 : http://www.openinfo.co.uk/mailman/patches/728836/templates-2.1.2-0.1.patch http://www.openinfo.co.uk/mailman/patches/732366/tz-2.1.2-0.2.patch http://www.openinfo.co.uk/mailman/patches/730769/tcache-2.1.2-0.3.patch http://www.openinfo.co.uk/mailman/patches/444879/indexing-2.1.2-0.1.patch http://www.openinfo.co.uk/mailman/patches/444884/htdig-2.1.2-0.4.patch And all were applied happily. The indexing appears to be happening correctly on the filesystem level since the htdig directory is being created, the conf file is being created, and if I manually perform a search (htsearch -c blah), I do get output and results. However, I am not getting the search form at the top of the index.html page as is supposed to happen. So, as expected, I cannot search via the web interface. :( The index.html file *IS* being updated, but nothing is getting added to it (no search form)... I *believe* I followed the htdig docs to the letter, but it seems as if I am still missing something. Any help would be much appreciated! Thanks! -Rich -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mailman + htDig
Ok.. I think I know what I did.. I didn't restart the qrunner. As I wrote the previous email to you, I realized that I had _thought_ about restarting the qrunner, but didn't. I went through the whole process again: o Edit mm_cfg.py to set USE_HTDIR=1 o python -c 'from compileall import *; compile_dir(prefix/Mailman,10,prefix/Mailman)' o /etc/init.d/mailmanctrl restart o bin/rmlist test o bin/newlist test o bin/arch test o Entered additional recipients via the web interface. o Sent a test message to the test list o /usr/bin/python -S prefix/cron/nightly_htdig -v test (it complained about not having the centralized db files, but that seemed ok) o Pointed my browser at the test archives, and viola! The search ability was there! And searching worked! I'm not sure if it was the fact that I recompiled the mm_cfg.py file or restarting the qrunner which started things working, 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, ran arch test, and sent a message to the list. It seems likeit does everything BUT create update the index.html file with the search info.. Perhaps I should start over from scratch... -Rich Wait a sec... if I am reading that correctly, then existing lists would have been created using the standard templates which did not, obviously, have the htdig patch. Newly created lists would be created against the now-patched htdig templates, and they should work properly. Existing lists would have to have their templates patched accordingly. Is that right? If so, then it is likely that my installation IS working as expected. I will have to delete my test list and recreate it, then run some tests and observe the results. I'll let you know if I have any troubles there. Thanks for your help!! -Rich -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] RPM/SRPM for Mailman 2.1
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: ftp://ftp.wesmo.com/pub/redhat/SRPMS/mailman-2.1-1.src.rpm Note that it will NOT automatically upgrade your lists, nor will it replace the existing crontab file (if found). Follow the instructions within the UPGRADING file (included from the source distribution of mailman). Enjoy! -Rich -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Upgrade to 2.1 with Sendmail not mailing to list?
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 lists for a variety of domains. After upgrading on our test machine (same exact configuration as the production box), changing the smrsh lins to point to the renamed wrapper mailman, disabling the old qrunner, and starting up the queue runner daemon, it appears that emails TO the list work just fine. However, email FROM the list out to the recipients doesn't happen. For example, I mail into the list as a non-subscribed user. I go to the web interface, and select approve. The very next entry in the sendmail logs is: Jan 2 11:44:15 testserv sm-mta[29018]: h02GiFBO029018: localhost [127.0.0.1] did not issue MAIL/EXPN/VRFY/ETRN during connection to MTA And then nothing.. no email, nothing. So, I try it as a subscribed user, and I immediately get a message in the sendmail logs as above. I combed through the instructions to no avail. Any ideas would be much appreciated! Thanks! -Rich -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mailman rpm for RedHat 7.3?
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 [EMAIL PROTECTED] writes: DKP Is there a packaged rpm for RedHat 7.3 for Mailman 2.1? If someone wants to build and contribute one, and own responsibility for it, I'll be happy to add it as a file download on SF. -Barry -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mailman using REDHAT Powertools RPM
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 Dan Mick wrote: Regardless, if it presents a checklist of things you have to do other than the RPM installation, clearly that checklist needs to include set up cron for Mailman, as Mailman will be a brick without it. -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] Sendmail 8.12.1 + MailMan
Actually, I use /etc/mail/access rather heavily (see http://www.freshmeat.net/projects/spaminator as a rudimentary example to how much I use it.), and, although I tinkered around with it to get Mailman to work via SMTPDirect, it seemed to constantly ignore whatever I put in there regarding Mailman. It is almost as if Mailman were re-writing the headers in such a way as to fool Sendmail into checking the _recipient_ of the email to see if they can relay through us.. Enough so as to make my brain hurt thinking about it. I would be interested to see what others have done in their access file or sendmail config to make everything behave.. Oh, and, yes, Sendmail 8.12.x looks like a fantastic upgrade. I have been running it on a development machine for a week and a half now (upgrading to 8.12.1 only last night) and the additional feature/configuration options regarding 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: 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 being 'from' the list member, and, hence, sendmail denies it because it looks like spam (aka: the sender is not a local user) o Configure Defaults.py to use Sendmail, although non-secure, it worked under 8.11.x without any hitches. Now, using the MSP aspect of the latest sendmail, I get: I haven't up to the grade of 8.12 yet, but I hear folks are having a great time and I should step up soon... Have you looked at playing with the /etc/mail/access file to allow relaying for your Mailman install? In the past that has allowed folks to open up relaying for a their installs. Good Luck - Jon Carnes -- -- Richard Westmailto:[EMAIL PROTECTED] Sr. Systems Administrator Diva - Princeton, NJhttp://www.divatv.com -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] Mailman using REDHAT Powertools RPM
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 -qi mailman there will be instructions as to what to do next. For example: # rpm -qi mailman Name: mailman Relocations: (not relocateable) Version : 2.0.6 Vendor: (none) Release : 1 Build Date: Fri 31 Aug 2001 03:06:19 PM EDT Install date: Fri 31 Aug 2001 03:06:42 PM EDT Build Host: lobe Group : Applications/Internet Source RPM: mailman-2.0.6-1.src.rpm Size: 2123729 License: GPL URL : http://www.list.org/ Summary : Mailing list manager with built in web access. Description : Mailman is software to help manage email discussion lists, much like Majordomo and Smartmail. Unlike most similar products, Mailman gives each mailing list a web page, and allows users to subscribe, unsubscribe, etc. over the web. Even the list manager can administer his or her list entirely from the web. Mailman also integrates most things people want to do with mailing lists, including archiving, mail - news gateways, and so on. When the package has finished installing, you will need to: * Run /var/mailman/bin/mmsitepass to set the mailman administrator password. * Edit /var/mailman/Mailman/mm_cfg.py to customize mailman's configuration for your site. * Modify the sendmail configuration to ensure that it is running and accepting connections from the outside world (to ensure that it runs, set DAEMON=yes in /etc/sysconfig/sendmail, ensuring that it accepts connections from the outside world may require modifying /etc/mail/sendmail.mc and regenerating sendmail.cf), and * Add these lines: ScriptAlias /mailman/ /var/mailman/cgi-bin/ Alias /pipermail/ /var/mailman/archives/public/ Directory /var/mailman/archives Options +FollowSymlinks /Directory to /etc/httpd/conf/httpd.conf to configure your web server. Users upgrading from previous releases of this package may need to move their data or adjust the configuration files to point to the locations where their data is. Denis Croombs wrote: Hi I have installed Mailman from the Powertools CD, it installed OK, but I can find no documentation or man entry to tell me what to do next, has anyone installed it that way and if so what do I do next. I can find plenty of data if I install it from a tarball but not from rpm. Many thanks Denis Croombs -- Richard Westmailto:[EMAIL PROTECTED] Sr. Systems Administrator Diva - Princeton, NJhttp://www.divatv.com -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] Mailman using REDHAT Powertools RPM
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 understanding is that the primary purpose of an RPM is to simply install the package and keep track of all of the files associated to the package (plus other organizational things too, as well as other aspects that are off-topic) . The Admin is still left to configure it via /var/mailman/Mailman/Defaults.py, check out the docs at www.lists.org, check mailing lists, etc, etc. (essentially, the admin has to educate themselves about the app) It certainly is not 100% automated (gawd, I hope not. :).. -Rich -- Richard Westmailto:[EMAIL PROTECTED] Sr. Systems Administrator Diva - Princeton, NJhttp://www.divatv.com -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] Sendmail 8.12.1 + Mailman 2.0.6
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 directory and watched as the number of files in the directory grew exponentially. I had to remove the files by hand for it to stop.. Initially I thought it might be a permission problem within the qfiles directory, but that just wasn't the case.. it turns out that Mailman's sendmail delivery method (defined within Defaults.py) no longer works under Sendmail 8.12.x. Because of changes with Sendmail 8.12.x, it now behaves almost exactly as if I defined SMTPDirect. So, I figured I would pose the question: How do I get Mailman to work with SMTPDirect and Sendmail? I'm not sure if it is a config problem within sendmail (not relaying the email sent from localhost or something) or a problem with Mailman. I suspect the latter because other apps, like Request Tracker (which uses the same delivery method as Mailman's sendmail) seem to work properly... Just an FYI, but Sendmail + MailMan (using sendmail delivery mode) does work for Sendmail 8.11.6. Sendmail + Mailman (using either delivery mode) does NOT work for Sendmail 8.12.1. I backed down to 8.11.6 for now, but I would love to get the two problems (SMTPDirect and Sendmail 8.12.x) cleared up.. Any help/direction would be much appreciated. Thanks! -Rich An excerpt from the sendmail log shows: Oct 4 21:12:44 cranium sm-mta[30876]: f951Chtw030875: to=|/var/mailman/mail/wrapper post test, ctladdr=[EMAIL PROTECTED] (8/0), delay=00:00:01, xdelay=00:00:01, mailer=prog, pri=30270, dsn=2.0.0, stat=Sent Oct 4 21:13:01 cranium sendmail[30885]: f951D1pI030885: Authentication-Warning: cranium.wesmo.com: mailman set sender to [EMAIL PROTECTED] using -f Oct 4 21:13:01 cranium sendmail[30885]: f951D1pI030885: [EMAIL PROTECTED], size=383, class=-60, nrcpts=3, msgid=[EMAIL PROTECTED], relay=mailman@localhost Oct 4 21:13:02 cranium sm-mta[30886]: STARTTLS=server, relay=IDENT:mailman@localhost [127.0.0.1], version=TLSv1/SSLv3, verify=NO, cipher=EDH-RSA-DES-CBC3-SHA, bits=168/168 Oct 4 21:13:02 cranium sendmail[30885]: STARTTLS=client, relay=localhost, version=TLSv1/SSLv3, verify=FAIL, cipher=EDH-RSA-DES-CBC3-SHA, bits=168/168 Oct 4 21:13:02 cranium sm-mta[30886]: f951D1tx030886: ruleset=check_rcpt, arg1=[EMAIL PROTECTED], relay=IDENT:mailman@localhost [127.0.0.1], reject=550 5.7.1 [EMAIL PROTECTED]... Relaying denied. Proper authentication required. Oct 4 21:13:02 cranium sendmail[30885]: f951D1pI030885: [EMAIL PROTECTED], [EMAIL PROTECTED] (41/41), delay=00:00:01, xdelay=00:00:01, mailer=relay, pri=199170, relay=localhost [127.0.0.1], dsn=5.7.1, stat=User unknown Oct 4 21:13:02 cranium sm-mta[30886]: f951D1tx030886: from=[EMAIL PROTECTED], size=383, class=-60, nrcpts=1, msgid=[EMAIL PROTECTED], proto=ESMTP, daemon=MTA, relay=IDENT:mailman@localhost [127.0.0.1] Oct 4 21:13:02 cranium sendmail[30885]: f951D1pI030885: [EMAIL PROTECTED],[EMAIL PROTECTED], [EMAIL PROTECTED] (41/41), delay=00:00:01, xdelay=00:00:01, mailer=relay, pri=199170, relay=localhost [127.0.0.1], dsn=2.0.0, stat=Sent (f951D1tx030886 Message accepted for delivery) Oct 4 21:13:02 cranium sendmail[30885]: f951D1pI030885: f951D1pJ030885: DSN: User unknown Oct 4 21:13:02 cranium sm-mta[30888]: f951D1tx030886: to=[EMAIL PROTECTED], delay=00:00:00, xdelay=00:00:00, mailer=local, pri=138411, dsn=2.0.0, stat=Sent Oct 4 21:13:02 cranium sm-mta[30886]: f951D1u1030886: from=, size=2629, class=0, nrcpts=1, msgid=[EMAIL PROTECTED], proto=ESMTP, daemon=MTA, relay=IDENT:mailman@localhost [127.0.0.1] Oct 4 21:13:02 cranium sendmail[30885]: f951D1pJ030885: [EMAIL PROTECTED], delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=30100, relay=localhost [127.0.0.1], dsn=2.0.0, stat=Sent (f951D1u1030886 Message accepted for delivery) -- Richard West mailto:[EMAIL PROTECTED]Got TV? Wesmo Computer Serviceshttp://www.wesmo.com Get your .TV! Full Domain Registration Services For As Little As $14.95/yr! .BIZ .INFO Registrations Available NOW! -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] Sendmail 8.12.1 + MailMan
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 being 'from' the list member, and, hence, sendmail denies it because it looks like spam (aka: the sender is not a local user) o Configure Defaults.py to use Sendmail, although non-secure, it worked under 8.11.x without any hitches. Now, using the MSP aspect of the latest sendmail, I get: sendmail[13379]: NOQUEUE: SYSERR(mailman): can not write to queue directory /var/spool/clientmqueue/ (RunAsGid=0, required=26): Permission denied Ack.. this should be easy.. I've been handling sendmail for nearly 9 years, and it seems like I am just missing something obvious here.. :) Obviously, I would like to use SMTPDirect over 'Sendmail', so.. how can I get that to behave properly? Any pointers or help would be MUCH appreciated.. My forehead is beginning to hurt from banging it into the desk. I'm not on the mailing list yet, so please send replies directly to me and CC the list.. Thanks! -Rich -- Richard Westmailto:[EMAIL PROTECTED] Sr. Systems Administrator Diva - Princeton, NJhttp://www.divatv.com -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
