Qmail won't send to outside addresses [Oops!]

lazloman · Last edited by lazloman on Thu Jul 28, 2005 2:53 am; edited 2 times in total

I solved an earlier problem, but this one has me vexed. When I try to send mail outside my network, the qmail-send/current log shows that qmail-remote crashed. No other explanation is logged. I've looked at all my configuration files and compared them to my current working qmail server and can't find anything wrong. Does anyone have any ideas? Yes, I did look at Life With Qmail.
_________________
Gentoo x86
2x Dell Optiplex GX200

"My Break-Dancing days are over, but there's always the Funky Chicken."
--The Full Monty

skunkworx · Posted: Wed Jan 21, 2004 11:21 pm Post subject:

Can you post the log entries showing qmail-remote crashing, and also your configuration files under /var/qmail/control (except for servercert.cnf and all files ending in .pem, if they exist). Also, which version of the ebuild are you using?

lazloman · Posted: Thu Jan 22, 2004 1:56 am Post subject:

I'm using qmail-1.03-r13

Here the qmail-send log for the last two attempts

@40000000400f25282440922c starting delivery 6: msg 50087 to remote outside@address.com
@40000000400f2528244149c4 status: local 0/10 remote 1/20
@40000000400f25282583726c delivery 6: deferral: qmail-remote_crashed./
@40000000400f252825840eac status: local 0/10 remote 0/20
@40000000400f263625ab8ff4 starting delivery 7: msg 50086 to remote outside@address.com
@40000000400f263625ac478c status: local 0/10 remote 1/20
@40000000400f263626f09314 delivery 7: deferral: qmail-remote_crashed./
@40000000400f263626f12b6c status: local 0/10 remote 0/20

My /var/qmail/control files
conf-common:

# Common Configuration file for all qmail daemons
# $Header: /home/cvsroot/gentoo-x86/net-mail/qmail/files/1.03-r13/conf-common,v 1.1 2003/10/27 09:42:54 robbat2 Exp $

# Qmail User IDS to run daemons as
QMAILDUID=`id -u qmaild`
NOFILESGID=`id -g qmaild`

# Qmail Control Dir (this is actually set in /etc/env.d/99qmail)
#QMAIL_CONTROLDIR=/var/qmail/control

# Host and port to listen on
# We listen on the IPv4 local ip by default
TCPSERVER_HOST=0.0.0.0
TCPSERVER_PORT=${SERVICE}

# you do not need to specify -x, -c, -u or -g in this variable as those are
# added later
TCPSERVER_OPTS="-p -v"

# we limit data and stack segments to 8mbytes, you may need to raise this if
# you are using a filter in QMAILQUEUE
SOFTLIMIT_OPTS="-m 800000000"

# We don't have anything to set QMAILQUEUE to at the moment, so we leave it alone
#QMAILQUEUE=""

# tcpserver maximum concurrency, defaults to 40 in tcpserver
# this controls the maximum number of incoming connections that it will accept
[ -e ${QMAIL_CONTROLDIR}/concurrencyincoming ] && MAXCONN=$(<${QMAIL_CONTROLDIR}/concurrencyincoming) || MAXCONN=40

conf-smtpd:
# Configuration file for qmail-smtpd
# $Header: /home/cvsroot/gentoo-x86/net-mail/qmail/files/1.03-r13/conf-smtpd,v 1.2 2003/11/30 03:00:20 robbat2 Exp $

# Stuff to run before tcpserver
#QMAIL_TCPSERVER_PRE=""
# Stuff to run qmail-smtpd
#QMAIL_SMTP_PRE=""
# Stuff to after qmail-smtpd
QMAIL_SMTP_POST="sage.thethurmans.com"

# this turns off the IDENT grab attempt on connecting
TCPSERVER_OPTS="${TCPSERVER_OPTS} -R"

# You might want to use rblsmtpd with this, but you need to fill in a RBL server here first
# see http://cr.yp.to/ucspi-tcp/rblsmtpd.html for more details
#QMAIL_SMTP_PRE="${QMAIL_SMTP_PRE} rblsmtpd -r blackholes.mail-abuse.org"

# If you are interested in providing POP or IMAP before SMTP type relaying,
# emerge relay-ctrl, then uncomment the next 2 lines
#QMAIL_TCPSERVER_PRE="${QMAIL_TCPSERVER_PRE} envdir /etc/relay-ctrl relay-ctrl-chdir"
#QMAIL_SMTP_PRE="${QMAIL_SMTP_PRE} relay-ctrl-check"
# In /etc/courier-imap/authdaemonrc add the next line to the end:
#authmodulelist="${authmodulelist} relay-ctrl-allow"
# Then in /etc/courier-imap/{imapd,imapd-ssl,pop3d,pop3d-ssl}
# Add this at the end
#PRERUN="${PRERUN} envdir /etc/relay-ctrl relay-ctrl-chdir"

