Qmail/MailMan - Crashing Children with no cause.
This is an odd ball error: "deferral: preline:_fatal:_child_crashed/" I'm using mailman as a list agent (ezmlm is nice, buta bit short of my needs) and for some reason when passing info through preline this error pops up in the syslog. However if I pipe the mail message direct to the command itself without preline or qmail, I get a message just fine. the line in the .qmail- file reads: |/var/qmail/bin/preline /usr/local/mailman/mail/wrapper mailcmd timy As much as I would like to say it's all mailmans fault, I can't figure why it would die via only qmail, and not the command line. I'm on Solaris X86 ver 8 Using roaming users, and vchkpwd. Any ideas of things to try or how to debug would be very helpful and appreachiated -Alex
Re: Qmail/MailMan - Crashing Children with no cause.
Search the archives for preline and SIGPIPE. I think you'll find the answer there. Regards. On Mon, Jul 02, 2001 at 03:33:20PM -0700, Alex Hathaway allegedly wrote: This is an odd ball error: deferral: preline:_fatal:_child_crashed/ I'm using mailman as a list agent (ezmlm is nice, but a bit short of my needs) and for some reason when passing info through preline this error pops up in the syslog. However if I pipe the mail message direct to the command itself without preline or qmail, I get a message just fine. the line in the .qmail- file reads: |/var/qmail/bin/preline /usr/local/mailman/mail/wrapper mailcmd timy As much as I would like to say it's all mailmans fault, I can't figure why it would die via only qmail, and not the command line. I'm on Solaris X86 ver 8 Using roaming users, and vchkpwd. Any ideas of things to try or how to debug would be very helpful and appreachiated -Alex
RE: Qmail/MailMan - Crashing Children with no cause.
I don't think that's the problem.. To quote Dan, The next version of preline will work just like a pipe from the shell: it will put the main command in the foreground, and it will die silently if it receives SIGPIPE. ---Dan I even to speculation, used the patch in the archives with still the same result. *pullig heair out* why can appy's just get along? -Original Message- From: MarkD [mailto:[EMAIL PROTECTED]] Sent: Monday, July 02, 2001 4:20 PM To: [EMAIL PROTECTED] Subject: Re: Qmail/MailMan - Crashing Children with no cause. Search the archives for preline and SIGPIPE. I think you'll find the answer there. Regards. On Mon, Jul 02, 2001 at 03:33:20PM -0700, Alex Hathaway allegedly wrote: This is an odd ball error: deferral: preline:_fatal:_child_crashed/ I'm using mailman as a list agent (ezmlm is nice, but a bit short of my needs) and for some reason when passing info through preline this error pops up in the syslog. However if I pipe the mail message direct to the command itself without preline or qmail, I get a message just fine. the line in the .qmail- file reads: |/var/qmail/bin/preline /usr/local/mailman/mail/wrapper mailcmd timy As much as I would like to say it's all mailmans fault, I can't figure why it would die via only qmail, and not the command line. I'm on Solaris X86 ver 8 Using roaming users, and vchkpwd. Any ideas of things to try or how to debug would be very helpful and appreachiated -Alex
Re: Qmail/MailMan - Crashing Children with no cause.
On Mon, Jul 02, 2001 at 04:29:50PM -0700, Alex Hathaway allegedly wrote: I don't think that's the problem.. To quote Dan, The next version of preline will work just like a pipe from the shell: it will put the main command in the foreground, and it will die silently if it receives SIGPIPE. Right. But that next version isn't out yet. Your point is? I even to speculation, used the patch in the archives with still the same result. *pullig heair out* why can appy's just get along? You're being silly. You don't know the reason for your problem, yet when someone offers a solution you dismiss it for no good reason and without even trying it! Sounds like you enjoy *pullig heair out* (sic). Regards. -Original Message- From: MarkD [mailto:[EMAIL PROTECTED]] Sent: Monday, July 02, 2001 4:20 PM To: [EMAIL PROTECTED] Subject: Re: Qmail/MailMan - Crashing Children with no cause. Search the archives for preline and SIGPIPE. I think you'll find the answer there. Regards. On Mon, Jul 02, 2001 at 03:33:20PM -0700, Alex Hathaway allegedly wrote: This is an odd ball error: deferral: preline:_fatal:_child_crashed/ I'm using mailman as a list agent (ezmlm is nice, but a bit short of my needs) and for some reason when passing info through preline this error pops up in the syslog. However if I pipe the mail message direct to the command itself without preline or qmail, I get a message just fine. the line in the .qmail- file reads: |/var/qmail/bin/preline /usr/local/mailman/mail/wrapper mailcmd timy As much as I would like to say it's all mailmans fault, I can't figure why it would die via only qmail, and not the command line. I'm on Solaris X86 ver 8 Using roaming users, and vchkpwd. Any ideas of things to try or how to debug would be very helpful and appreachiated -Alex
Re: qmail + mailman
On Tue, May 29, 2001 at 03:47:11AM +0100, Rodrigo Borges Pereira wrote: Hi! I'm doing some testing with qmail and mailman, and i stumbled into this problem: I have this list with 20 members.. 3 of them have mail accounts on the same machine where i run qmail and mailman. The other 17 are around the internet. Problem is: only the local 3 receive messages posted to the list. Checking logs reveals that qmail completely ignores the other 17. I see qmail happily sending just 3 messages, nothing more. I have had a similar problem. In my case as well, I had never seen a problem before Mailman because all my other local apps sent mail via usr/sbin/sendmail or qmail-inject, and qmail was configured never to relay. Mailman wants to send mail via an SMTP connection to the local machine, so you might want to check if you allow connections from 127.0.0.1 to relay mail. Allowing relaying from localhost solved my problem. Regards, Kyle J.
qmail + mailman
Hi! I'm doing some testing with qmail and mailman, and i stumbled into this problem: I have this list with 20 members.. 3 of them have mail accounts on the same machine where i run qmail and mailman. The other 17 are around the internet. Problem is: only the local 3 receive messages posted to the list. Checking logs reveals that qmail completely ignores the other 17. I see qmail happily sending just 3 messages, nothing more. I'm posting this here because i do not believe this is mailman related, i think it's something with my mail subsystem configuration. I think i should note that i'm using Bruce Guenter's relay-ctrl package too, just in case. Using other programs to send mail to external addresses works just fine (i.e. local pine, users with outlook, etc) What could be the problem here? Thanks in advance.
Re: Qmail + Mailman
Rodrigo Borges Pereira([EMAIL PROTECTED])@2001.05.14 21:29:12 +:
Hello all.
Although this may seem off-topic (regarding mailman) i think the problem
here is more qmail'ish, so i thought of giving a try on this list too.
why bother using mailman? try ezmlm, it works for a lot of real high
volume mailing lists ;-)
(or does mailman have some real features compared to exmlm-idx?)
/k
--
I can emulate the Beta-version of every C #include signal.h
program I've ever written in two lines! - main() {raise(11);}
KR433/KR11-RIPE -- http://www.webmonster.de -- ftp://ftp.webmonster.de
[Key] [KeyID---] [Created-] [Fingerprint-]
GnuPG 0x2964BF46 2001-03-15 42F9 9FFF 50D4 2F38 DBEE DF22 3340 4F4E 2964 BF46
Re: Qmail + Mailman
* Karsten W. Rohrbach (Wed, May 16, 2001 at 05:55:23PM +0200) why bother using mailman? try ezmlm, it works for a lot of real high volume mailing lists ;-) ezmlm is, in my opinion, the way to go if you want to have as little to do with your lists and lists users as possible after you've set up your lists. I really like VERP, it saves me lots of time needed to othervise trying to track down the address users are subscribed as. (or does mailman have some real features compared to exmlm-idx?) For some, the web interface of mailman would be the reason for installing it. If you happen to like web interfaces (many users do), you would have to look long to find something as good as the mailman web interface. I've tried both, and qmail has no problem at all with either of these mailing list managers. -- SSM - Stig Sandbeck Mathisen Trust the Computer, the Computer is your Friend
Qmail + Mailman
Hello all. Although this may seem off-topic (regarding mailman) i think the problem here is more qmail'ish, so i thought of giving a try on this list too. I'm trying to make qmail work together with Mailman. Mailman comes with a python script for the purpose, that is called from a .qmail-default file under /var/mailman (mailman's user home dir), like this: |/user/bin/python /var/mailman/qmail-to-mailman.py. This script is supposed to eliminate the need to create any aliases files for the lists to work. Problem is, after any list created, i am able to receive administrative mail from the list (i.e. welcoming, password reminder, etc) and the addresses look fine, but when i send mail to the list, i see on the logs that qmail complains that it cannot found such mailbox ([EMAIL PROTECTED]), but i do receive mail from testlist-owner and testlist-admin. I created a virtual domain for the lists as u can see (lists.domain.com) and added that domain to rcpthosts and an entry like this to virtualdomains: lists.domain.com:mailman. So, i'm not sure what the problem is and would appreciante some help, if any of you has mailman working with qmail using a virtual domain. (i didn't get any reply about this on the Mailman list :( TIA, Rodrigo Borges Pereira
Re: Qmail + Mailman
Rodrigo Borges Pereira [EMAIL PROTECTED] wrote: I'm trying to make qmail work together with Mailman. Mailman comes with a python script for the purpose, that is called from a .qmail-default file under /var/mailman (mailman's user home dir), like this: |/user/bin/python /var/mailman/qmail-to-mailman.py. This script is supposed to eliminate the need to create any aliases files for the lists to work. Problem is, after any list created, i am able to receive administrative mail from the list (i.e. welcoming, password reminder, etc) and the addresses look fine, but when i send mail to the list, i see on the logs that qmail complains that it cannot found such mailbox ([EMAIL PROTECTED]), but i do receive mail from testlist-owner and testlist-admin. If user joe has a .qmail file named joe-default, it will control mail addressed to joe-foo and joe-bar, but _not_ just joe. His .qmail file named .qmail will control address joe. `man dot-qmail` for details. I suspect that simply symlinking .qmail-default to .qmail will fix your problems. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
RE: Qmail + Mailman
It did not work :( i keep getting this: May 15 01:55:12 picasso qmail: 989906112.543715 info msg 39916: bytes 647 from [EMAIL PROTECTED] qp 3792 uid 101 May 15 01:55:12 picasso qmail: 989906112.555758 starting delivery 21: msg 39916 to local [EMAIL PROTECTED] May 15 01:55:12 picasso qmail: 989906112.555948 status: local 1/10 remote 0/20 May 15 01:55:12 picasso qmail: 989906112.556026 starting delivery 22: msg 39916 to local [EMAIL PROTECTED] May 15 01:55:12 picasso qmail: 989906112.556092 status: local 2/10 remote 0/20 May 15 01:55:12 picasso smtpd: 989906112.557550 tcpserver: end 3790 status 0 May 15 01:55:12 picasso smtpd: 989906112.557754 tcpserver: status: 0/20 May 15 01:55:12 picasso qmail: 989906112.583466 delivery 21: success: did_0+0+0/ May 15 01:55:12 picasso qmail: 989906112.583675 status: local 1/10 remote 0/20 May 15 01:55:12 picasso qmail: 989906112.583753 delivery 22: failure: Sorry,_no_mailbox_here_by_that_name._(#5.1.1)/ getting desperate.. i would use ezmlm-idx.. but it lacks the fabulous web interface that mailman has. -Original Message- From: Charles Cazabon [mailto:[EMAIL PROTECTED]] Sent: segunda-feira, 14 de Maio de 2001 22:28 To: [EMAIL PROTECTED] Subject: Re: Qmail + Mailman Rodrigo Borges Pereira [EMAIL PROTECTED] wrote: I'm trying to make qmail work together with Mailman. Mailman comes with a python script for the purpose, that is called from a .qmail-default file under /var/mailman (mailman's user home dir), like this: |/user/bin/python /var/mailman/qmail-to-mailman.py. This script is supposed to eliminate the need to create any aliases files for the lists to work. Problem is, after any list created, i am able to receive administrative mail from the list (i.e. welcoming, password reminder, etc) and the addresses look fine, but when i send mail to the list, i see on the logs that qmail complains that it cannot found such mailbox ([EMAIL PROTECTED]), but i do receive mail from testlist-owner and testlist-admin. If user joe has a .qmail file named joe-default, it will control mail addressed to joe-foo and joe-bar, but _not_ just joe. His .qmail file named .qmail will control address joe. `man dot-qmail` for details. I suspect that simply symlinking .qmail-default to .qmail will fix your problems. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
Calling all qmail / mailman admins ...
[previously posted to the "mailman users" list] Try as I might, I still don't have qmail and mailman playing nice together. If anyone has pulled this stunt off, or is currently trying to figure it out (like I am), could you please contact me? I'd like to discuss in an offline e-mail thread all the nuances (above and beyond what's in README.QMAIL) and then post what will hopefully be the definitive "steps to configure" for qmail/mailman. Not that I object to discussing it here (I don't) but if it will help keep the signal/noise ratio down ... :-) -- Joe D'Andrea ATT Laboratories