# This next block is for SMTP-AUTH
# This provides the LOGIN, PLAIN and CRAM-MD5 types
# the 'cmd5checkpw' used in $QMAIL_SMTP_AUTHCHECKPASSWORD supports CRAM-MD5
# and reads it's data from /etc/poppasswd
# see the manpage for cmd5checkpw for details on the passwords
# uncomment the next four lines to enable SMTP-AUTH
#QMAIL_SMTP_AUTHHOST=$(<${QMAIL_CONTROLDIR}/me)
#[ -z "${QMAIL_SMTP_POST}" ] && QMAIL_SMTP_POST=/bin/true
#QMAIL_SMTP_CHECKPASSWORD="/bin/cmd5checkpw"
#QMAIL_SMTP_POST="${QMAIL_SMTP_AUTHHOST} ${QMAIL_SMTP_CHECKPASSWORD} ${QMAIL_SMTP_POST}"

defaultdelivery:
# Uncomment the next line for .forward support
#|dot-forward .forward
| spamassassin -P | maildir ./maildir/

defaultdomain:
thethurmans.com

locals:
thethurmans.com
internal.thethurmans.com

me:
thethurmans.com

plusdomain:
thethurmans.com

rcpthosts:
thethurmans.com
internal.thethurmans.com

smtproutes:
internal.thethurmans.com:
:mail.mindspring.com

Thanks for helping
_________________
Gentoo x86
2x Dell Optiplex GX200

"My Break-Dancing days are over, but there's always the Funky Chicken."
--The Full Monty

skunkworx · Posted: Thu Jan 22, 2004 5:24 pm Post subject:

lazloman · Posted: Thu Jan 22, 2004 5:58 pm Post subject:

Thanks for the reply, I'll try what you've suggested and see what happens.

It crashes immediately and no core dump is left.

One thing I should add though, is that since I'm migrating from one machine to another, any appropriate network settings like MX records are still pointing to my current mail server, so if there is anything outside of qmail's config files that might be a factor feel free to add.

Thaks again
_________________
Gentoo x86
2x Dell Optiplex GX200

"My Break-Dancing days are over, but there's always the Funky Chicken."
--The Full Monty

skunkworx · Posted: Thu Jan 22, 2004 7:48 pm Post subject:

Network problems or misconfigurations would cause mail to be deferred or delivered incorrectly, but they wouldn't cause qmail-remote to crash. The qmail executables are pretty solid, usually even under a mountain of patches.

Good luck!

Derringer · n00b Joined: 06 Jan 2004 Posts: 53 Location: Detroit, MI

I'm a fairly seasoned qmail admin in both corporate and private settings and this kind of has me vexed. I'd be very interested in hearing how you fix it when you do, if you wouldn't mind, for future reference.

One of the problems with administering qmail is not entirely evident when you initially set it up... and that is that it is so damn solid that it might be an entire year before you have an issue you have to troubleshoot, and by that time you have forgotten how (hehe, thought a joke was in order).

In all seriousness, I'm unfamiliar with setting it up under Gentoo, but have always done it from source following Life with Qmail in other distributions. Is the Gentoo build patched with the patches to qmailqueue, for instance ?

kashani · Posted: Fri Jan 23, 2004 12:34 am Post subject:

Yep, Gentoo includes all the major patches. As of 1.03-r13 the patches you get by default are

qmailqueue
big-todo
qmail-link-sync
big-concurrency
qmail-0.0.0.0
sendmail-flagf
qmtpc
qmail-smtpd-relay-reject
qmail-local-tabs
qmail-maildir++
qmail-date-localtime
qmail-limit-bounce-size

as well as 7 or 8 more. I'm still running r8 myself as I didn't see the need to get r13 as it mostly adds user type functionality. I'd also install qmhandle and supervise-scripts as well. I do recall having some issues building r10 or r13 recently, but I evenutally got around the problem.

I would recommend trying a different qmail ebuild, such as r8, with much less patches to see if the problems go away. Assuming the problems do disappear, you might try r10 and then r13 to see if you can pin point where things have gone wrong. Also it's not hard to drop some fo the stranger patches out the ebuild. r8 has about the minimum set of patches I recommend using.

kashani
_________________
Will personally fix your server in exchange for motorcycle related shop tools in good shape.

skunkworx · Posted: Fri Jan 23, 2004 5:31 pm Post subject:

Going to an earlier, less-patched ebuild of qmail is a good idea if r13 continues to give problems, but I would recommend going back to r10, not r8. r8 is not compatible with the latest glibc packages (the errno issue for those who know what that means).

I have a complete list of all the patches r13 applies to the qmail sources, with a little bit of explanation about what each one does. This should help anyone who is looking to prune their qmail installation. Go here and scroll down to appendix C.

WHiZZi · n00b Joined: 09 Sep 2003 Posts: 24 Location: Rosmalen City

Sorry for this bump, but it's worth it.

I had the same problem on one of my mailservers with qmail-1.03-r13 while other mailservers (exact the same configuration, except for hostname) just worked flawless.

After a long search on this forum, newsgroups and lots of other places I just couldn't find a solution. So I was preparing to downgrade to r10 and hoping that will work. I was preparing a fall back server in case everything went wrong. While the server was transferring it's configfiles, mailfiles and database I was looking to find a way to start qmail-remote from the command line.. you know, reading man pages..

At this manpage I found the following:

mcj2a · n00b Joined: 28 Feb 2005 Posts: 3

I am getting the same error on my ppc machine...qmail-remote works fine with no smtproutes specified, whereas it dies when there is one. I've gotten an strace running qmail-remote from the command line, but I am not a programmer and I have no idea what this output means...anyone smarter than me have any ideas?

The command line:

lazloman · Posted: Mon Feb 28, 2005 10:32 pm Post subject:

Is still have not solved the problem, but I did find that I can use the qmail-remote binary from r10 with r13, so I keep a copy and then replace the newly compiled one with it.
_________________
Gentoo x86
2x Dell Optiplex GX200

"My Break-Dancing days are over, but there's always the Funky Chicken."
--The Full Monty

mcj2a · n00b Joined: 28 Feb 2005 Posts: 3

paulhart · n00b Joined: 17 Mar 2005 Posts: 2

I'm getting the same problem as previous posters, using r15 on PPC. This is the end of my strace output:

lazloman · Posted: Mon Jun 13, 2005 2:46 pm Post subject:

Unfortunately, I'm still having the same problem. No one responded to my strace post. The helohost fixed noted earlier in the thread did not work for me, so I'm still using the r-10 qmail-remote although technically, I'm running r-15. If find a fix a fix, I'll post back here.
_________________
Gentoo x86
2x Dell Optiplex GX200

"My Break-Dancing days are over, but there's always the Funky Chicken."
--The Full Monty

lazloman · Posted: Tue Jul 26, 2005 2:36 pm Post subject:

This one sure took a while, it was compiler flags. These settings work:

CFLAGS="-O2 -pipe -mmultiple -mstring"

I'm good now.
_________________
Gentoo x86
2x Dell Optiplex GX200

"My Break-Dancing days are over, but there's always the Funky Chicken."
--The Full Monty

lazloman · Posted: Thu Jul 28, 2005 3:09 am Post subject:

Actually, I was wrong about this. The compliler flags did not help. I ended up getting the source for netqmail, compiling the source and using the qmail-remote from there. This one works. It does not have all the patches the portage version has, but it does have a few. From what I can find out about this on the internet, it may be the patches that are the problem, but only time will tell. Anyway, after making sure things were working this time, I ran an strace of the working qmail-remote and compared it to the bad version (posted earlier). Here's the output from that. If you compare the two, you see the failed version seg faults just after a call to getpid() which to appears to return successfully. Maybe one day I'll take a look at the source and see if I can find the problem.

SweepingOar · Apprentice Joined: 31 Dec 2003 Posts: 263 Location: LA

I had this problem and this message seems to have fixed it, but only for one day! For newbies like me, here is the only thing I did:

lazloman · Posted: Thu Oct 20, 2005 2:13 am Post subject:

I tried this myself and it did not work. I have both "me" amd "helohost" with the same contents.
_________________
Gentoo x86
2x Dell Optiplex GX200

"My Break-Dancing days are over, but there's always the Funky Chicken."
--The Full Monty

SweepingOar · Apprentice Joined: 31 Dec 2003 Posts: 263 Location: LA

Sorry, yeah, it only worked for us for a day! I edited that post so as to not give out false hope anymore. I don't know what to do. Developers, gurus veterans, please help!

SweepingOar · Apprentice Joined: 31 Dec 2003 Posts: 263 Location: LA

You also might want to look at this thread I started. One of the veterans suggested a simple fix that appears to have worked.

https://forums.gentoo.org/viewtopic-p-2818055.html
_________________
-SweepingOar

lazloman · Posted: Sat Oct 22, 2005 4:30 am Post subject:

Thanks, I just re merged QMail without SSL support and it seems to be just fine.
_________________
Gentoo x86
2x Dell Optiplex GX200

"My Break-Dancing days are over, but there's always the Funky Chicken."
--The Full Monty