From zmailer-owner@nic.funet.fi Sat Jan 31 01:33:12 2009
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S84390AbZA3XdFVuVfI (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Sat, 31 Jan 2009 01:33:05 +0200
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S84396AbZA3XdFQ4Fq4
	(ORCPT <rfc822;zmailer-outgoing>); Sat, 31 Jan 2009 01:33:05 +0200
Received: from mail.Morgan-Systems.com ([204.16.172.8]:45683 "EHLO
	mail.morgan-systems.com" rhost-flags-OK-OK-OK-OK) by nic.funet.fi
	with ESMTP id S84390AbZA3XdEkeqrk (ORCPT
	<rfc822;zmailer@nic.funet.fi>); Sat, 31 Jan 2009 01:33:04 +0200
Received: from Server-16.MorganSys.net ([10.30.1.16]:6170 "HELO
	Mail.Morgan-Systems.com" whoson: "-unregistered-" smtp-auth: <none>
	TLS-CIPHER: <none> TLS-PEER-CN1: <none> rhost-flags-OK-OK-OK-FAIL)
	by Mail.Morgan-Systems.com with SMTP id S1049898AbZA3Xcd convert rfc822-to-8bit
	(ORCPT <rfc822;zmailer@nic.funet.fi>);
	Fri, 30 Jan 2009 15:32:33 -0800
X-Morgan-Systems-MailScanner-Watermark:	1233963162.39044@t7Ibgw+K5+uERlyBmHoGPg
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8BIT
Subject: RE: [ZMailer] Zmailer crashes
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date:	Fri, 30 Jan 2009 15:32:31 -0800
Message-ID: <7D1CC61717004141A57CA6CA1C8087EC38ED0B@server-16.MorganSys.net>
In-Reply-To: <20081031160305.GB9632@linux-mips.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ZMailer] Zmailer crashes
Thread-Index: Ack7clTaTjFl3l7OQS+c8D7h2/owGhHwBOHQ
References: <20081031160305.GB9632@linux-mips.org>
From:	"Neal Morgan" <Neal@Morgan-Systems.com>
To:	<zmailer@nic.funet.fi>
X-Morgan-Systems-MailScanner-Information: Please contact the ISP for more information
X-MailScanner-ID: 104989830153233
X-Morgan-Systems-MailScanner: Found to be clean
X-Morgan-Systems-MailScanner-From: neal@morgan-systems.com
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

> On October 31, 2008 9:03 AM Ralf Baechle wrote
> 
> Since quite a while I'm observing these kernel messages on a Linux
x86_64
> system:
>
> sm[3270]: segfault at 3ba7f9f0 ip 79fbc9 sp 7fffe7c48e30 error 6 in
libc-2.7.so[72d000+14d000]
> sm[3493] trap stack segment ip:7f0e2a121bc9 sp:7fff3240e4a0 error:0
> sm[3773]: segfault at 3ba7f9f0 ip 79fbc9 sp 7fff55499680 error 6 in
libc-2.7.so[72d000+14d000]


Matti: I've been seeing these across 4 servers:

kernel: smtpserver[31693]: segfault at 00000000 eip b7c16371 esp
bf94b018 error 4

kernel: router[9934]: segfault at 00000008 eip 0807fa95 esp bfdf5570
error 4

The interesting thing is it only happens when booted into a 2.6.24
kernel.  If I reboot the same box into a 2.6.18 kernel everything runs
fine (and there are no segfaults).



--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Sat Jan 31 01:37:16 2009
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S84384AbZA3XhQ1P5zQ (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Sat, 31 Jan 2009 01:37:16 +0200
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S84386AbZA3XhQXaJNQ
	(ORCPT <rfc822;zmailer-outgoing>); Sat, 31 Jan 2009 01:37:16 +0200
Received: from mail.Morgan-Systems.com ([204.16.172.8]:45683 "EHLO
	mail.morgan-systems.com" rhost-flags-OK-OK-OK-OK) by nic.funet.fi
	with ESMTP id S84384AbZA3XhPyN9ks (ORCPT
	<rfc822;zmailer@nic.funet.fi>); Sat, 31 Jan 2009 01:37:15 +0200
Received: from Server-16.MorganSys.net ([10.30.1.16]:6229 "HELO
	Mail.Morgan-Systems.com" whoson: "-unregistered-" smtp-auth: <none>
	TLS-CIPHER: <none> TLS-PEER-CN1: <none> rhost-flags-OK-OK-OK-FAIL)
	by Mail.Morgan-Systems.com with SMTP id S1049896AbZA3Xgt convert rfc822-to-8bit
	(ORCPT <rfc822;zmailer@nic.funet.fi>);
	Fri, 30 Jan 2009 15:36:49 -0800
X-Morgan-Systems-MailScanner-Watermark:	1233963414.3624@BTSshC7PHG8Tkv1LKsWZOA
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8BIT
Subject: [ZMailer] CVS Status?
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date:	Fri, 30 Jan 2009 15:36:47 -0800
Message-ID: <7D1CC61717004141A57CA6CA1C8087EC38ED0C@server-16.MorganSys.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: CVS Status?
Thread-Index: AcmDM54uZfFRYuDkSx6ayM4N15Wsfw==
From:	"Neal Morgan" <Neal@Morgan-Systems.com>
To:	<zmailer@nic.funet.fi>
X-Morgan-Systems-MailScanner-Information: Please contact the ISP for more information
X-MailScanner-ID: 104989630153649
X-Morgan-Systems-MailScanner: Found to be clean
X-Morgan-Systems-MailScanner-From: neal@morgan-systems.com
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

Matti:

I tried updating from your CVS the other day and got a login failure.
Eugene's still works, but since I haven't heard from him on the list
lately I wonder if his is up to date.  Can you shed any light on
either/both of these?



Thanks,

Neal


--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Sun Feb  1 15:52:51 2009
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S85245AbZBANworqKTs (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Sun, 1 Feb 2009 15:52:44 +0200
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S85240AbZBANwomYXvA
	(ORCPT <rfc822;zmailer-outgoing>); Sun, 1 Feb 2009 15:52:44 +0200
Received: (mea@paja.nic.funet.fi) by nic.funet.fi id S82863AbZBANwoF-GT4
	(ORCPT <rfc822;zmailer@nic.funet.fi>);
	Sun, 1 Feb 2009 15:52:44 +0200
Date:	Sun, 1 Feb 2009 15:52:44 +0200
From:	Matti Aarnio <mea@nic.funet.fi>
To:	Neal Morgan <Neal@Morgan-Systems.com>
Cc:	zmailer@nic.funet.fi
Subject: Re: [ZMailer] Zmailer crashes
Message-ID: <20090201135244.GA8440@paja.nic.funet.fi>
References: <20081031160305.GB9632@linux-mips.org> <7D1CC61717004141A57CA6CA1C8087EC38ED0B@server-16.MorganSys.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <7D1CC61717004141A57CA6CA1C8087EC38ED0B@server-16.MorganSys.net>
User-Agent: Mutt/1.4.2.1i
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

On Fri, Jan 30, 2009 at 03:32:31PM -0800, Neal Morgan wrote:
> > On October 31, 2008 9:03 AM Ralf Baechle wrote
> > Since quite a while I'm observing these kernel messages on a Linux x86_64
> > system:
> >
> > sm[3270]: segfault at 3ba7f9f0 ip 79fbc9 sp 7fffe7c48e30 error 6 in
> libc-2.7.so[72d000+14d000]
> > sm[3493] trap stack segment ip:7f0e2a121bc9 sp:7fff3240e4a0 error:0
> > sm[3773]: segfault at 3ba7f9f0 ip 79fbc9 sp 7fff55499680 error 6 in
> libc-2.7.so[72d000+14d000]
> 
> Matti: I've been seeing these across 4 servers:
> 
> kernel: smtpserver[31693]: segfault at 00000000 eip b7c16371 esp
> bf94b018 error 4
> 
> kernel: router[9934]: segfault at 00000008 eip 0807fa95 esp bfdf5570
> error 4
> 
> The interesting thing is it only happens when booted into a 2.6.24
> kernel.  If I reboot the same box into a 2.6.18 kernel everything runs
> fine (and there are no segfaults).

I do see them too with 2.6.26 kernel at zmailer.org server.
A few hits per week according to kernel dmesg logs.

I suspect more about glibc doing something stupid, than program really
going over the edge, but these are so rare that debugging them is next
to impossible.   Previously I have seen them happen after the program
has called exit(0).

Anyway I have turned on core dumps to be able to see what happens.


-- 
/Matti Aarnio	<mea@nic.funet.fi>
--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Mon Feb  2 11:34:25 2009
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S85387AbZBBJeSXi60Y (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Mon, 2 Feb 2009 11:34:18 +0200
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S85395AbZBBJeSSfSwQ
	(ORCPT <rfc822;zmailer-outgoing>); Mon, 2 Feb 2009 11:34:18 +0200
Received: from smtp.rol.ru ([194.67.1.9]:26759 "EHLO smtp.rol.ru"
	rhost-flags-OK-OK-OK-OK) by nic.funet.fi with ESMTP
	id S85387AbZBBJeRrko8Y (ORCPT <rfc822;zmailer@nic.funet.fi>);
	Mon, 2 Feb 2009 11:34:17 +0200
Received: from loki.glas.net ([195.218.254.119]:41746 "EHLO [195.218.254.119]"
	smtp-auth: <none> TLS-CIPHER: "DHE-RSA-AES256-SHA keybits 256/256
	version TLSv1/SSLv3" TLS-PEER-CN1: <none> rhost-flags-OK-OK-OK-FAIL)
	by gnome05.net.rol.ru with ESMTPS id S1276640AbZBBJeR (ORCPT
	<rfc822;zmailer@nic.funet.fi>); Mon, 2 Feb 2009 12:34:17 +0300
Message-ID: <4986BE19.5070005@rol.ru>
Date:	Mon, 02 Feb 2009 12:34:17 +0300
From:	Kostik <koc@rol.ru>
User-Agent: Thunderbird 2.0.0.19 (X11/20081209)
MIME-Version: 1.0
To:	zmailer@nic.funet.fi
Subject: Re: [ZMailer] CVS Status?
Content-Type: text/plain; charset=KOI8-R
Content-Transfer-Encoding: 7bit
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

Hi!

Eugene asked to send this reply:

---

Neal Morgan wrote:

> I tried updating from your CVS the other day and got a login failure.
> Eugene's still works, but since I haven't heard from him on the list
> lately I wonder if his is up to date.  Can you shed any light on
> either/both of these?

My mirror *may* be out of sync. But again, it may not be, as I did not see
commit notifications from Matti for a long time now.

[ since my hosted server in Australia crashed, and I got the new one in
Canada, I did not get to make synchronization fully automatic... OTOH, I'd
have more incentive if there was more activity ;-) ]

Eugene
--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Wed Feb  4 17:10:13 2009
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S86119AbZBDPKIKcwfA (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Wed, 4 Feb 2009 17:10:08 +0200
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S86118AbZBDPKIDjV6I
	(ORCPT <rfc822;zmailer-outgoing>); Wed, 4 Feb 2009 17:10:08 +0200
Received: from h5.dl5rb.org.uk ([81.2.74.5]:39716 "EHLO h5.dl5rb.org.uk"
	rhost-flags-OK-OK-OK-OK) by nic.funet.fi with ESMTP
	id S86116AbZBDPKHQuUGk (ORCPT <rfc822;zmailer@nic.funet.fi>);
	Wed, 4 Feb 2009 17:10:07 +0200
Received: from h5.dl5rb.org.uk (localhost.localdomain [127.0.0.1])
	by h5.dl5rb.org.uk (8.14.3/8.14.3) with ESMTP id n14FA0OY024632;
	Wed, 4 Feb 2009 15:10:00 GMT
Received: (from ralf@localhost)
	by h5.dl5rb.org.uk (8.14.3/8.14.3/Submit) id n14F9tSX024630;
	Wed, 4 Feb 2009 15:09:55 GMT
Date:	Wed, 4 Feb 2009 15:09:55 +0000
From:	Ralf Baechle <ralf@linux-mips.org>
To:	Matti Aarnio <mea@nic.funet.fi>
Cc:	Neal Morgan <Neal@Morgan-Systems.com>, zmailer@nic.funet.fi
Subject: Re: [ZMailer] Zmailer crashes
Message-ID: <20090204150955.GA24046@linux-mips.org>
References: <20081031160305.GB9632@linux-mips.org> <7D1CC61717004141A57CA6CA1C8087EC38ED0B@server-16.MorganSys.net> <20090201135244.GA8440@paja.nic.funet.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20090201135244.GA8440@paja.nic.funet.fi>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

On Sun, Feb 01, 2009 at 03:52:44PM +0200, Matti Aarnio wrote:

> On Fri, Jan 30, 2009 at 03:32:31PM -0800, Neal Morgan wrote:
> > > On October 31, 2008 9:03 AM Ralf Baechle wrote
> > > Since quite a while I'm observing these kernel messages on a Linux x86_64
> > > system:
> > >
> > > sm[3270]: segfault at 3ba7f9f0 ip 79fbc9 sp 7fffe7c48e30 error 6 in
> > libc-2.7.so[72d000+14d000]
> > > sm[3493] trap stack segment ip:7f0e2a121bc9 sp:7fff3240e4a0 error:0
> > > sm[3773]: segfault at 3ba7f9f0 ip 79fbc9 sp 7fff55499680 error 6 in
> > libc-2.7.so[72d000+14d000]
> > 
> > Matti: I've been seeing these across 4 servers:
> > 
> > kernel: smtpserver[31693]: segfault at 00000000 eip b7c16371 esp
> > bf94b018 error 4
> > 
> > kernel: router[9934]: segfault at 00000008 eip 0807fa95 esp bfdf5570
> > error 4
> > 
> > The interesting thing is it only happens when booted into a 2.6.24
> > kernel.  If I reboot the same box into a 2.6.18 kernel everything runs
> > fine (and there are no segfaults).

Older kernels don't emit this segfault message.  It was added in
commit abd4f7505bafdd6c5319fe3cb5caf9af6104e17a that is for 2.6.23.  Could
that be why you didn't notice it earlier?

> I do see them too with 2.6.26 kernel at zmailer.org server.
> A few hits per week according to kernel dmesg logs.
> 
> I suspect more about glibc doing something stupid, than program really
> going over the edge, but these are so rare that debugging them is next
> to impossible.   Previously I have seen them happen after the program
> has called exit(0).
> 
> Anyway I have turned on core dumps to be able to see what happens.

I've seen Zmailer stopping mail delivery or stopping accepting connections
on port 25.  The issue is hitting relativly infrequently but I decieded to
follow your example and just turned on core dumps; it is affecting sm,
smtpserver and router.  Lately the frequency of this issue striking
seems to have increased significantly - I wonder if that's due to me
looking more frequently after it or due to my extremly inflated mail
queue with over 1,700,000 stored messages.

Ironically I seem to have gotten another router segfault just seconds
before I enabled core dumps ...

  Ralf
--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Thu Feb  5 13:00:32 2009
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S86592AbZBELA3TEXdA (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Thu, 5 Feb 2009 13:00:29 +0200
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S86595AbZBELA3N5plk
	(ORCPT <rfc822;zmailer-outgoing>); Thu, 5 Feb 2009 13:00:29 +0200
Received: from smtp.rol.ru ([194.67.1.9]:5439 "EHLO smtp.rol.ru"
	rhost-flags-OK-OK-OK-OK) by nic.funet.fi with ESMTP
	id S86592AbZBELA2h8q9s (ORCPT <rfc822;zmailer@nic.funet.fi>);
	Thu, 5 Feb 2009 13:00:28 +0200
Received: from pccross.average.org ([91.192.241.20]:53073 "EHLO
	[192.168.1.207]" smtp-auth: "egc@online.ru" TLS-CIPHER:
	"DHE-RSA-AES256-SHA keybits 256/256 version TLSv1/SSLv3" TLS-PEER-CN1:
	<none> rhost-flags-OK-OK-OK-FAIL) by gnome06.net.rol.ru with ESMTPSA
	id S1275870AbZBELA2 (ORCPT <rfc822;zmailer@nic.funet.fi>);
	Thu, 5 Feb 2009 14:00:28 +0300
Message-ID: <498AC6CC.6050808@online.ru>
Date:	Thu, 05 Feb 2009 14:00:28 +0300
From:	Eugene Crosser <crosser@online.ru>
Organization: ROL
User-Agent: Thunderbird 2.0.0.19 (X11/20081209)
MIME-Version: 1.0
To:	zmailer@nic.funet.fi
Subject: [ZMailer] CVS mirror at cvs.average.org
X-Enigmail-Version: 0.95.7
OpenPGP: id=8C3A5169;
	url=http://www.average.org/~crosser/pubkey.txt
Content-Type: text/plain; charset=KOI8-R
Content-Transfer-Encoding: 7bit
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Well, following a recent note on this list, I think that I've fixed my
mirror of zmailer source to actually work unattended, syncing daily.
As a reminder,

$ cvs -d :pserver:cvs@cvs.average.org:/cvsroot login
Password: cvs
$ cd /your/source/tree
$ cvs -d :pserver:cvs@cvs.average.org:/cvsroot checkout zmailer

the thing physically lives in Montreal, Canada.
Have fun!

Eugene

P.S. 'sudo' rules!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJisa4frw/cIw6UWkRAtVjAJ9OB4RZn+tQcOId+QxAgrybSyoRaACcChB3
N2ct6LCEdkW09YqgtrX0zlk=
=M0LO
-----END PGP SIGNATURE-----

--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Mon Apr 20 19:16:05 2009
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S81623AbZDTQPzBgEDY (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Mon, 20 Apr 2009 19:15:55 +0300
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S81625AbZDTQPyxrzH4
	(ORCPT <rfc822;zmailer-outgoing>); Mon, 20 Apr 2009 19:15:54 +0300
Received: from mate.dm.uba.ar ([157.92.22.1]:42285 "EHLO mate.dm.uba.ar"
	rhost-flags-OK-OK-OK-OK) by nic.funet.fi with ESMTP
	id S81623AbZDTQPy1p2q4 (ORCPT <rfc822;zmailer@nic.funet.fi>);
	Mon, 20 Apr 2009 19:15:54 +0300
Received: from mate36.dm.uba.ar ([157.92.22.36]:54023 "EHLO [157.92.22.36]"
	smtp-auth: <none> TLS-CIPHER: <none> TLS-PEER-CN1: <none>)
	by mate.dm.uba.ar with ESMTP id S4628013AbZDTQPs (ORCPT
	<rfc822;zmailer@nic.funet.fi>); Mon, 20 Apr 2009 13:15:48 -0300
Message-ID: <49EC9FB4.20402@dm.uba.ar>
Date:	Mon, 20 Apr 2009 13:15:48 -0300
From:	Rodolfo Cossalter <rcoss@dm.uba.ar>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To:	zmailer@nic.funet.fi
Subject: [ZMailer] SPF problem
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

After compiling zmailer from Eugene's CVS, using spf_alt, I noticed that
sfp_threshold is always 0, no matter what PARAM spf-threshold is defined
in smtpserver.conf. PARAM spf-threshold is actually read but it seems as
if sfp_threshold never gets initialized in policytest.c .
I added a line  like
sfp_threshold = OCP->sfp_threshold;
just after
#ifdef Z_CHECK_SPF_DATA
and now it works, but I don't know if this is the right place.
Maybe some other spf related PARAMs need to be initilized too.
Can anyone check this?

Thanks

Rodolfo
--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Mon Apr 20 23:59:33 2009
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S81672AbZDTU7WRP8hk (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Mon, 20 Apr 2009 23:59:22 +0300
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S81674AbZDTU7WL4RaI
	(ORCPT <rfc822;zmailer-outgoing>); Mon, 20 Apr 2009 23:59:22 +0300
Received: from smtp.rol.ru ([194.67.1.9]:23803 "EHLO smtp.rol.ru"
	rhost-flags-OK-OK-OK-OK) by nic.funet.fi with ESMTP
	id S81672AbZDTU7VY1OJI (ORCPT <rfc822;zmailer@nic.funet.fi>);
	Mon, 20 Apr 2009 23:59:21 +0300
Received: from pccross.average.org ([91.192.241.20]:34251 "EHLO [192.168.1.9]"
	smtp-auth: "egc@online.ru" TLS-CIPHER: "DHE-RSA-AES256-SHA keybits
	256/256 version TLSv1/SSLv3" TLS-PEER-CN1: <none>
	rhost-flags-OK-OK-OK-FAIL) by gnome05.net.rol.ru with ESMTPSA
	id S1276148AbZDTU7U (ORCPT <rfc822;zmailer@nic.funet.fi>);
	Tue, 21 Apr 2009 00:59:20 +0400
Message-ID: <49ECE21F.7070005@online.ru>
Date:	Tue, 21 Apr 2009 00:59:11 +0400
From:	Eugene Crosser <crosser@online.ru>
Organization: ROL
User-Agent: Thunderbird 2.0.0.21 (X11/20090409)
MIME-Version: 1.0
To:	Rodolfo Cossalter <rcoss@dm.uba.ar>
CC:	zmailer@nic.funet.fi
Subject: Re: [ZMailer] SPF problem
References: <49EC9FB4.20402@dm.uba.ar>
In-Reply-To: <49EC9FB4.20402@dm.uba.ar>
X-Enigmail-Version: 0.95.7
OpenPGP: id=8C3A5169;
	url=http://www.average.org/~crosser/pubkey.txt
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enig5F02E8007D30736D7C5140F4"
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig5F02E8007D30736D7C5140F4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Rodolfo Cossalter wrote:
> After compiling zmailer from Eugene's CVS, using spf_alt, I noticed tha=
t
> sfp_threshold is always 0, no matter what PARAM spf-threshold is define=
d
> in smtpserver.conf. PARAM spf-threshold is actually read but it seems a=
s
> if sfp_threshold never gets initialized in policytest.c .
> I added a line  like
> sfp_threshold =3D OCP->sfp_threshold;
> just after
> #ifdef Z_CHECK_SPF_DATA
> and now it works, but I don't know if this is the right place.
> Maybe some other spf related PARAMs need to be initilized too.
> Can anyone check this?

I'll take a look, thanks.

Eugene


--------------enig5F02E8007D30736D7C5140F4
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJ7OIlfrw/cIw6UWkRAncSAJ40Al8rMsGCnT9PE+INOaPMsJTHowCfTnD1
REkHpEsTb1f09h2w7LJ/Uok=
=QrdU
-----END PGP SIGNATURE-----

--------------enig5F02E8007D30736D7C5140F4--
--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Sat May  2 05:14:44 2009
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S77791AbZEBCOoCiSwk (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Sat, 2 May 2009 05:14:44 +0300
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77793AbZEBCOn4uK1Q
	(ORCPT <rfc822;zmailer-outgoing>); Sat, 2 May 2009 05:14:43 +0300
Received: from mail.Morgan-Systems.com ([204.16.172.8]:52526 "EHLO
	mail.morgan-systems.com" rhost-flags-OK-OK-OK-OK) by nic.funet.fi
	with ESMTP id S77791AbZEBCOn0Os1c (ORCPT
	<rfc822;zmailer@nic.funet.fi>); Sat, 2 May 2009 05:14:43 +0300
Received: from Server-16.MorganSys.net ([10.30.1.16]:39742 "HELO
	Mail.Morgan-Systems.com" whoson: "-unregistered-" smtp-auth: <none>
	TLS-CIPHER: <none> TLS-PEER-CN1: <none> rhost-flags-OK-OK-OK-FAIL)
	by Mail.Morgan-Systems.com with SMTP id S1051023AbZEBCOX convert rfc822-to-8bit
	(ORCPT <rfc822;zmailer@nic.funet.fi>);
	Fri, 1 May 2009 19:14:23 -0700
X-Morgan-Systems-MailScanner-Watermark:	1241835271.74567@2na7P0YVm5RSGRcyDay4fw
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8BIT
Subject: [ZMailer] TLS Documentation
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date:	Fri, 1 May 2009 19:14:12 -0700
Message-ID: <6557A87A5B462247861990180A542B14466F@server-16.MorganSys.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: TLS Documentation
thread-index: AcnKyw3dGBmng9DERWuhZcua420K1wAAICMA
From:	"Neal Morgan" <Neal@Morgan-Systems.com>
To:	<zmailer@nic.funet.fi>
X-Morgan-Systems-MailScanner-Information: Please contact the ISP for more information
X-MailScanner-ID: 105102301191423
X-Morgan-Systems-MailScanner: Found to be clean
X-Morgan-Systems-MailScanner-From: neal@morgan-systems.com
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

Hello List:

My SSL certificate has expired and I am trying to install the new one.  I cannot seem to locate my notes about how I did this last time.  Nor can I locate anything beyond the self-sign CA notes in the docs folder in the source tree.

Can someone help me out with specific instructions or point me towards the right documentation for this?

Specifically, I need to take a .pfx or pkcs12 export and get it into the format expected by zmailer.  Also, I can't remember whether I manually retrieved my CA's cert last time around or if that somehow happened magically when converting the cert/key files expected by ZMailer.


Thanks,

Neal Morgan

--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Sat May  2 19:32:34 2009
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S83719AbZEBQcVIqquc (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Sat, 2 May 2009 19:32:21 +0300
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S83715AbZEBQcVCkseY
	(ORCPT <rfc822;zmailer-outgoing>); Sat, 2 May 2009 19:32:21 +0300
Received: (mea@paja.nic.funet.fi) by nic.funet.fi id S83711AbZEBQcUQ3iLQ
	(ORCPT <rfc822;zmailer@nic.funet.fi>);
	Sat, 2 May 2009 19:32:20 +0300
Date:	Sat, 2 May 2009 19:32:20 +0300
From:	Matti Aarnio <mea@nic.funet.fi>
To:	Neal Morgan <Neal@Morgan-Systems.com>
Cc:	zmailer@nic.funet.fi
Subject: Re: [ZMailer] TLS Documentation
Message-ID: <20090502163220.GD1590@paja.nic.funet.fi>
References: <6557A87A5B462247861990180A542B14466F@server-16.MorganSys.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <6557A87A5B462247861990180A542B14466F@server-16.MorganSys.net>
User-Agent: Mutt/1.4.2.1i
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

On Fri, May 01, 2009 at 07:14:12PM -0700, Neal Morgan wrote:
> Hello List:
> 
> My SSL certificate has expired and I am trying to install the new one.
> I cannot seem to locate my notes about how I did this last time.
> Nor can I locate anything beyond the self-sign CA notes in the docs
> folder in the source tree.
> 
> Can someone help me out with specific instructions or point me towards
> the right documentation for this?
> 
> Specifically, I need to take a .pfx or pkcs12 export and get it into
> the format expected by zmailer.  Also, I can't remember whether
> I manually retrieved my CA's cert last time around or if that somehow
> happened magically when converting the cert/key files expected by ZMailer.

ZMailer uses OpenSSL library to implement the SMTPS/STARTTLS, thus
what you will need is key and certificate in format that OpenSSL
can use.

I have recently been employed on among others an issue of managing certificate
lifetimes on a networked server system, and procedures like preparing new 
certificate for use well in advance of previous one expiring, and how to
propagate knowledge about the new certificates so that systems will not have
any "flag day" of needing synchronized certificate updates...

Common thing with that commercial job and ZMailer's certificates is that
to freshen the certificate, one must create a new key with proper X.500 DN
in it, then create a CSR and have a CA to sign it, and finally to import
the certificate into proper place in the ZMailer server.

The same procedure is  usable as with Sendmail, and with Postfix, I think.
Configuration details, that is telling where the cert and key are is specific
to each system.

One could also - in theory - recycle old key, but such a thing is a way to
be juicier attack target, when RSA key is kept the same for prolonged time.
One should always create a new key when creating a new certificate.

> Thanks,
> Neal Morgan
-- 
/Matti Aarnio	<mea@nic.funet.fi>
--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Wed May  6 20:41:34 2009
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S84157AbZEFRld46Qbc (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Wed, 6 May 2009 20:41:33 +0300
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S84165AbZEFRldvTMsY
	(ORCPT <rfc822;zmailer-outgoing>); Wed, 6 May 2009 20:41:33 +0300
Received: from p02c11o142.mxlogic.net ([208.65.144.75]:48417 "EHLO
	p02c11o142.mxlogic.net" rhost-flags-OK-OK-OK-OK) by nic.funet.fi
	with ESMTP id S84157AbZEFRldTJoF4 convert rfc822-to-8bit (ORCPT
	<rfc822;zmailer@nic.funet.fi>); Wed, 6 May 2009 20:41:33 +0300
Received: from unknown [68.179.27.105] (EHLO MailServer.lan.adbase.com)
	by p02c11o142.mxlogic.net (mxl_mta-6.1.1-4) over TLS secured channel
	with ESMTP id acbc10a4.3415976848.23738.00-003.p02c11o142.mxlogic.net (envelope-from <ekugel@adbase.com>);
	Wed, 06 May 2009 11:41:32 -0600 (MDT)
Received: from MailServer.lan.adbase.com ([fe80::9e5:4f4b:fed8:4540]) by
 MailServer.lan.adbase.com ([fe80::9e5:4f4b:fed8:4540%10]) with mapi; Wed, 6
 May 2009 13:38:59 -0400
From:	Ernest Kugel <ekugel@adbase.com>
To:	"'zmailer@nic.funet.fi'" <zmailer@nic.funet.fi>
Date:	Wed, 6 May 2009 13:38:58 -0400
Subject: [ZMailer] Zmailer scheduler crashes as a result of an flock error
Thread-Topic: Zmailer scheduler crashes as a result of an flock error
Thread-Index: AcnOcYr2BgBwPKZdRLKOR+7MoZrImg==
Message-ID: <ED19ACA645D1C8458D864C29328C801A1CE7E05A98@MailServer.lan.adbase.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage:	en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 8BIT
MIME-Version: 1.0
X-Spam:	[F=0.2000000000; S=0.200(2009020301)]
X-MAIL-FROM: <ekugel@adbase.com>
X-SOURCE-IP: [(unknown)]
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

Hi all,

I'm experiencing periodic crashes with scheduler which seem to be caused by an flock failure, and it looks like this brings Zmailer to a halt with a fork error.

This seems to be more frequent during higher load periods, and the only way to get Zmailer sending again is to restart scheduler.

I'm curious if anyone saw something similar before? If not, would anyone have even the slightest idea as to what might be causing it?

We're running it on Debian 4, amd64.

Thanks in advance for the time, any thoughts would be greatly appreciated... 

Ernest Kugel


--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Mon Jun 22 12:38:16 2009
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S77963AbZFVJh74kAdc (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Mon, 22 Jun 2009 12:37:59 +0300
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77983AbZFVJh7tyLkY
	(ORCPT <rfc822;zmailer-outgoing>); Mon, 22 Jun 2009 12:37:59 +0300
Received: from [194.149.90.8] ([194.149.90.8]:50847 "EHLO webhosts.mm-com.ru"
	rhost-flags-FAIL-FAIL-OK-OK) by nic.funet.fi with ESMTP
	id S77963AbZFVJh7UmS3s (ORCPT <rfc822;zmailer@nic.funet.fi>);
	Mon, 22 Jun 2009 12:37:59 +0300
Received: from host-93-182-8-148.real.kvidex.net ([93.182.8.148]:60721 "EHLO
	[192.168.100.10]" rhost-flags-OK-OK-OK-FAIL) by mail.euro-comm.net
	with ESMTPSA id S17124727AbZFVJh5 (ORCPT
	<rfc822;zmailer@nic.funet.fi>); Mon, 22 Jun 2009 13:37:57 +0400
Message-ID: <4A3F50F2.50204@lipetsk.ru>
Date:	Mon, 22 Jun 2009 13:37:54 +0400
From:	Victor Gamov <vit@lipetsk.ru>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b3pre) Gecko/20090223 Thunderbird/3.0b2
MIME-Version: 1.0
To:	zmailer@nic.funet.fi
Subject: [ZMailer] FQDN at zmailer
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

Hi gentlemans!

I use zmailer many years ago and now I try to use it again at my company 
domain.

Now we need to use virtual domains at mail server and I need to zmailer 
deliver mail to mailboxes like user@dom1 and user@dom2
If I use fqdnaliases then I need to use something like
user@dom1:	userbox_dom1

but I want to deliver mail into mailbox name in form user@dom1. If i try 
to use zmailer-2.99.57 "out of box" at FreeBSD box then I get
"Malformed (missing) recipient privilege data"

Is it posible to turn on/off some zmailer params to achieve this 
functionality or I need to hack fqdnliases.cf

Thanks!

--
CU,
Victor Gamov
--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Mon Jun 29 11:45:51 2009
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S77364AbZF2IpvFgNHk (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Mon, 29 Jun 2009 11:45:51 +0300
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77367AbZF2Ipu6mxwI
	(ORCPT <rfc822;zmailer-outgoing>); Mon, 29 Jun 2009 11:45:50 +0300
Received: from smtp.rol.ru ([194.67.1.9]:30528 "EHLO smtp.rol.ru"
	rhost-flags-OK-OK-OK-OK) by nic.funet.fi with ESMTP
	id S77364AbZF2Ipu0nHXs (ORCPT <rfc822;zmailer@nic.funet.fi>);
	Mon, 29 Jun 2009 11:45:50 +0300
Received: from blueice2n1.de.ibm.com ([195.212.29.171]:16296 "EHLO
	[9.156.35.19]" smtp-auth: "egc@online.ru" TLS-CIPHER:
	"DHE-RSA-AES256-SHA keybits 256/256 version TLSv1/SSLv3" TLS-PEER-CN1:
	<none> rhost-flags-OK-OK-OK-FAIL) by gnome06.net.rol.ru with SUBMITSA
	id S1276121AbZF2Ipt (ORCPT <rfc822;zmailer@nic.funet.fi>);
	Mon, 29 Jun 2009 12:45:49 +0400
X-Comment: RFC 2476 MSA function at gnome06.net.rol.ru logged sender identity as: egc@online.ru
Message-ID: <4A487F3A.9030605@online.ru>
Date:	Mon, 29 Jun 2009 12:45:46 +0400
From:	Eugene Crosser <crosser@online.ru>
User-Agent: Thunderbird 2.0.0.6 (X11/20070728)
MIME-Version: 1.0
To:	Victor Gamov <vit@lipetsk.ru>
CC:	zmailer@nic.funet.fi
Subject: Re: [ZMailer] FQDN at zmailer
References: <4A3F50F2.50204@lipetsk.ru>
In-Reply-To: <4A3F50F2.50204@lipetsk.ru>
Content-Type: text/plain; charset=KOI8-R
Content-Transfer-Encoding: 7bit
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

Victor Gamov wrote:

> I use zmailer many years ago and now I try to use it again at my company
> domain.
> 
> Now we need to use virtual domains at mail server and I need to zmailer
> deliver mail to mailboxes like user@dom1 and user@dom2
> If I use fqdnaliases then I need to use something like
> user@dom1:    userbox_dom1
> 
> but I want to deliver mail into mailbox name in form user@dom1. If i try
> to use zmailer-2.99.57 "out of box" at FreeBSD box then I get
> "Malformed (missing) recipient privilege data"
> 
> Is it posible to turn on/off some zmailer params to achieve this
> functionality or I need to hack fqdnliases.cf

I am not sure why do you get the message about the privilege data, but
as to your original goal, maybe MAILBOX=/var/maildoms/%D/%u (or like)
could be a solution.

This approach works best if your getpwnam() accepts username in the form
"user@domain.tld".

Eugene
--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Tue Jun 30 14:25:32 2009
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S77434AbZF3LZQFCw44 (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Tue, 30 Jun 2009 14:25:16 +0300
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77439AbZF3LZPsRjiI
	(ORCPT <rfc822;zmailer-outgoing>); Tue, 30 Jun 2009 14:25:15 +0300
Received: from [194.149.90.8] ([194.149.90.8]:58866 "EHLO webhosts.mm-com.ru"
	rhost-flags-FAIL-FAIL-OK-OK) by nic.funet.fi with ESMTP
	id S77434AbZF3LZPDluKI (ORCPT <rfc822;zmailer@nic.funet.fi>);
	Tue, 30 Jun 2009 14:25:15 +0300
Received: from host-93-182-8-148.real.kvidex.net ([93.182.8.148]:62291 "EHLO
	[192.168.100.10]" rhost-flags-OK-OK-OK-FAIL) by mail.euro-comm.net
	with ESMTPSA id S17127639AbZF3LZN (ORCPT
	<rfc822;zmailer@nic.funet.fi>); Tue, 30 Jun 2009 15:25:13 +0400
Message-ID: <4A49F617.3000509@lipetsk.ru>
Date:	Tue, 30 Jun 2009 15:25:11 +0400
From:	Victor Gamov <vit@lipetsk.ru>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b3pre) Gecko/20090223 Thunderbird/3.0b2
MIME-Version: 1.0
To:	zmailer@nic.funet.fi
Subject: Re: [ZMailer] FQDN at zmailer
References: <4A3F50F2.50204@lipetsk.ru> <4A487F3A.9030605@online.ru>
In-Reply-To: <4A487F3A.9030605@online.ru>
Content-Type: text/plain; charset=KOI8-R; format=flowed
Content-Transfer-Encoding: 7bit
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

On 29.06.2009 12:45, Eugene Crosser wrote:
> Victor Gamov wrote:
>
>> I use zmailer many years ago and now I try to use it again at my company
>> domain.
>>
>> Now we need to use virtual domains at mail server and I need to zmailer
>> deliver mail to mailboxes like user@dom1 and user@dom2
>> If I use fqdnaliases then I need to use something like
>> user@dom1:    userbox_dom1
>>
>> but I want to deliver mail into mailbox name in form user@dom1. If i try
>> to use zmailer-2.99.57 "out of box" at FreeBSD box then I get
>> "Malformed (missing) recipient privilege data"
>>
>> Is it posible to turn on/off some zmailer params to achieve this
>> functionality or I need to hack fqdnliases.cf
>
> I am not sure why do you get the message about the privilege data, but
> as to your original goal, maybe MAILBOX=/var/maildoms/%D/%u (or like)
> could be a solution.
>
> This approach works best if your getpwnam() accepts username in the form
> "user@domain.tld".

Messages delivered OK for real users from passwd.  But for virtual users 
I use following at line 335 at fqdnaliases.cf

if [ $key = $address ]
then
   returns (((local "$address" "$address" $A)))
else
   returns (((bitbucket "duplicate-$key.fqdnaliases"  "$address" $A)))
fi


in fqdnaliases file I use

virtuser_1@domain_1.tld:	virtuser_1@domain_1.tld
virtuser_1@domain_2.tld:	virtuser_1@domain_2.tld

and everything works fine

I think that it may be patch to fqdnaliases.cf and we need some 
directive at config to get this functionality.

--
CU,
Victor Gamov
--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Thu Jul 23 21:38:42 2009
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S78069AbZGWSi3W60xI (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Thu, 23 Jul 2009 21:38:29 +0300
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S78077AbZGWSi3RUbik
	(ORCPT <rfc822;zmailer-outgoing>); Thu, 23 Jul 2009 21:38:29 +0300
Received: from mail.Morgan-Systems.com ([204.16.172.8]:38884 "EHLO
	mail.morgan-systems.com" rhost-flags-OK-OK-OK-OK) by nic.funet.fi
	with ESMTP id S78069AbZGWSi2evddc (ORCPT
	<rfc822;zmailer@nic.funet.fi>); Thu, 23 Jul 2009 21:38:28 +0300
Received: from Server-16.MorganSys.net ([10.30.1.16]:5871 "HELO
	Mail.Morgan-Systems.com" whoson: "-unregistered-" smtp-auth: <none>
	TLS-CIPHER: <none> TLS-PEER-CN1: <none> rhost-flags-OK-OK-OK-FAIL)
	by Mail.Morgan-Systems.com with SMTP id S1049835AbZGWSh6 convert rfc822-to-8bit
	(ORCPT <rfc822;zmailer@nic.funet.fi>);
	Thu, 23 Jul 2009 11:37:58 -0700
X-Morgan-Systems-MailScanner-Watermark:	1248979084.14886@AtRW2YPUUICA6K5+S45Nvg
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8BIT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date:	Thu, 23 Jul 2009 11:37:57 -0700
Message-ID: <6557A87A5B462247861990180A542B144BEC@server-16.MorganSys.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: SMTP Timeout Parm in Scheduler.conf 
thread-index: AcoLxLKSMIwX7+aNR6O8uS8NLYmkTg==
From:	"Neal Morgan" <Neal@Morgan-Systems.com>
To:	<zmailer@nic.funet.fi>
X-Morgan-Systems-MailScanner-Information: Please contact the ISP for more information
X-MailScanner-ID: 104983523113758
X-Morgan-Systems-MailScanner: Found to be clean
X-Morgan-Systems-MailScanner-From: neal@morgan-systems.com
Subject: [ZMailer] SMTP Timeout Parm in Scheduler.conf
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

Greetings:

I have a remote server that has an intermittent problem with its SMTP
service.  As a result, I see messages queue growing as my outbound smtp
waits through a connection timeout and subsequent retries.

The remote eventually self corrects and shortly thereafter the messages
deliver.

I would like to change my configuration for this channel/host so the
SMTP timeout is substantially lower than the 5 minute default - to see
if I can reduce the amount of delay experienced in message delivery.

The message I am seeing is:

	"diag	Timeout of 300 sec while waiting responses from remote"


I see a timeout parm in the man page for smtp, but I am not
understanding the exact syntax required.  Here is what I have tried (in
scheduler.conf) for this channel/host - but neither of these seem to
work.  I still see the 300 sec timeout message.


	command="smtp -s -L [204.16.171.8] -T conn=30s tcpw=30s"

and 

	command="smtp -s -L [204.16.171.8] -Tconn=30s -Ttcpw=30s"


What is the correct syntax here?


Thanks,

Neal Morgan

--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Thu Jul 23 21:45:37 2009
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S78085AbZGWSpgwperQ (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Thu, 23 Jul 2009 21:45:36 +0300
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S78088AbZGWSpgtVim4
	(ORCPT <rfc822;zmailer-outgoing>); Thu, 23 Jul 2009 21:45:36 +0300
Received: from mail.Morgan-Systems.com ([204.16.172.8]:37279 "EHLO
	mail.morgan-systems.com" rhost-flags-OK-OK-OK-OK) by nic.funet.fi
	with ESMTP id S78085AbZGWSpgOeJDY (ORCPT
	<rfc822;zmailer@nic.funet.fi>); Thu, 23 Jul 2009 21:45:36 +0300
Received: from Server-16.MorganSys.net ([10.30.1.16]:6004 "HELO
	Mail.Morgan-Systems.com" whoson: "-unregistered-" smtp-auth: <none>
	TLS-CIPHER: <none> TLS-PEER-CN1: <none> rhost-flags-OK-OK-OK-FAIL)
	by Mail.Morgan-Systems.com with SMTP id S1049804AbZGWSoV convert rfc822-to-8bit
	(ORCPT <rfc822;zmailer@nic.funet.fi>);
	Thu, 23 Jul 2009 11:44:21 -0700
X-Morgan-Systems-MailScanner-Watermark:	1248979484.62469@2EBlVog/mOks0JLCgQ0KOQ
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8BIT
Subject: [ZMailer] Retry Order in Scheduler.conf
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date:	Thu, 23 Jul 2009 11:44:19 -0700
Message-ID: <6557A87A5B462247861990180A542B144BED@server-16.MorganSys.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Retry Order in Scheduler.conf
thread-index: AcoLxZa9rHZLN2LBS7ybqPOqGFaYmg==
From:	"Neal Morgan" <Neal@Morgan-Systems.com>
To:	<zmailer@nic.funet.fi>
X-Morgan-Systems-MailScanner-Information: Please contact the ISP for more information
X-MailScanner-ID: 104980423114421
X-Morgan-Systems-MailScanner: Found to be clean
X-Morgan-Systems-MailScanner-From: neal@morgan-systems.com
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

Greetings:

Is there a way to change the retry order for a particular Channel/Host
in the scheduler?

>From time to time I will have a destination reject the first message in
the queue for something related to content, and zmailer waits/retries
patiently in the same order until I either remove the offending message
or the destination changes its mind and accepts the message.

I am wondering if there is a way to make it start with a different
message on the next retry rather than continue trying to deliver in
order.

I see an "AgeOrder" parameter in the scheduler.conf, but I don't see any
mention of it in the man page, and I am not finding any alternatives to
this that look like what I want.

Does such a mechanism exist?  



Thanks,

Neal Morgan


--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Fri Jul 24 00:03:05 2009
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S77634AbZGWVCwwuaKs (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Fri, 24 Jul 2009 00:02:52 +0300
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77909AbZGWVCwrhbIc
	(ORCPT <rfc822;zmailer-outgoing>); Fri, 24 Jul 2009 00:02:52 +0300
Received: from mate.dm.uba.ar ([157.92.22.1]:41952 "EHLO mate.dm.uba.ar"
	rhost-flags-OK-OK-OK-OK) by nic.funet.fi with ESMTP
	id S77634AbZGWVCvqjIl4 (ORCPT <rfc822;zmailer@nic.funet.fi>);
	Fri, 24 Jul 2009 00:02:51 +0300
Received: from mate36.dm.uba.ar ([157.92.22.36]:17669 "EHLO [157.92.22.36]"
	smtp-auth: <none> TLS-CIPHER: <none> TLS-PEER-CN1: <none>)
	by mate.dm.uba.ar with ESMTP id S4627839AbZGWVCt (ORCPT
	<rfc822;zmailer@nic.funet.fi>); Thu, 23 Jul 2009 18:02:49 -0300
Message-ID: <4A68CFF8.8040001@dm.uba.ar>
Date:	Thu, 23 Jul 2009 18:02:48 -0300
From:	Rodolfo Cossalter <rcoss@dm.uba.ar>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To:	Neal Morgan <Neal@Morgan-Systems.com>
CC:	zmailer@nic.funet.fi
Subject: Re: [ZMailer] SMTP Timeout Parm in Scheduler.conf
References: <6557A87A5B462247861990180A542B144BEC@server-16.MorganSys.net>
In-Reply-To: <6557A87A5B462247861990180A542B144BEC@server-16.MorganSys.net>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

Neal Morgan escribió:
> Greetings:
> 
> I have a remote server that has an intermittent problem with its SMTP
> service.  As a result, I see messages queue growing as my outbound smtp
> waits through a connection timeout and subsequent retries.
> 
> The remote eventually self corrects and shortly thereafter the messages
> deliver.
> 
> I would like to change my configuration for this channel/host so the
> SMTP timeout is substantially lower than the 5 minute default - to see
> if I can reduce the amount of delay experienced in message delivery.
> 
> The message I am seeing is:
> 
> 	"diag	Timeout of 300 sec while waiting responses from remote"
> 
> 
> I see a timeout parm in the man page for smtp, but I am not
> understanding the exact syntax required.  Here is what I have tried (in
> scheduler.conf) for this channel/host - but neither of these seem to
> work.  I still see the 300 sec timeout message.
> 
> 
> 	command="smtp -s -L [204.16.171.8] -T conn=30s tcpw=30s"
> 
> and 
> 
> 	command="smtp -s -L [204.16.171.8] -Tconn=30s -Ttcpw=30s"
> 
> 
> What is the correct syntax here?
> 
That is what the man page for smtp reads, but from the source code for
smtp.c you can see that the timeouts are in seconds.
Extract from smtp.c :
-----------
...
...
...
 case 'T':		/* specify Timeout in seconds */
	    if (CISTREQN(optarg,"conn=",5)) {
	      timeout_conn = parse_interval(optarg+5,NULL);
	      if (timeout_conn < 10) {
		fprintf(stderr, "%s: bad tcp connection timeout: %s\n",
			argv[0], optarg+5);
		++errflg;
	      }
	      break;
	    } else if (CISTREQN(optarg,"data=",5)) {
	      timeout_data = parse_interval(optarg+5,NULL);
	      if (timeout_data < 10) {
		fprintf(stderr, "%s: bad data timeout: %s\n",
			argv[0], optarg+5);
		++errflg;
	      }
	      break;
	    } else if (CISTREQN(optarg,"dot=",4)) {
	      timeout_dot = parse_interval(optarg+4,NULL);
	      if (timeout_dot < 10) {
		fprintf(stderr, "%s: bad data-dot-reply timeout: %s\n",
			argv[0], optarg+4);
		++errflg;
	      }
	      break;
...
...

-------------------
I didn't try it myself

hth
Rodolfo

> 
> Thanks,
> 
> Neal Morgan
> 
> --
> To unsubscribe from this list: send the line "unsubscribe zmailer" in
> the body of a message to majordomo@nic.funet.fi

--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Sat Sep  5 17:16:12 2009
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S76799AbZIEOQLhDNUs (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Sat, 5 Sep 2009 17:16:11 +0300
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S76980AbZIEOQLaxlqI
	(ORCPT <rfc822;zmailer-outgoing>); Sat, 5 Sep 2009 17:16:11 +0300
Received: from smtp.rol.ru ([194.67.1.9]:41402 "EHLO smtp.rol.ru"
	rhost-flags-OK-OK-OK-OK) by nic.funet.fi with ESMTP
	id S76799AbZIEOQLB3v0s (ORCPT <rfc822;zmailer@nic.funet.fi>);
	Sat, 5 Sep 2009 17:16:11 +0300
Received: from ppp91-78-73-1.pppoe.mtu-net.ru ([91.78.73.1]:1342 "EHLO
	ppp91-78-73-1.pppoe.mtu-net.ru" smtp-auth: "koc@rol.ru" TLS-CIPHER:
	"AES256-SHA keybits 256/256 version TLSv1/SSLv3" TLS-PEER-CN1: <none>
	rhost-flags-OK-FAIL-OK-FAIL) by gnome08.net.rol.ru with ESMTPSA
	id S1212808AbZIEOQK (ORCPT <rfc822;zmailer@nic.funet.fi>);
	Sat, 5 Sep 2009 18:16:10 +0400
Date:	Sat, 5 Sep 2009 18:21:03 +0400
From:	Kostik <koc@rol.ru>
X-Priority: 3 (Normal)
Message-ID: <961782618.20090905182103@rol.ru>
To:	zmailer@nic.funet.fi
Subject: [ZMailer] DCC in conjunction with ZMailer
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

Hi All!

We implement DCC in conjunction with ZMailer - ZMS_DCC.

The Distributed Checksum Clearinghouses or DCC is an anti-spam
content filter that runs on a variety of operating systems. ZMS_DCC is
Zmscanner module. It uses DCC Interface Daemon (dccifd) to submit messages into
DCC. This also allows to use DCC greylisting mechanism for ZMailer MTA.

ZMS_DCC homepage: http://kocmuk.ru/zmscanner/#en

We are using ZMS_DCC more then 6 month on high traffic mail systems and it works fine.
Any question and suggestion are welcome.

=kostik


--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Sat Sep  5 18:00:53 2009
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S76999AbZIEPAqpJNLc (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Sat, 5 Sep 2009 18:00:46 +0300
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77037AbZIEPAqj0anQ
	(ORCPT <rfc822;zmailer-outgoing>); Sat, 5 Sep 2009 18:00:46 +0300
Received: from smtp.rol.ru ([194.67.1.9]:54826 "EHLO smtp.rol.ru"
	rhost-flags-OK-OK-OK-OK) by nic.funet.fi with ESMTP
	id S76999AbZIEPApgfjG4 (ORCPT <rfc822;zmailer@nic.funet.fi>);
	Sat, 5 Sep 2009 18:00:45 +0300
Received: from ppp91-78-73-1.pppoe.mtu-net.ru ([91.78.73.1]:3166 "EHLO
	ppp91-78-73-1.pppoe.mtu-net.ru" smtp-auth: "koc@rol.ru" TLS-CIPHER:
	"AES256-SHA keybits 256/256 version TLSv1/SSLv3" TLS-PEER-CN1: <none>
	rhost-flags-OK-FAIL-OK-FAIL) by gnome08.net.rol.ru with ESMTPSA
	id S1212948AbZIEPAo (ORCPT <rfc822;zmailer@nic.funet.fi>);
	Sat, 5 Sep 2009 19:00:44 +0400
Date:	Sat, 5 Sep 2009 19:05:38 +0400
From:	Kostik <koc@rol.ru>
X-Priority: 3 (Normal)
Message-ID: <1063830218.20090905190538@rol.ru>
To:	zmailer@nic.funet.fi
Subject: [ZMailer] Broken mailbox files on NFS, linux 2.6
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

Hi All!

As known, NFS client at Linux 2.6 works strange.
If you have filesystem quota and try to write data size exceeds quota, you break yours data.
Simple test_nfswrite.c program (gcc test_nfswrite.c -o test_nfswrite):
---
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>
#include <stdio.h>
#include <stdlib.h>
#include <errno.h>
#include <string.h>
#include <unistd.h>
int main(int arc, char * argv[]) {
    int fd;
    int rc;
    int i;
    int size = 1024;
    char *buf;
    int it;

    it = atoi(argv[1]);

    buf = (char*)malloc(size * sizeof(char));
    memset(buf, 'a', size - 1);
    buf[size - 1] = '\0';

/* Open test file on "quota on" file system */
    fd = open("/mount/m7/tmp/test", O_RDWR);

    for(i = 0; i < it; i++) {
    /* Write 1024 bytes blocks */1
        rc = write(fd, buf, strlen(buf));
        printf("write: %d, errno = %s\n", rc, strerror(errno));
    }
    rc = fsync(fd);
    printf("fsync: %d, errno = %s\n", rc, strerror(errno));
    rc = fdatasync(fd);
    printf("fdatasync: %d, errno = %s\n", rc, strerror(errno));
    rc = close(fd);
    printf("close: %d\n", rc);

    free(buf);
    return 0;
}
---
Run: ./test_nfswrite 120
(write 120*1024 bytes block, set more blocks for write overquota data)

On 2.4 you receive error on write stage then data size exceeds quota.
On 2.6 it always says OK. But you receive broken "test" file.

If you change:
---
-   fd = open("/mount/m7/tmp/test", O_RDWR);
+   fd = open("/mount/m7/tmp/test", O_RDWR|O_SYNC);
---
everything will work well on 2.6 - error on write stage.

Here is patch for last Zmailer (many thanx to Mike <fandorin(at)rol.ru>):

--- ./zmailer.orig/transports/mailbox/mailbox.c 2006-06-26 20:28:03.000000000 +0400
+++ ./zmailer/transports/mailbox/mailbox.c      2009-06-22 16:49:18.000000000 +0400
@@ -1753,7 +1753,8 @@
                  "To open a file with euid=%d egid=%d ismbox=%d file='%s'\n",
                  (int)geteuid(), (int)getegid(), ismbox, file);

-       fdmail = open(file, O_RDWR|O_APPEND);
+/* koc */
+       fdmail = open(file, O_RDWR|O_APPEND|O_SYNC);

        if (fdmail < 0) {
          char fmtbuf[512];
@@ -1997,6 +1998,11 @@
       int rc = write(sffileno(sfp), p, len);
       int e  = errno;

+/* koc */
+      if ((rc < 0) && (fsync(sffileno(sfp)) < 0)) {
+        if (errno == EDQUOT) e  = errno;
+      }
+
 if (verboselog)
   fprintf(verboselog, " mbox_sfwrite(ptr, len=%d) rc=%d errno=%d\n",
          (int)len, rc, e);


=koc

--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Fri Sep 11 16:04:09 2009
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S77377AbZIKNECZneCQ (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Fri, 11 Sep 2009 16:04:02 +0300
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77381AbZIKNECSzs4A
	(ORCPT <rfc822;zmailer-outgoing>); Fri, 11 Sep 2009 16:04:02 +0300
Received: from ss2.mm-com.ru ([194.149.90.8]:64137 "EHLO ss2.mm-com.ru"
	rhost-flags-OK-FAIL-OK-FAIL) by nic.funet.fi with ESMTP
	id S77377AbZIKNEBdpxUY (ORCPT <rfc822;zmailer@nic.funet.fi>);
	Fri, 11 Sep 2009 16:04:01 +0300
Received: from host-93-182-8-148.real.kvidex.net ([93.182.8.148]:63195 "EHLO
	[192.168.100.10]" rhost-flags-OK-OK-OK-FAIL) by mail.euro-comm.net
	with ESMTPSA id S17123360AbZIKND5 (ORCPT
	<rfc822;zmailer@nic.funet.fi>); Fri, 11 Sep 2009 17:03:57 +0400
Message-ID: <4AAA4ABC.2010401@lipetsk.ru>
Date:	Fri, 11 Sep 2009 17:03:56 +0400
From:	Victor Gamov <vit@lipetsk.ru>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3
MIME-Version: 1.0
To:	zmailer@nic.funet.fi
Subject: [ZMailer] smtpserver core dumped
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

Hi all

FreeBSD-7.2 + perl-5.8.9 + zmailer-2.99.57 (--with-embed-perl)

smtpserver compiling produce following:
./smtphook.c: In function 'ZSMTP_hook_init':
./smtphook.c:78: warning: passing argument 2 of 'Perl_sys_init3' from 
incompatible pointer type

When smtpserver started it core dumped.
Looking at smtphook.c and "man perlembed" and yes incompatible type founded.

(dirty) patch by diff -c applyed:

---------------- cut here -------------------
*** smtphook.c.orig     Fri Sep 11 16:53:06 2009
--- smtphook.c  Fri Sep 11 16:58:18 2009
***************
*** 67,72 ****
--- 67,73 ----
   {
         const char *smtpperl5opt;
         char *argv[] = {"", perlhookpath};
+       char **argv2 = &argv;
         int argc = sizeof(argv) / sizeof(char *), exitstatus;

   #ifdef HAVE_PUTENV
***************
*** 75,81 ****
                         type(NULL , 0, NULL, "Can not set PERL5OPT 
environment variable !");
   #endif

!       PERL_SYS_INIT3(&argc, &argv, NULL);

         if ((my_perl = perl_alloc()) == NULL) {
                 type(NULL , 0, NULL, "Can not allocate memory for perl !");
--- 76,82 ----
                         type(NULL , 0, NULL, "Can not set PERL5OPT 
environment variable !");
   #endif

!       PERL_SYS_INIT3(&argc, &argv2, NULL);

         if ((my_perl = perl_alloc()) == NULL) {
                 type(NULL , 0, NULL, "Can not allocate memory for perl !");
---------------- /cut here -------------------

smtpserver compiled and worked correctly now.


--
CU,
Victor Gamov
--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Fri Sep 11 17:05:20 2009
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S77364AbZIKOFUGeU3c (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Fri, 11 Sep 2009 17:05:20 +0300
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77380AbZIKOFT51yJk
	(ORCPT <rfc822;zmailer-outgoing>); Fri, 11 Sep 2009 17:05:19 +0300
Received: from ss2.mm-com.ru ([194.149.90.8]:56444 "EHLO ss2.mm-com.ru"
	rhost-flags-OK-FAIL-OK-FAIL) by nic.funet.fi with ESMTP
	id S77364AbZIKOFTXEvIs (ORCPT <rfc822;zmailer@nic.funet.fi>);
	Fri, 11 Sep 2009 17:05:19 +0300
Received: from host-93-182-8-148.real.kvidex.net ([93.182.8.148]:62325 "EHLO
	[192.168.100.10]" rhost-flags-OK-OK-OK-FAIL) by mail.euro-comm.net
	with ESMTPSA id S17123360AbZIKOFR (ORCPT
	<rfc822;zmailer@nic.funet.fi>); Fri, 11 Sep 2009 18:05:17 +0400
Message-ID: <4AAA591B.2050209@lipetsk.ru>
Date:	Fri, 11 Sep 2009 18:05:15 +0400
From:	Victor Gamov <vit@lipetsk.ru>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3
MIME-Version: 1.0
To:	zmailer@nic.funet.fi
Subject: Re: [ZMailer] smtpserver core dumped
References: <4AAA4ABC.2010401@lipetsk.ru>
In-Reply-To: <4AAA4ABC.2010401@lipetsk.ru>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

On 11.09.2009 17:03, Victor Gamov wrote:
> Hi all
>
> FreeBSD-7.2 + perl-5.8.9 + zmailer-2.99.57 (--with-embed-perl)
>
> smtpserver compiling produce following:
> ./smtphook.c: In function 'ZSMTP_hook_init':
> ./smtphook.c:78: warning: passing argument 2 of 'Perl_sys_init3' from
> incompatible pointer type
>
> When smtpserver started it core dumped.
> Looking at smtphook.c and "man perlembed" and yes incompatible type
> founded.
>
> (dirty) patch by diff -c applyed:
>
> ---------------- cut here -------------------
> *** smtphook.c.orig Fri Sep 11 16:53:06 2009
> --- smtphook.c Fri Sep 11 16:58:18 2009
> ***************
> *** 67,72 ****
> --- 67,73 ----
> {
> const char *smtpperl5opt;
> char *argv[] = {"", perlhookpath};
> + char **argv2 = &argv;

hmm
char **argv2 = &argv[0];
looks like more correct
--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Fri Oct  9 17:45:04 2009
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S76740AbZJIOozWjLJA (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Fri, 9 Oct 2009 17:44:55 +0300
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77050AbZJIOozRLJpA
	(ORCPT <rfc822;zmailer-outgoing>); Fri, 9 Oct 2009 17:44:55 +0300
Received: from eddie.linux-mips.org ([78.24.191.182]:34656 "EHLO
	eddie.linux-mips.org" rhost-flags-OK-OK-OK-OK) by nic.funet.fi
	with ESMTP id S76740AbZJIOoyZgBUk (ORCPT
	<rfc822;zmailer@nic.funet.fi>); Fri, 9 Oct 2009 17:44:54 +0300
Received: from localhost.localdomain ([127.0.0.1]:32800 "EHLO h5.dl5rb.org.uk"
	rhost-flags-OK-OK-OK-FAIL) by ftp.linux-mips.org with ESMTP
	id S1492878AbZJIOov (ORCPT <rfc822;zmailer@nic.funet.fi> + 1 other);
	Fri, 9 Oct 2009 16:44:51 +0200
Received: from h5.dl5rb.org.uk (localhost.localdomain [127.0.0.1])
	by h5.dl5rb.org.uk (8.14.3/8.14.3) with ESMTP id n99Ek19Z019671;
	Fri, 9 Oct 2009 16:46:01 +0200
Received: (from ralf@localhost)
	by h5.dl5rb.org.uk (8.14.3/8.14.3/Submit) id n99Ek0G3019667;
	Fri, 9 Oct 2009 16:46:00 +0200
Date:	Fri, 9 Oct 2009 16:46:00 +0200
From:	Ralf Baechle <ralf@linux-mips.org>
To:	Matti Aarnio <mea@nic.funet.fi>
Cc:	Neal Morgan <Neal@Morgan-Systems.com>, zmailer@nic.funet.fi
Subject: Re: [ZMailer] Zmailer crashes
Message-ID: <20091009144600.GA19375@linux-mips.org>
References: <20081031160305.GB9632@linux-mips.org> <7D1CC61717004141A57CA6CA1C8087EC38ED0B@server-16.MorganSys.net> <20090201135244.GA8440@paja.nic.funet.fi> <20090204150955.GA24046@linux-mips.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20090204150955.GA24046@linux-mips.org>
User-Agent: Mutt/1.5.19 (2009-01-05)
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

On Wed, Feb 04, 2009 at 03:09:55PM +0000, Ralf Baechle wrote:

> > On Fri, Jan 30, 2009 at 03:32:31PM -0800, Neal Morgan wrote:
> > > > On October 31, 2008 9:03 AM Ralf Baechle wrote
> > > > Since quite a while I'm observing these kernel messages on a Linux x86_64
> > > > system:
> > > >
> > > > sm[3270]: segfault at 3ba7f9f0 ip 79fbc9 sp 7fffe7c48e30 error 6 in
> > > libc-2.7.so[72d000+14d000]
> > > > sm[3493] trap stack segment ip:7f0e2a121bc9 sp:7fff3240e4a0 error:0
> > > > sm[3773]: segfault at 3ba7f9f0 ip 79fbc9 sp 7fff55499680 error 6 in
> > > libc-2.7.so[72d000+14d000]
> > > 
> > > Matti: I've been seeing these across 4 servers:
> > > 
> > > kernel: smtpserver[31693]: segfault at 00000000 eip b7c16371 esp
> > > bf94b018 error 4
> > > 
> > > kernel: router[9934]: segfault at 00000008 eip 0807fa95 esp bfdf5570
> > > error 4
> > > 
> > > The interesting thing is it only happens when booted into a 2.6.24
> > > kernel.  If I reboot the same box into a 2.6.18 kernel everything runs
> > > fine (and there are no segfaults).
> 
> Older kernels don't emit this segfault message.  It was added in
> commit abd4f7505bafdd6c5319fe3cb5caf9af6104e17a that is for 2.6.23.  Could
> that be why you didn't notice it earlier?
> 
> > I do see them too with 2.6.26 kernel at zmailer.org server.
> > A few hits per week according to kernel dmesg logs.
> > 
> > I suspect more about glibc doing something stupid, than program really
> > going over the edge, but these are so rare that debugging them is next
> > to impossible.   Previously I have seen them happen after the program
> > has called exit(0).
> > 
> > Anyway I have turned on core dumps to be able to see what happens.
> 
> I've seen Zmailer stopping mail delivery or stopping accepting connections
> on port 25.  The issue is hitting relativly infrequently but I decieded to
> follow your example and just turned on core dumps; it is affecting sm,
> smtpserver and router.  Lately the frequency of this issue striking
> seems to have increased significantly - I wonder if that's due to me
> looking more frequently after it or due to my extremly inflated mail
> queue with over 1,700,000 stored messages.
> 
> Ironically I seem to have gotten another router segfault just seconds
> before I enabled core dumps ...

To close this old case - the issue went away for me after upgrading the
system from Fedora 8 to Fedora 10.  So I assume there indeed as suspected
by Matti was something toxic in glibc.

  Ralf
--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Sun Oct 18 21:05:19 2009
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S77515AbZJRSFLKBRcQ (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Sun, 18 Oct 2009 21:05:11 +0300
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77662AbZJRSFKy7zzk
	(ORCPT <rfc822;zmailer-outgoing>); Sun, 18 Oct 2009 21:05:10 +0300
Received: from smtp.rol.ru ([194.67.1.9]:21664 "EHLO smtp.rol.ru"
	rhost-flags-OK-OK-OK-OK) by nic.funet.fi with ESMTP
	id S77529AbZJRSFJw5qdc (ORCPT <rfc822;zmailer@nic.funet.fi>);
	Sun, 18 Oct 2009 21:05:09 +0300
Received: from ppp91-77-133-0.pppoe.mtu-net.ru ([91.77.133.0]:3428 "EHLO
	ppp91-77-133-0.pppoe.mtu-net.ru" smtp-auth: "koc@rol.ru" TLS-CIPHER:
	"AES256-SHA keybits 256/256 version TLSv1/SSLv3" TLS-PEER-CN1: <none>
	rhost-flags-OK-OK-OK-OK) by gnome09.net.rol.ru with ESMTPSA
	id S1180219AbZJRSFI (ORCPT <rfc822;zmailer@nic.funet.fi>);
	Sun, 18 Oct 2009 22:05:08 +0400
X-DSPAM-Result:	Innocent
X-DSPAM-Confidence: 0.8505
X-DSPAM-Probability: 0.0000
Date:	Sun, 18 Oct 2009 22:10:47 +0400
From:	Kostik <koc@rol.ru>
X-Priority: 3 (Normal)
Message-ID: <903984983.20091018221047@rol.ru>
To:	zmailer@nic.funet.fi
Subject: [ZMailer] Dovecot LDA as local delivery agent
MIME-Version: 1.0
Content-Type:	text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

Hi!

Some time ago, we are setup Dovecot LDA as local delivery agent for Zmailer.

Main features of Dovecot LDA (http://wiki.dovecot.org/LDA):
-- Mailbox indexing during mail delivery, providing faster mailbox access later
-- Quota enforcing by a plugin
-- Sieve language support by a plugin
---- Mail filtering
---- Mail forwarding
---- Vacation auto-reply

Perhaps anyone would be interested:

1. Add to zmailer/sm.conf
---
# dovecot LDA
dovecot SPfne  /usr/local/libexec/dovecot/deliver  deliver -e -n -d $u
---

2. Change zmailer/scheduler.conf like this:

Go local/file* and local/pipe* thru "mailbox" delivery agent:
---
local/file*
local/pipe*
        ...
        # zmailer local delivery transport agent
        command="mailbox -8HS -l ${LOGDIR}/mailbox"
---

and after go all other local/* thru dovecot LDA:
---
local/*
        ...
        # DOVECOT as the local delivery agent:
        command="sm -8c $channel dovecot"
---

As /Matti Aarnio wrote about procmail:
>
> Then all deliveries to local users will go thru procmail, AND
> if users want to run pipes / store to files thru their  .forward
> files, they can do that too.  (That is why there are tag-matchers
> for  "local/file*" and "local/pipe*" before "local/*" in that
> scheduler.conf file; those are for cases which must not run thru
> procmail.)


But little problem: If you (as we) will start use "-e" deliver param:
---
-e: If mail gets rejected, write the rejection reason to stderr and exit with EX_NOPERM.
---
Zmailer start complain on reject case: "(this is abnormal, investigate!)".

Fix Zmailer: in zmailer/transports/libta/diagnostic.c:
---
-      case EX_NOPERM:
       case EX_PROTOCOL:
       case EX_USAGE:
               strcat(message,
                      " (this is abnormal, investigate!)");
               s += strlen(s);
               /* fall through */
+      case EX_NOPERM:
       case EX_NOUSER:
       case EX_NOHOST:
       case EX_UNAVAILABLE:
---

Or fix Dovecot: in dovecot-1.2.6/src/deliver/deliver.c:
---
                if (stderr_rejection)
-                       return EX_NOPERM;
+                       return EX_UNAVAILABLE;
---


=kostik

--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Tue Nov 24 00:43:01 2009
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S76993AbZKWWnB1lgMk (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Tue, 24 Nov 2009 00:43:01 +0200
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77346AbZKWWnBWIELI
	(ORCPT <rfc822;zmailer-outgoing>); Tue, 24 Nov 2009 00:43:01 +0200
Received: from h5.dl5rb.org.uk ([81.2.74.5]:58408 "EHLO h5.dl5rb.org.uk"
	rhost-flags-OK-OK-OK-OK) by nic.funet.fi with ESMTP
	id S76993AbZKWWnAvq40Q (ORCPT <rfc822;zmailer@nic.funet.fi>);
	Tue, 24 Nov 2009 00:43:00 +0200
Received: from h5.dl5rb.org.uk (localhost.localdomain [127.0.0.1])
	by h5.dl5rb.org.uk (8.14.3/8.14.3) with ESMTP id nANMhFge027680;
	Mon, 23 Nov 2009 22:43:15 GMT
Received: (from ralf@localhost)
	by h5.dl5rb.org.uk (8.14.3/8.14.3/Submit) id nANMhE3X027678;
	Mon, 23 Nov 2009 22:43:14 GMT
Date:	Mon, 23 Nov 2009 22:43:14 +0000
From:	Ralf Baechle <ralf@linux-mips.org>
To:	zmailer@nic.funet.fi
Cc:	Matti Aarnio <mea@nic.funet.fi>
Subject: [ZMailer] Zmailer breaks on Fedora 12
Message-ID: <20091123224314.GA26735@linux-mips.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.19 (2009-01-05)
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

An upgrade from Fedora 10 to Fedora 12 broke zmailer for me.  Initial
sympthom were syslog messages:

Message from syslogd@box at Nov 23 23:23:53 ...
 smtpserver[18047]: smtpserver policy database problem, code: 2

where code 2 means not found.  Since the database file was present I was
wondering what smtpserver was actually trying to open and found this gem
in the strace output:

[pid 17844] stat("$MLVAR/db/smsmtp-policy.db", 0x7fff018ebbf0) = -1 ENOENT (No such file or directory)

I was able to get that to work by throwing in two symlinks but obviously
something is very wrong here.

  Ralf
--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Tue Nov 24 13:56:14 2009
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S77049AbZKXL4EbY8-4 (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Tue, 24 Nov 2009 13:56:04 +0200
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77455AbZKXL4E0OZ0A
	(ORCPT <rfc822;zmailer-outgoing>); Tue, 24 Nov 2009 13:56:04 +0200
Received: from mail-3.netbauds.net ([78.33.0.242]:56623 "EHLO
	mail-3.netbauds.net" rhost-flags-OK-OK-OK-OK) by nic.funet.fi
	with ESMTP id S77049AbZKXL4Dxtch4 (ORCPT
	<rfc822;zmailer@nic.funet.fi>); Tue, 24 Nov 2009 13:56:03 +0200
Received: from 93-97-168-38.zone5.bethere.co.uk ([93.97.168.38]:35097 "EHLO
	odin.home.darrylmiles.org" smtp-auth: "darryl" TLS-CIPHER:
	"DHE-RSA-AES256-SHA keybits 256/256 version TLSv1/SSLv3" TLS-PEER-CN1:
	<none> rhost-flags-OK-OK-OK-FAIL) by mail-3.netbauds.net with ESMTPSA
	id S4524883AbZKXL4C (ORCPT <rfc822;mea@nic.funet.fi> + 1 other);
	Tue, 24 Nov 2009 11:56:02 +0000
Message-ID: <4B0BC9C8.1000008@netbauds.net>
Date:	Tue, 24 Nov 2009 11:55:52 +0000
From:	Darryl Miles <darryl-mailinglists@netbauds.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB; rv:1.8.1.23) Gecko/20090823 SeaMonkey/1.1.18
MIME-Version: 1.0
To:	Ralf Baechle <ralf@linux-mips.org>
CC:	zmailer@nic.funet.fi, Matti Aarnio <mea@nic.funet.fi>
Subject: Re: [ZMailer] Zmailer breaks on Fedora 12
References: <20091123224314.GA26735@linux-mips.org>
In-Reply-To: <20091123224314.GA26735@linux-mips.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi


Could the format have changes ?  have you tried deleting all DBM 
database files and recreating them from the original data ?

Darryl


Ralf Baechle wrote:
> An upgrade from Fedora 10 to Fedora 12 broke zmailer for me.  Initial
> sympthom were syslog messages:
> 
> Message from syslogd@box at Nov 23 23:23:53 ...
>  smtpserver[18047]: smtpserver policy database problem, code: 2
> 
> where code 2 means not found.  Since the database file was present I was
> wondering what smtpserver was actually trying to open and found this gem
> in the strace output:
> 
> [pid 17844] stat("$MLVAR/db/smsmtp-policy.db", 0x7fff018ebbf0) = -1 ENOENT (No such file or directory)
> 
> I was able to get that to work by throwing in two symlinks but obviously
> something is very wrong here.
--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Tue Nov 24 14:16:48 2009
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S77035AbZKXMQiomAx4 (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Tue, 24 Nov 2009 14:16:38 +0200
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77599AbZKXMQijU7bs
	(ORCPT <rfc822;zmailer-outgoing>); Tue, 24 Nov 2009 14:16:38 +0200
Received: from h5.dl5rb.org.uk ([81.2.74.5]:39311 "EHLO h5.dl5rb.org.uk"
	rhost-flags-OK-OK-OK-OK) by nic.funet.fi with ESMTP
	id S77035AbZKXMQiMdWYI (ORCPT <rfc822;zmailer@nic.funet.fi>);
	Tue, 24 Nov 2009 14:16:38 +0200
Received: from h5.dl5rb.org.uk (localhost.localdomain [127.0.0.1])
	by h5.dl5rb.org.uk (8.14.3/8.14.3) with ESMTP id nAOCGqM3026523;
	Tue, 24 Nov 2009 12:16:52 GMT
Received: (from ralf@localhost)
	by h5.dl5rb.org.uk (8.14.3/8.14.3/Submit) id nAOCGpWd026521;
	Tue, 24 Nov 2009 12:16:51 GMT
Date:	Tue, 24 Nov 2009 12:16:51 +0000
From:	Ralf Baechle <ralf@linux-mips.org>
To:	Darryl Miles <darryl-mailinglists@netbauds.net>
Cc:	zmailer@nic.funet.fi, Matti Aarnio <mea@nic.funet.fi>
Subject: Re: [ZMailer] Zmailer breaks on Fedora 12
Message-ID: <20091124121651.GA5749@linux-mips.org>
References: <20091123224314.GA26735@linux-mips.org> <4B0BC9C8.1000008@netbauds.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4B0BC9C8.1000008@netbauds.net>
User-Agent: Mutt/1.5.19 (2009-01-05)
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

On Tue, Nov 24, 2009 at 11:55:52AM +0000, Darryl Miles wrote:

> Could the format have changes ?  have you tried deleting all DBM  
> database files and recreating them from the original data ?

Tried that and it didn't make any difference.  I also tried rebuilding
Zmailer again that didn't make any difference.

  Ralf
--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Tue Nov 24 14:51:18 2009
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S77599AbZKXMvJEQ3cA (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Tue, 24 Nov 2009 14:51:09 +0200
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77666AbZKXMvJA76aQ
	(ORCPT <rfc822;zmailer-outgoing>); Tue, 24 Nov 2009 14:51:09 +0200
Received: from mail-1.netbauds.net ([78.33.0.162]:10565 "EHLO
	mail-1.netbauds.net" rhost-flags-OK-OK-OK-OK) by nic.funet.fi
	with ESMTP id S77599AbZKXMvIaqMm4 (ORCPT
	<rfc822;zmailer@nic.funet.fi>); Tue, 24 Nov 2009 14:51:08 +0200
Received: from 93-97-168-38.zone5.bethere.co.uk ([93.97.168.38]:41097 "EHLO
	odin.home.darrylmiles.org" smtp-auth: "darryl" TLS-CIPHER:
	"DHE-RSA-AES256-SHA keybits 256/256 version TLSv1/SSLv3" TLS-PEER-CN1:
	<none> rhost-flags-OK-OK-OK-FAIL) by mail-1.netbauds.net with ESMTPSA
	id S8324107AbZKXMvH (ORCPT <rfc822;mea@nic.funet.fi> + 1 other);
	Tue, 24 Nov 2009 12:51:07 +0000
Message-ID: <4B0BD6B0.9060201@netbauds.net>
Date:	Tue, 24 Nov 2009 12:50:56 +0000
From:	Darryl Miles <darryl-mailinglists@netbauds.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB; rv:1.8.1.23) Gecko/20090823 SeaMonkey/1.1.18
MIME-Version: 1.0
To:	Ralf Baechle <ralf@linux-mips.org>
CC:	zmailer@nic.funet.fi, Matti Aarnio <mea@nic.funet.fi>
Subject: Re: [ZMailer] Zmailer breaks on Fedora 12
References: <20091123224314.GA26735@linux-mips.org> <4B0BC9C8.1000008@netbauds.net> <20091124121651.GA5749@linux-mips.org>
In-Reply-To: <20091124121651.GA5749@linux-mips.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

Ralf Baechle wrote:
> On Tue, Nov 24, 2009 at 11:55:52AM +0000, Darryl Miles wrote:
> 
>> Could the format have changes ?  have you tried deleting all DBM  
>> database files and recreating them from the original data ?
> 
> Tried that and it didn't make any difference.  I also tried rebuilding
> Zmailer again that didn't make any difference.

Okay has the file naming convention changed ?  I.e. its no longer *.db 
but *.whateverdb ?

When you did install/recreate the DB files what new names did they get ?

Darryl
--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Tue Nov 24 15:02:08 2009
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S77739AbZKXNCIS0Hy4 (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Tue, 24 Nov 2009 15:02:08 +0200
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77742AbZKXNCIO1Iv4
	(ORCPT <rfc822;zmailer-outgoing>); Tue, 24 Nov 2009 15:02:08 +0200
Received: from h5.dl5rb.org.uk ([81.2.74.5]:33247 "EHLO h5.dl5rb.org.uk"
	rhost-flags-OK-OK-OK-OK) by nic.funet.fi with ESMTP
	id S77739AbZKXNCHlsWRc (ORCPT <rfc822;zmailer@nic.funet.fi>);
	Tue, 24 Nov 2009 15:02:07 +0200
Received: from h5.dl5rb.org.uk (localhost.localdomain [127.0.0.1])
	by h5.dl5rb.org.uk (8.14.3/8.14.3) with ESMTP id nAOD2NH1027492;
	Tue, 24 Nov 2009 13:02:23 GMT
Received: (from ralf@localhost)
	by h5.dl5rb.org.uk (8.14.3/8.14.3/Submit) id nAOD2NFT027490;
	Tue, 24 Nov 2009 13:02:23 GMT
Date:	Tue, 24 Nov 2009 13:02:23 +0000
From:	Ralf Baechle <ralf@linux-mips.org>
To:	Darryl Miles <darryl-mailinglists@netbauds.net>
Cc:	zmailer@nic.funet.fi, Matti Aarnio <mea@nic.funet.fi>
Subject: Re: [ZMailer] Zmailer breaks on Fedora 12
Message-ID: <20091124130223.GC5749@linux-mips.org>
References: <20091123224314.GA26735@linux-mips.org> <4B0BC9C8.1000008@netbauds.net> <20091124121651.GA5749@linux-mips.org> <4B0BD6B0.9060201@netbauds.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4B0BD6B0.9060201@netbauds.net>
User-Agent: Mutt/1.5.19 (2009-01-05)
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

On Tue, Nov 24, 2009 at 12:50:56PM +0000, Darryl Miles wrote:

> 
> Ralf Baechle wrote:
>> On Tue, Nov 24, 2009 at 11:55:52AM +0000, Darryl Miles wrote:
>>
>>> Could the format have changes ?  have you tried deleting all DBM   
>>> database files and recreating them from the original data ?
>>
>> Tried that and it didn't make any difference.  I also tried rebuilding
>> Zmailer again that didn't make any difference.
>
> Okay has the file naming convention changed ?  I.e. its no longer *.db  
> but *.whateverdb ?
>
> When you did install/recreate the DB files what new names did they get ?

No, the naming convention hasn't changed and the db file has the correct
name /etc/zmailer/db/smtp-policy.db.  The issue is that smtpserver is using
this utterly broken filename "$MLVAR/db/smsmtp-policy.db" to look for the
policy db.

  Ralf
--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Wed Nov 25 13:36:04 2009
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S77794AbZKYLgD5sMJs (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Wed, 25 Nov 2009 13:36:03 +0200
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77792AbZKYLgDxF7d4
	(ORCPT <rfc822;zmailer-outgoing>); Wed, 25 Nov 2009 13:36:03 +0200
Received: (mea@paja.nic.funet.fi) by nic.funet.fi id S77787AbZKYLgDP4hCQ
	(ORCPT <rfc822;zmailer@nic.funet.fi>);
	Wed, 25 Nov 2009 13:36:03 +0200
Date:	Wed, 25 Nov 2009 13:36:03 +0200
From:	Matti Aarnio <mea@nic.funet.fi>
To:	Ralf Baechle <ralf@linux-mips.org>
Cc:	zmailer@nic.funet.fi, Matti Aarnio <mea@nic.funet.fi>
Subject: Re: [ZMailer] Zmailer breaks on Fedora 12
Message-ID: <20091125113603.GB11733@paja.nic.funet.fi>
References: <20091123224314.GA26735@linux-mips.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20091123224314.GA26735@linux-mips.org>
User-Agent: Mutt/1.4.2.1i
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

On Mon, Nov 23, 2009 at 10:43:14PM +0000, Ralf Baechle wrote:
> An upgrade from Fedora 10 to Fedora 12 broke zmailer for me.  Initial
> sympthom were syslog messages:

I have usually had a need to recompile the ZMailer on new
Fedora.  For the reason of libraries having changed...

The strace results below are rather surprising...
Your box is MIPS, which has different endianity, and all such funny things?

> Message from syslogd@box at Nov 23 23:23:53 ...
>  smtpserver[18047]: smtpserver policy database problem, code: 2
> 
> where code 2 means not found.  Since the database file was present I was
> wondering what smtpserver was actually trying to open and found this gem
> in the strace output:
> 
> [pid 17844] stat("$MLVAR/db/smsmtp-policy.db", 0x7fff018ebbf0) = -1 ENOENT (No such file or directory)
> 
> I was able to get that to work by throwing in two symlinks but obviously
> something is very wrong here.
> 
>   Ralf

-- 
/Matti Aarnio	<mea@nic.funet.fi>
--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Wed Nov 25 14:33:37 2009
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S77787AbZKYMdguPgYs (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Wed, 25 Nov 2009 14:33:36 +0200
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77795AbZKYMdgqF7l4
	(ORCPT <rfc822;zmailer-outgoing>); Wed, 25 Nov 2009 14:33:36 +0200
Received: from h5.dl5rb.org.uk ([81.2.74.5]:33923 "EHLO h5.dl5rb.org.uk"
	rhost-flags-OK-OK-OK-OK) by nic.funet.fi with ESMTP
	id S77787AbZKYMdgO3k94 (ORCPT <rfc822;zmailer@nic.funet.fi>);
	Wed, 25 Nov 2009 14:33:36 +0200
Received: from h5.dl5rb.org.uk (localhost.localdomain [127.0.0.1])
	by h5.dl5rb.org.uk (8.14.3/8.14.3) with ESMTP id nAPCXmKP006339;
	Wed, 25 Nov 2009 12:33:50 GMT
Received: (from ralf@localhost)
	by h5.dl5rb.org.uk (8.14.3/8.14.3/Submit) id nAPCXle9006337;
	Wed, 25 Nov 2009 12:33:47 GMT
Date:	Wed, 25 Nov 2009 12:33:47 +0000
From:	Ralf Baechle <ralf@linux-mips.org>
To:	Matti Aarnio <mea@nic.funet.fi>
Cc:	zmailer@nic.funet.fi
Subject: Re: [ZMailer] Zmailer breaks on Fedora 12
Message-ID: <20091125123347.GA5225@linux-mips.org>
References: <20091123224314.GA26735@linux-mips.org> <20091125113603.GB11733@paja.nic.funet.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20091125113603.GB11733@paja.nic.funet.fi>
User-Agent: Mutt/1.5.19 (2009-01-05)
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

On Wed, Nov 25, 2009 at 01:36:03PM +0200, Matti Aarnio wrote:

> On Mon, Nov 23, 2009 at 10:43:14PM +0000, Ralf Baechle wrote:
> > An upgrade from Fedora 10 to Fedora 12 broke zmailer for me.  Initial
> > sympthom were syslog messages:
> 
> I have usually had a need to recompile the ZMailer on new
> Fedora.  For the reason of libraries having changed...
> 
> The strace results below are rather surprising...
> Your box is MIPS, which has different endianity, and all such funny things?

No; the system is which is a x86_64 virtual machine running on VMware ESX
running pretty much a stock F12 - with maybe the biggest difference from a
standard system being Zmailer :-)

I don't seem to have issues with any of the other databases btw.  Only
the policy DB seems to be affected.  Where in the zmailer code is the
filename for the policy db generated?

  Ralf
--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Wed Nov 25 14:41:42 2009
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S77799AbZKYMllkn9gI (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Wed, 25 Nov 2009 14:41:41 +0200
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77795AbZKYMllhLAGk
	(ORCPT <rfc822;zmailer-outgoing>); Wed, 25 Nov 2009 14:41:41 +0200
Received: (mea@paja.nic.funet.fi) by nic.funet.fi id S77799AbZKYMlk5KzPI
	(ORCPT <rfc822;zmailer@nic.funet.fi>);
	Wed, 25 Nov 2009 14:41:40 +0200
Date:	Wed, 25 Nov 2009 14:41:40 +0200
From:	Matti Aarnio <mea@nic.funet.fi>
To:	Ralf Baechle <ralf@linux-mips.org>
Cc:	Matti Aarnio <mea@nic.funet.fi>, zmailer@nic.funet.fi
Subject: Re: [ZMailer] Zmailer breaks on Fedora 12
Message-ID: <20091125124140.GC11733@paja.nic.funet.fi>
References: <20091123224314.GA26735@linux-mips.org> <20091125113603.GB11733@paja.nic.funet.fi> <20091125123347.GA5225@linux-mips.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20091125123347.GA5225@linux-mips.org>
User-Agent: Mutt/1.4.2.1i
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

On Wed, Nov 25, 2009 at 12:33:47PM +0000, Ralf Baechle wrote:
> > The strace results below are rather surprising...
> > Your box is MIPS, which has different endianity, and all such funny things?
> 
> No; the system is which is a x86_64 virtual machine running on VMware ESX
> running pretty much a stock F12 - with maybe the biggest difference from a
> standard system being Zmailer :-)
> 
> I don't seem to have issues with any of the other databases btw.  Only
> the policy DB seems to be affected.  Where in the zmailer code is the
> filename for the policy db generated?

It is at  smtpserver.conf file.  The default file says essentially:

#
# The policy database:  (NOTE: See  'makedb'  for its default suffixes!)
#
PARAM  policydb        $DBTYPE  $MAILVAR/db/smtp-policy

The $MAILVAR  is read from   zmailer.conf  (where that is in your system),
and if you have there a string:

    MAILVAR=$LMVAR

that would explain at least part of the problem..  The variable substitution
engine does not handle double-indirections.

>   Ralf

Btw: zmailer.org  runs on Amd-X2 (x86-64) and F12, so all things being equal,
     I should be able to reproduce your problem..

-- 
/Matti Aarnio	<mea@nic.funet.fi>
--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Wed Nov 25 15:02:54 2009
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S77800AbZKYNCyKiodc (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Wed, 25 Nov 2009 15:02:54 +0200
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77802AbZKYNCyG5F0s
	(ORCPT <rfc822;zmailer-outgoing>); Wed, 25 Nov 2009 15:02:54 +0200
Received: from h5.dl5rb.org.uk ([81.2.74.5]:59129 "EHLO h5.dl5rb.org.uk"
	rhost-flags-OK-OK-OK-OK) by nic.funet.fi with ESMTP
	id S77800AbZKYNCx0qW5A (ORCPT <rfc822;zmailer@nic.funet.fi>);
	Wed, 25 Nov 2009 15:02:53 +0200
Received: from h5.dl5rb.org.uk (localhost.localdomain [127.0.0.1])
	by h5.dl5rb.org.uk (8.14.3/8.14.3) with ESMTP id nAPD39db006915;
	Wed, 25 Nov 2009 13:03:09 GMT
Received: (from ralf@localhost)
	by h5.dl5rb.org.uk (8.14.3/8.14.3/Submit) id nAPD39we006913;
	Wed, 25 Nov 2009 13:03:09 GMT
Date:	Wed, 25 Nov 2009 13:03:09 +0000
From:	Ralf Baechle <ralf@linux-mips.org>
To:	Matti Aarnio <mea@nic.funet.fi>
Cc:	zmailer@nic.funet.fi
Subject: Re: [ZMailer] Zmailer breaks on Fedora 12
Message-ID: <20091125130309.GB5225@linux-mips.org>
References: <20091123224314.GA26735@linux-mips.org> <20091125113603.GB11733@paja.nic.funet.fi> <20091125123347.GA5225@linux-mips.org> <20091125124140.GC11733@paja.nic.funet.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20091125124140.GC11733@paja.nic.funet.fi>
User-Agent: Mutt/1.5.19 (2009-01-05)
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

On Wed, Nov 25, 2009 at 02:41:40PM +0200, Matti Aarnio wrote:

> > I don't seem to have issues with any of the other databases btw.  Only
> > the policy DB seems to be affected.  Where in the zmailer code is the
> > filename for the policy db generated?
> 
> It is at  smtpserver.conf file.  The default file says essentially:
> 
> #
> # The policy database:  (NOTE: See  'makedb'  for its default suffixes!)
> #
> PARAM  policydb        $DBTYPE  $MAILVAR/db/smtp-policy
> 
> The $MAILVAR  is read from   zmailer.conf  (where that is in your system),
> and if you have there a string:
> 
>     MAILVAR=$LMVAR
> 
> that would explain at least part of the problem..  The variable substitution
> engine does not handle double-indirections.

# grep MAILVAR /etc/zmailer/zmailer.conf
MAILVAR=/etc/zmailer
#

Grepping through /etc/zmailer doesn't find a single instance of "LMVAR".

> Btw: zmailer.org  runs on Amd-X2 (x86-64) and F12, so all things being equal,
>      I should be able to reproduce your problem..

I'm just installing F12 into a VM so I have a chance to look into what is
going wrong.

  Ralf
--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Fri Nov 27 01:17:20 2009
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S77475AbZKZXRUOcvyQ (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Fri, 27 Nov 2009 01:17:20 +0200
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77705AbZKZXRUJKRqk
	(ORCPT <rfc822;zmailer-outgoing>); Fri, 27 Nov 2009 01:17:20 +0200
Received: from h5.dl5rb.org.uk ([81.2.74.5]:39133 "EHLO h5.dl5rb.org.uk"
	rhost-flags-OK-OK-OK-OK) by nic.funet.fi with ESMTP
	id S77475AbZKZXRTZ3QpI (ORCPT <rfc822;zmailer@nic.funet.fi>);
	Fri, 27 Nov 2009 01:17:19 +0200
Received: from h5.dl5rb.org.uk (localhost.localdomain [127.0.0.1])
	by h5.dl5rb.org.uk (8.14.3/8.14.3) with ESMTP id nAQNHZk1029608;
	Thu, 26 Nov 2009 23:17:36 GMT
Received: (from ralf@localhost)
	by h5.dl5rb.org.uk (8.14.3/8.14.3/Submit) id nAQNHZtk029607;
	Thu, 26 Nov 2009 23:17:35 GMT
Date:	Thu, 26 Nov 2009 23:17:34 +0000
From:	Ralf Baechle <ralf@linux-mips.org>
To:	Matti Aarnio <mea@nic.funet.fi>
Cc:	zmailer@nic.funet.fi
Subject: Re: [ZMailer] Zmailer breaks on Fedora 12
Message-ID: <20091126231734.GA28593@linux-mips.org>
References: <20091123224314.GA26735@linux-mips.org>
 <20091125113603.GB11733@paja.nic.funet.fi>
 <20091125123347.GA5225@linux-mips.org>
 <20091125124140.GC11733@paja.nic.funet.fi>
 <20091125130309.GB5225@linux-mips.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20091125130309.GB5225@linux-mips.org>
User-Agent: Mutt/1.5.20 (2009-08-17)
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

On Wed, Nov 25, 2009 at 01:03:09PM +0000, Ralf Baechle wrote:

> > > I don't seem to have issues with any of the other databases btw.  Only
> > > the policy DB seems to be affected.  Where in the zmailer code is the
> > > filename for the policy db generated?
> > 
> > It is at  smtpserver.conf file.  The default file says essentially:
> > 
> > #
> > # The policy database:  (NOTE: See  'makedb'  for its default suffixes!)
> > #
> > PARAM  policydb        $DBTYPE  $MAILVAR/db/smtp-policy
> > 
> > The $MAILVAR  is read from   zmailer.conf  (where that is in your system),
> > and if you have there a string:
> > 
> >     MAILVAR=$LMVAR
> > 
> > that would explain at least part of the problem..  The variable substitution
> > engine does not handle double-indirections.
> 
> # grep MAILVAR /etc/zmailer/zmailer.conf
> MAILVAR=/etc/zmailer
> #
> 
> Grepping through /etc/zmailer doesn't find a single instance of "LMVAR".
> 
> > Btw: zmailer.org  runs on Amd-X2 (x86-64) and F12, so all things being equal,
> >      I should be able to reproduce your problem..
> 
> I'm just installing F12 into a VM so I have a chance to look into what is
> going wrong.

So on this vanilla F12 VM with zmailer rebuilt on the VM intself I can't
reproduce the issue.  Will now copy the config files from the actual
server machine one by one and will also to use the binaries built on the
server machine which had the issue.

  Ralf
--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Wed Mar 31 06:27:11 2010
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S77021Ab0CaD1GVt9Ik (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Wed, 31 Mar 2010 06:27:06 +0300
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77473Ab0CaD1GMJzNA
	(ORCPT <rfc822;zmailer-outgoing>); Wed, 31 Mar 2010 06:27:06 +0300
Received: from mail-1.netbauds.net ([78.33.0.162]:22614 "EHLO
	mail-1.netbauds.net" rhost-flags-OK-OK-OK-OK) by nic.funet.fi
	with ESMTP id S77021Ab0CaD1F0HRm4 (ORCPT
	<rfc822;zmailer@nic.funet.fi>); Wed, 31 Mar 2010 06:27:05 +0300
Received: from 93-97-168-38.zone5.bethere.co.uk ([93.97.168.38]:58092 "EHLO
	odin.home.darrylmiles.org" smtp-auth: "darryl" TLS-CIPHER:
	"DHE-RSA-AES256-SHA keybits 256/256 version TLSv1/SSLv3" TLS-PEER-CN1:
	<none> rhost-flags-OK-OK-OK-FAIL) by mail-1.netbauds.net with ESMTPSA
	id S6751069Ab0CaD1D (ORCPT <rfc822;zmailer@nic.funet.fi>);
	Wed, 31 Mar 2010 04:27:03 +0100
Message-ID: <4BB2C106.30708@netbauds.net>
Date:	Wed, 31 Mar 2010 04:27:02 +0100
From:	"Darryl L. Miles" <darryl-mailinglists@netbauds.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB; rv:1.8.1.23) Gecko/20090823 SeaMonkey/1.1.18
MIME-Version: 1.0
To:	zmailer@nic.funet.fi
Subject: [ZMailer] Zmailer CVS down ?  SPF2 autoconf build issue!
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi


Hi,


Is Matti aware that the CVS server is down, however RSYNC is working ok.

$ cvs -d :pserver:cvs@anoncvs.zmailer.org:/cvsroot checkout zmailer
Fatal error, aborting.
cvs: no such system user



Also what is the recommended implementation of SPF2 to use ?  There is 
libspf2-1.x libspf2-2.x and libspf_alt.  If you configure and install 
this library on a Linux system it ends up in /usr/local/.

The ./configure for zmailer doesn't fully detect the existence of SPF2; 
it knows that spf2 is in /usr/local I can see that detected but it 
doesn't setup the appropriate config.h setting for the header file 
#include to use:

#define HAVE__USR_LOCAL_INCLUDE_SPF2_SPF_H 1

Due to the existence of /usr/local/include/spf2/spf.h.  I also can not 
find how or where the autoconf performs detection of this, is this 
implied by the existence of the define in config.h.in ?  I can see a 
shell variable $ac_cv_header__usr_local_include_spf2_spf_h in 
./configure but not being an autoconf expert I don't know how this gets 
setup.

Due to this the build fails at smtpserver where is it used.


Thanks,

Darryl

--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Mon May 17 19:55:49 2010
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S77346Ab0EQQzqNUWuA (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Mon, 17 May 2010 19:55:46 +0300
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77355Ab0EQQzqCYEmk
	(ORCPT <rfc822;zmailer-outgoing>); Mon, 17 May 2010 19:55:46 +0300
Received: from mail.Morgan-Systems.com ([204.16.172.8]:36481 "EHLO
	mail.morgan-systems.com" rhost-flags-OK-OK-OK-OK) by nic.funet.fi
	with ESMTP id S77346Ab0EQQzp0mRLA (ORCPT
	<rfc822;zmailer@nic.funet.fi>); Mon, 17 May 2010 19:55:45 +0300
Received: from Server-16.MorganSys.net ([10.30.1.16]:41219 "HELO
	Mail.Morgan-Systems.com" whoson: "-unregistered-" smtp-auth: <none>
	TLS-CIPHER: <none> TLS-PEER-CN1: <none> rhost-flags-OK-OK-OK-FAIL)
	by Mail.Morgan-Systems.com with SMTP id S1050146Ab0EQQzQ convert rfc822-to-8bit
	(ORCPT <rfc822;zmailer@nic.funet.fi>);
	Mon, 17 May 2010 09:55:16 -0700
X-Morgan-Systems-MailScanner-Watermark:	1274720121.50009@sVyLQuzvPlm5KAMHH+E5Vw
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8BIT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: [ZMailer] Reorder Queue/Channel, Delete Single Message
Date:	Mon, 17 May 2010 09:55:15 -0700
Message-ID: <6557A87A5B462247861990180A542B142665F5@server-16.MorganSys.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Reorder Queue/Channel, Delete Single Message
Thread-Index: Acr14bk3eLRzbG7GR1WuEoCH9Vvb8g==
From:	"Neal Morgan" <Neal@Morgan-Systems.com>
To:	<zmailer@nic.funet.fi>
X-Morgan-Systems-MailScanner-Information: Please contact the ISP for more information
X-MailScanner-ID: 105014617095516
X-Morgan-Systems-MailScanner: Found to be clean
X-Morgan-Systems-MailScanner-From: neal@morgan-systems.com
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

Greetings:

This is probably something I should already know.  Is there a way to
make zmailer re-order the queue for a particular channel/host when the
top message is being rejected by the receiving end?  We continually find
that aol will reject a message with a temporary error, then subsequent
messages will queue up behind it, and the queue grows larger and larger
until we take manual action to correct it.  Zmailer continues to want to
deliver the messages in the original order, meaning the newer messages
never get tried since the top message is in the way.  So, is it possible
to make zmailer put the message with the temporary error at the bottom
of the queue after some configurable number of retries?

We have been handling this manually, by deleting the offending top
message from both the transport and queue directories.  Is there a
zmailer-approved way to delete a single message for a channel/host?
We've just been using "rm" for this, then forcing a resubmit on that
channel/host.



Thanks,

Neal Morgan

--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Mon May 17 20:59:17 2010
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S77365Ab0EQR7NSLt7s (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Mon, 17 May 2010 20:59:13 +0300
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77368Ab0EQR7NMGpuY
	(ORCPT <rfc822;zmailer-outgoing>); Mon, 17 May 2010 20:59:13 +0300
Received: from doors.huapi.net.ar ([190.136.177.222]:40455 "EHLO
	doors.huapi.net.ar" rhost-flags-OK-OK-OK-OK) by nic.funet.fi
	with ESMTP id S77365Ab0EQR7M0taiQ (ORCPT
	<rfc822;zmailer@nic.funet.fi>); Mon, 17 May 2010 20:59:12 +0300
DKIM-Signature:	v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=huapi.ba.ar; s=mail;
	h=Subject:Content-Transfer-Encoding:Content-Type:In-Reply-To:References:CC:To:MIME-Version:From:Date:Message-ID; bh=C22q/4GBqcsZzo6f4H3AdVSvImjNaiYBlIQiGD0AtXs=;
	b=iaTPVjmuiX4e/r+ReMuzf/jNZEVtPMtACwvJ3QcsGM2KWroi1/E8WGUyipfgcrKRucauSwBtnQ/XcYzNfCiWinJNbdt7K5EI/vdLlUJzVhgOO/8W/LAsmaoG+1j/nGJ745LFeXDU1duIn/sZ5GSjUImclep0N+gA6PkiUWqz8TA=;
Received: from huapi.ba.ar ([172.30.0.2])
	by doors.huapi.net.ar with esmtp (Exim 4.71)
	(envelope-from <tron@huapi.ba.ar>)
	id 1OE4aq-000402-8D; Mon, 17 May 2010 14:59:08 -0300
Message-ID: <4BF183EB.1050808@huapi.ba.ar>
Date:	Mon, 17 May 2010 14:59:07 -0300
From:	Carlos G Mendioroz <tron@huapi.ba.ar>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To:	Neal Morgan <Neal@Morgan-Systems.com>
CC:	zmailer@nic.funet.fi
References: <6557A87A5B462247861990180A542B142665F5@server-16.MorganSys.net>
In-Reply-To: <6557A87A5B462247861990180A542B142665F5@server-16.MorganSys.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 172.30.0.2
X-SA-Exim-Mail-From: tron@huapi.ba.ar
X-Spam-Checker-Version:	SpamAssassin 3.2.5 (2008-06-10) on doors.huapi.net.ar
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 required=8.0 tests=ALL_TRUSTED,AWL,BAYES_20,
	DNS_FROM_OPENWHOIS autolearn=no version=3.2.5
Subject: Re: [ZMailer] Reorder Queue/Channel, Delete Single Message
X-SA-Exim-Version: 4.2.1 (built Thu, 26 Jun 2008 08:56:56 +0000)
X-SA-Exim-Scanned: Yes (on doors.huapi.net.ar)
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

I kind of remember that this sort of failure can be minimized by
setting 2 channels to work in parallel for delivery.

In any case, you may consider moving away from zmailer. World is moving
and zmailer is not. I've been a big fan of zmailer from Rayan's time,
then at UofT. But sadly, it's no longer a viable option IMHO.

-Carlos

Neal Morgan @ 17/05/2010 13:55 -0300 dixit:
> Greetings:
> 
> This is probably something I should already know.  Is there a way to
> make zmailer re-order the queue for a particular channel/host when the
> top message is being rejected by the receiving end?  We continually find
> that aol will reject a message with a temporary error, then subsequent
> messages will queue up behind it, and the queue grows larger and larger
> until we take manual action to correct it.  Zmailer continues to want to
> deliver the messages in the original order, meaning the newer messages
> never get tried since the top message is in the way.  So, is it possible
> to make zmailer put the message with the temporary error at the bottom
> of the queue after some configurable number of retries?
> 
> We have been handling this manually, by deleting the offending top
> message from both the transport and queue directories.  Is there a
> zmailer-approved way to delete a single message for a channel/host?
> We've just been using "rm" for this, then forcing a resubmit on that
> channel/host.
> 
> 
> 
> Thanks,
> 
> Neal Morgan
> 
> --
> To unsubscribe from this list: send the line "unsubscribe zmailer" in
> the body of a message to majordomo@nic.funet.fi

-- 
Carlos G Mendioroz  <tron@huapi.ba.ar>  LW7 EQI  Argentina
--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Mon May 17 22:46:19 2010
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S77039Ab0EQTqQnMZkY (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Mon, 17 May 2010 22:46:16 +0300
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77368Ab0EQTqQdJGAA
	(ORCPT <rfc822;zmailer-outgoing>); Mon, 17 May 2010 22:46:16 +0300
Received: from mail.Morgan-Systems.com ([204.16.172.8]:40553 "EHLO
	mail.morgan-systems.com" rhost-flags-OK-OK-OK-OK) by nic.funet.fi
	with ESMTP id S77039Ab0EQTqPdYxUs (ORCPT
	<rfc822;zmailer@nic.funet.fi>); Mon, 17 May 2010 22:46:15 +0300
Received: from Server-16.MorganSys.net ([10.30.1.16]:43252 "HELO
	Mail.Morgan-Systems.com" whoson: "-unregistered-" smtp-auth: <none>
	TLS-CIPHER: <none> TLS-PEER-CN1: <none> rhost-flags-OK-OK-OK-FAIL)
	by Mail.Morgan-Systems.com with SMTP id S1050133Ab0EQTpm convert rfc822-to-8bit
	(ORCPT <rfc822;zmailer@nic.funet.fi>);
	Mon, 17 May 2010 12:45:42 -0700
X-Morgan-Systems-MailScanner-Watermark:	1274730350.85484@Asf11fUuHjeV8NImTLoQ1Q
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8BIT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: RE: [ZMailer] Reorder Queue/Channel, Delete Single Message
Date:	Mon, 17 May 2010 12:45:41 -0700
Message-ID: <6557A87A5B462247861990180A542B14266603@server-16.MorganSys.net>
In-Reply-To: <4BF183EB.1050808@huapi.ba.ar>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ZMailer] Reorder Queue/Channel, Delete Single Message
Thread-Index: Acr16tMgMw0DliW4R36+6h2IJWQ0LAADfHQQ
References: <6557A87A5B462247861990180A542B142665F5@server-16.MorganSys.net> <4BF183EB.1050808@huapi.ba.ar>
From:	"Neal Morgan" <Neal@Morgan-Systems.com>
To:	<zmailer@nic.funet.fi>
X-Morgan-Systems-MailScanner-Information: Please contact the ISP for more information
X-MailScanner-ID: 105013317124542
X-Morgan-Systems-MailScanner: Found to be clean
X-Morgan-Systems-MailScanner-From: neal@morgan-systems.com
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

> > Neal Morgan @ 17/05/2010 13:55 -0300 dixit:
> > Greetings:
> > 
> > This is probably something I should already know.  Is there a way to
> > make zmailer re-order the queue for a particular channel/host when
the
> > top message is being rejected by the receiving end?  We continually
find
> > that aol will reject a message with a temporary error, then
subsequent
> > messages will queue up behind it, and the queue grows larger and
larger
> > until we take manual action to correct it.  Zmailer continues to
want to
> > deliver the messages in the original order, meaning the newer
messages
> > never get tried since the top message is in the way.  So, is it
possible
> > to make zmailer put the message with the temporary error at the
bottom
> > of the queue after some configurable number of retries?
> > 
> > We have been handling this manually, by deleting the offending top
> > message from both the transport and queue directories.  Is there a
> > zmailer-approved way to delete a single message for a channel/host?
> > We've just been using "rm" for this, then forcing a resubmit on that
> > channel/host.
> > 
> > 
> > 
> > Thanks,
> > 
> > Neal Morgan
> 
> on Monday, May 17, 2010 10:59 AM  Carlos G Mendioroz wrote 
> 
> I kind of remember that this sort of failure can be minimized by
> setting 2 channels to work in parallel for delivery.
>
> In any case, you may consider moving away from zmailer. World is
moving
> and zmailer is not. I've been a big fan of zmailer from Rayan's time,
> then at UofT. But sadly, it's no longer a viable option IMHO.
>
> -Carlos
>

Have you moved on to something else?  What did you choose?

Having climbed much of the learning curve with Zmailer, I have stuck
with it.  With modifications to your MailScanner hooks, it has been
working good for years.  I think I have a dozen instances of it on
various servers.

On the other hand, it hasn't been included in the Debian packages for
years now, and I think the rest of the world thinks it is dead.  I'm
pretty sure Matti is still out there, and would still write fixes if
they were necessary.

 
--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Mon May 17 23:06:35 2010
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S77368Ab0EQUGcCBGNQ (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Mon, 17 May 2010 23:06:32 +0300
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77377Ab0EQUGb4Ow84
	(ORCPT <rfc822;zmailer-outgoing>); Mon, 17 May 2010 23:06:31 +0300
Received: from doors.huapi.net.ar ([190.136.177.222]:34994 "EHLO
	doors.huapi.net.ar" rhost-flags-OK-OK-OK-OK) by nic.funet.fi
	with ESMTP id S77368Ab0EQUGa4sqJA (ORCPT
	<rfc822;zmailer@nic.funet.fi>); Mon, 17 May 2010 23:06:30 +0300
DKIM-Signature:	v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=huapi.ba.ar; s=mail;
	h=Subject:Content-Transfer-Encoding:Content-Type:In-Reply-To:References:CC:To:MIME-Version:From:Date:Message-ID; bh=cQtdUUckspx6PA/fKtA5agF+puOFtR4dl6YMASWqoo4=;
	b=HvIXNmJYi9XUPf6VvJx7QO7685T2DyeXFgguJEKz4VvVRjXt5lvRGQUxmnnHg4BAJ/Y/PefYAwgwm0Zy1N9QsnRPR6jj86jKgNxT7OIhr+KUpAKd5FhkMff3IECyH/u3Qm3vm2//pRBD0mcDLKVwh6IgZgtrnBuaJivQuLSFXcY=;
Received: from huapi.ba.ar ([172.30.0.2])
	by doors.huapi.net.ar with esmtp (Exim 4.71)
	(envelope-from <tron@huapi.ba.ar>)
	id 1OE6a2-0004aK-3L; Mon, 17 May 2010 17:06:26 -0300
Message-ID: <4BF1A1C1.5000302@huapi.ba.ar>
Date:	Mon, 17 May 2010 17:06:25 -0300
From:	Carlos G Mendioroz <tron@huapi.ba.ar>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To:	Neal Morgan <Neal@Morgan-Systems.com>
CC:	zmailer@nic.funet.fi
References: <6557A87A5B462247861990180A542B142665F5@server-16.MorganSys.net> <4BF183EB.1050808@huapi.ba.ar> <6557A87A5B462247861990180A542B14266603@server-16.MorganSys.net>
In-Reply-To: <6557A87A5B462247861990180A542B14266603@server-16.MorganSys.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 172.30.0.2
X-SA-Exim-Mail-From: tron@huapi.ba.ar
X-Spam-Checker-Version:	SpamAssassin 3.2.5 (2008-06-10) on doors.huapi.net.ar
X-Spam-Level: 
X-Spam-Status: No, score=-1.8 required=8.0 tests=ALL_TRUSTED,AWL,BAYES_40,
	DNS_FROM_OPENWHOIS autolearn=no version=3.2.5
Subject: Re: [ZMailer] Reorder Queue/Channel, Delete Single Message
X-SA-Exim-Version: 4.2.1 (built Thu, 26 Jun 2008 08:56:56 +0000)
X-SA-Exim-Scanned: Yes (on doors.huapi.net.ar)
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi



Neal Morgan @ 17/05/2010 16:45 -0300 dixit:
>>> Neal Morgan @ 17/05/2010 13:55 -0300 dixit:
>>> Greetings:
>>>
>>> This is probably something I should already know.  Is there a way to
>>> make zmailer re-order the queue for a particular channel/host when
> the
>>> top message is being rejected by the receiving end?  We continually
> find
>>> that aol will reject a message with a temporary error, then
> subsequent
>>> messages will queue up behind it, and the queue grows larger and
> larger
>>> until we take manual action to correct it.  Zmailer continues to
> want to
>>> deliver the messages in the original order, meaning the newer
> messages
>>> never get tried since the top message is in the way.  So, is it
> possible
>>> to make zmailer put the message with the temporary error at the
> bottom
>>> of the queue after some configurable number of retries?
>>>
>>> We have been handling this manually, by deleting the offending top
>>> message from both the transport and queue directories.  Is there a
>>> zmailer-approved way to delete a single message for a channel/host?
>>> We've just been using "rm" for this, then forcing a resubmit on that
>>> channel/host.
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Neal Morgan
>> on Monday, May 17, 2010 10:59 AM  Carlos G Mendioroz wrote 
>>
>> I kind of remember that this sort of failure can be minimized by
>> setting 2 channels to work in parallel for delivery.
>>
>> In any case, you may consider moving away from zmailer. World is
> moving
>> and zmailer is not. I've been a big fan of zmailer from Rayan's time,
>> then at UofT. But sadly, it's no longer a viable option IMHO.
>>
>> -Carlos
>>
> 
> Have you moved on to something else?  What did you choose?
> 
> Having climbed much of the learning curve with Zmailer, I have stuck
> with it.  With modifications to your MailScanner hooks, it has been
> working good for years.  I think I have a dozen instances of it on
> various servers.
> 
> On the other hand, it hasn't been included in the Debian packages for
> years now, and I think the rest of the world thinks it is dead.  I'm
> pretty sure Matti is still out there, and would still write fixes if
> they were necessary.
> 
>  
Yes, I've moved to Exim4. (More exactly, I'm in the process of moving
many installations to ~).
Along the years, the flexibility of zmailer has become a trap difficult
to escape from, and the beauty of routing and then delivering with a
small footprint is appealing.

As I said, I loved it, but decided to move on.
-Carlos (already been called a traitor :)

-- 
Carlos G Mendioroz  <tron@huapi.ba.ar>  LW7 EQI  Argentina
--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Tue May 18 02:03:21 2010
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S77390Ab0EQXDVZPrps (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Tue, 18 May 2010 02:03:21 +0300
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77393Ab0EQXDVPsRuQ
	(ORCPT <rfc822;zmailer-outgoing>); Tue, 18 May 2010 02:03:21 +0300
Received: from poczta.medcom.com.pl ([83.238.4.20]:48643 "EHLO
	poczta.medcom.com.pl" rhost-flags-OK-OK-OK-OK) by nic.funet.fi
	with ESMTP id S77390Ab0EQXDUkmQ7A (ORCPT
	<rfc822;zmailer@nic.funet.fi>); Tue, 18 May 2010 02:03:20 +0300
Received: (from localhost user: 'bartek' uid#1000 fake: STDIN
	(bartek@poczta.medcom.com.pl)) by poczta.medcom.com.pl
	id S367914Ab0EQXDT (ORCPT <rfc822;zmailer@nic.funet.fi>);
	Tue, 18 May 2010 01:03:19 +0200
Date:	Tue, 18 May 2010 01:03:19 +0200
From:	Bartek Krajnik <bartek@bmk-it.com>
To:	Carlos G Mendioroz <tron@huapi.ba.ar>
Cc:	Neal Morgan <Neal@Morgan-Systems.com>, zmailer@nic.funet.fi
Subject: Re: [ZMailer] Reorder Queue/Channel, Delete Single Message
Message-ID: <20100517230318.GA22235@poczta.medcom.com.pl>
References: <6557A87A5B462247861990180A542B142665F5@server-16.MorganSys.net> <4BF183EB.1050808@huapi.ba.ar> <6557A87A5B462247861990180A542B14266603@server-16.MorganSys.net> <4BF1A1C1.5000302@huapi.ba.ar>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4BF1A1C1.5000302@huapi.ba.ar>
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

On 17-05-2010 at 05:06:25PM -0300, Carlos G Mendioroz wrote:
> Neal Morgan @ 17/05/2010 16:45 -0300 dixit:
> > Have you moved on to something else?  What did you choose?
>
> Yes, I've moved to Exim4. (More exactly, I'm in the process of moving
> many installations to ~).
> Along the years, the flexibility of zmailer has become a trap difficult
> to escape from, and the beauty of routing and then delivering with a
> small footprint is appealing.
> 

It depends.
How much traffic supports mail server?

Exim is more user friendly regards some fast config changes (like queues) and has more users (more sites, more help).
Exim has more tools in most of standard linux distributions.
Exim works not on root id.

But exim is not so fast.

HTH
--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Wed May 19 14:53:42 2010
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S77554Ab0ESLxhoaeOQ (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Wed, 19 May 2010 14:53:37 +0300
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77550Ab0ESLxhjHfec
	(ORCPT <rfc822;zmailer-outgoing>); Wed, 19 May 2010 14:53:37 +0300
Received: (mea@paja.nic.funet.fi) by nic.funet.fi id S77544Ab0ESLxg1Avfc
	(ORCPT <rfc822;zmailer@nic.funet.fi>);
	Wed, 19 May 2010 14:53:36 +0300
Date:	Wed, 19 May 2010 14:53:36 +0300
From:	Matti Aarnio <mea@nic.funet.fi>
To:	Darryl Miles <darryl-mailinglists@netbauds.net>
Cc:	Bartek Krajnik <bartek@bmk-it.com>,
	Carlos G Mendioroz <tron@huapi.ba.ar>,
	Neal Morgan <Neal@Morgan-Systems.com>, zmailer@nic.funet.fi
Subject: Re: [ZMailer] Reorder Queue/Channel, Delete Single Message
Message-ID: <20100519115336.GB22072@paja.nic.funet.fi>
References: <6557A87A5B462247861990180A542B142665F5@server-16.MorganSys.net> <4BF183EB.1050808@huapi.ba.ar> <6557A87A5B462247861990180A542B14266603@server-16.MorganSys.net> <4BF1A1C1.5000302@huapi.ba.ar> <20100517230318.GA22235@poczta.medcom.com.pl> <4BF24463.5040406@netbauds.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4BF24463.5040406@netbauds.net>
User-Agent: Mutt/1.4.2.1i
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

On Tue, May 18, 2010 at 08:40:19AM +0100, Darryl Miles wrote:
> >It depends.
> >How much traffic supports mail server?
> >
> >Exim is more user friendly regards some fast config changes (like queues) 
> >and has more users (more sites, more help).
> >Exim has more tools in most of standard linux distributions.
> >Exim works not on root id.

For most parts ZMailer works fine on non-root id.
Only part needing root is when smtpserver is binding on port 25 et.al.
and the scheduler on the mailq.
(Even those can be hacked in platform dependent ways - like SE Linux
supplying special privileges to smtpserver binary to bind to allocated
ports without root capability.)


> >But exim is not so fast.
> 
> Those that do use Exim (or anything else for that matter) do they have:
>  * A top 10 list of the features most in demand.
>  * A top 10 gripe list of things Zmailer does badly.
> 
> Also what platforms do you care about ?
> 
> One factor with Zmailer in order to make progress forward is that it 
> needs to expunge all circa 1990-2002s cruft.  These days there isn't 
> that must diversity between platforms, the inefficiencies/bugs of 
> platform provided libraries isn't so significant as CPUs have become 
> faster, etc...

The IO to persistent storage is always "slow".
Present ZMailer's queue file handling is reasonably fast by minimizing
operations that generate physical IO, and if really necessary, one can
spread the postoffice around multiple spindles.  However these days
you probably pick an SSD for a postoffice spool disk instead of old
style spinning electromechanical devices.  Mailbox storage is entirely
different animal.

The modern ultra-fast CPUs make physical IO painfully obvious.

An extreme example of what the email load is being served by ZMailer
can be seen here:

  http://vger.kernel.org/z/

However its loading is radically different from your average mailbox server.
It is email-list system installation - one message in, 1000+ out.


> The major platforms I see today are Linux/xBSD/Solaris.  Who runs a mail 
> service on anything else and why (i.e. price/performance/maintenance) ? 
>  I'm sure people do but I'm also sure it becomes hard to justify 
> continuing to do so as the years roll by.

The GNU Autoconfig framework helps a lot on keeping around the support for
less used platforms.  Of course platforms without testing are prone to get
affected by bitrot..


> Matti has done a fine job of being gatekeeper for zmailer over the past 
> decade it would be kind of nice to hear his point of view on development 
> and usage also.

Queue scheduler management interface is missing.
Mainly a management _tool_ is missing - kick this message from that queue,
start that queue ("SMTP ETRN" hack exists, though.) etc.

Improving the hacky interface layer at smtpserver to run message content
scanners needs some work.

Improving the documentation.

The default queue modelling is also a bit difficult at times.  Namely sticking
on arrival order can result in stuck queue, as only first one is tried.
Original model was to randomize the queue order before delivery attempts, but
some sort of hybride might be better - prefer arrival order, if a retry is
ordered then put the troubled message on tail of the queue and try new queue
leader, but do not try too many... ( 500 messages, stuck because of 'connection
timed out', no point in retrying them all ad-infinitum.  Give the transport
agent channel to some other target thread for a while.)

Also these days I might brave the universe, and declare pthreads as a fundamental
resource available everywhere.  It would result in a radically different software
with tons of spinlocks to protect the queue data models.  That would affect
scheduler's construction.

At work I usually do Java programs using existing java.util.* classes to
do most of my heavy lifting with data structures.   (I use also Perl, and
ANSI-C, case depending..)

Rewriting entire system in Java is out of the question.  Rewriting major
parts of it even in C++ is very great challenge, and I don't have that much
free time.  I do not see that I would get immediate maintenance benefits
and/or improved features from doing such a thing.

Furthermore, I don't do email for a job anymore.  Just for a hobby.

> Darryl

-- 
/Matti Aarnio	<mea@nic.funet.fi>
--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Thu May 20 22:00:31 2010
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S77652Ab0ETTA1ArHIs (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Thu, 20 May 2010 22:00:27 +0300
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77659Ab0ETTA0uQ3Bs
	(ORCPT <rfc822;zmailer-outgoing>); Thu, 20 May 2010 22:00:26 +0300
Received: from mail.dm.uba.ar ([157.92.22.1]:36384 "EHLO mail.dm.uba.ar"
	rhost-flags-OK-OK-OK-OK) by nic.funet.fi with ESMTP
	id S77651Ab0ETTAZKBbLQ (ORCPT <rfc822;zmailer@nic.funet.fi>);
	Thu, 20 May 2010 22:00:25 +0300
Received: from mate36.dm.uba.ar ([157.92.22.36]:1868 "EHLO [157.92.22.36]"
	smtp-auth: <none> TLS-CIPHER: <none> TLS-PEER-CN1: <none>
	rhost-flags-OK-OK-OK-FAIL) by mail.dm.uba.ar with ESMTP
	id S29680408Ab0ETTAO (ORCPT <rfc822;zmailer@nic.funet.fi> + 1 other);
	Thu, 20 May 2010 16:00:14 -0300
Message-ID: <4BF586BA.3000401@dm.uba.ar>
Date:	Thu, 20 May 2010 16:00:10 -0300
From:	Rodolfo Cossalter <rcoss@dm.uba.ar>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To:	Ralf Baechle <ralf@linux-mips.org>
CC:	Matti Aarnio <mea@nic.funet.fi>,
	Neal Morgan <Neal@Morgan-Systems.com>, zmailer@nic.funet.fi
Subject: Re: [ZMailer] Zmailer crashes
References: <20081031160305.GB9632@linux-mips.org> <7D1CC61717004141A57CA6CA1C8087EC38ED0B@server-16.MorganSys.net> <20090201135244.GA8440@paja.nic.funet.fi> <20090204150955.GA24046@linux-mips.org> <20091009144600.GA19375@linux-mips.org>
In-Reply-To: <20091009144600.GA19375@linux-mips.org>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

Matti, Ralf, Neal,

I'm also getting segfaults from router, a few of them every week.
It's a Debian Linux box:
Linux mail 2.6.31.5 #1 SMP Mon Oct 26 23:42:58 ART 2009 x86_64 GNU/Linux
Zmailer sources from Eugene's CVS.
I've turned on core dumps (ulimit -Sc 51200 in the shell that
starts/restarts the router) but couldn't ever get a core file, however,
if I signal the router process with kill -SIGSEGV pid I get a core file
(useless).
So I decided to run gdb and attach to each router process (router -dkn
2) and wait...
This is what I got when router finally segfaulted.
Can anybody help with this gdb trace?

Thanks
Rodolfo

--------------------------------
(gdb) attach 27737
Attaching to process 27737
Reading symbols from /usr/local/zmailer/bin/router...done.
Reading symbols from /lib/libcrypt.so.1...Reading symbols from
/usr/lib/debug/lib/libcrypt-2.7.so...done.
done.
Loaded symbols for /lib/libcrypt.so.1
Reading symbols from /usr/lib/libdb-4.6.so...done.
Loaded symbols for /usr/lib/libdb-4.6.so
Reading symbols from /usr/lib/libgdbm.so.3...done.
Loaded symbols for /usr/lib/libgdbm.so.3
Reading symbols from /lib/libresolv.so.2...Reading symbols from
/usr/lib/debug/lib/libresolv-2.7.so...done.
done.
Loaded symbols for /lib/libresolv.so.2
Reading symbols from /lib/libc.so.6...Reading symbols from
/usr/lib/debug/lib/libc-2.7.so...done.
done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/libpthread.so.0...Reading symbols from
/usr/lib/debug/lib/libpthread-2.7.so...done.
[Thread debugging using libthread_db enabled]
[New Thread 0x7f9ecb9136e0 (LWP 27737)]
done.
Loaded symbols for /lib/libpthread.so.0
Reading symbols from /lib/ld-linux-x86-64.so.2...Reading symbols from
/usr/lib/debug/lib/ld-2.7.so...done.
done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
0x00007f9ecade2960 in __read_nocancel () from /lib/libc.so.6
(gdb) c
Continuing.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f9ecb9136e0 (LWP 27737)]
0x0000000000412ae8 in router (a=0x10c8570, uid=370, type=0x46fae8 "sender",
    senderstr=0x0) at shliaise.c:678
678                     if (p->p_type == anAddress) {
(gdb) where
#0  0x0000000000412ae8 in router (a=0x10c8570, uid=370,
    type=0x46fae8 "sender", senderstr=0x0) at shliaise.c:678
#1  0x00000000004168d8 in thesender (e=0x10c6c88, a=0x10c8570) at
rfc822.c:1175
#2  0x0000000000419c4f in sequencer (e=0x10c6c88, file=0xddf860 "29680333")
    at rfc822.c:1767
#3  0x0000000000413584 in run_rfc822 (argc=2, argv=0x7fff67e50280)
    at rfc822.c:165
#4  0x0000000000449b5a in execute (c=0x7fff67e51a30, caller=0x7fff67e53400,
    oretcode=0, name=0x46dccd "rfc822") at execute.c:397
#5  0x000000000043471a in runcommand (c=0x7fff67e51a30, pc=0x7fff67e53400,
    retcodep=0x7fff67e534dc, cmdname=0x46dccd "rfc822") at interpret.c:762
#6  0x00000000004379b4 in interpret (Vcode=0xdb0130, Veocode=0xdb03cb,
    Ventry=0xdb013f, caller=0x7fff67e53400, retcodep=0x7fff67e534dc,
    cdp=0xdafef0) at interpret.c:1805
#7  0x000000000043bc08 in lapply (fname=0x4713ab "process",
l=0x7f9eca818e58)
    at interpret.c:2881
#8  0x000000000043bcc0 in apply (argc=2, argv=0x7fff67e53910)
    at interpret.c:2905
#9  0x000000000040ff4b in s_apply (argc=2, argv=0x7fff67e53910)
    at shliaise.c:71
#10 0x0000000000429ca1 in rd_doit (filename=0x7fff67e53620 "29680333",
    dirs=0x7fff67e539a8 "") at daemonsub.c:1454
#11 0x0000000000428bf0 in child_server (tofd=0, frmfd=1) at daemonsub.c:799
#12 0x0000000000427c03 in start_child (i=0) at daemonsub.c:276
#13 0x000000000042a3e8 in run_daemon (argc=1, argv=0x7fff67e55d20)
    at daemonsub.c:1652
#14 0x0000000000404db8 in main (argc=3, argv=0x7fff67e55f18) at router.c:419
(gdb)
------------------------
Ralf Baechle escribió:
> On Wed, Feb 04, 2009 at 03:09:55PM +0000, Ralf Baechle wrote:
> 
>>> On Fri, Jan 30, 2009 at 03:32:31PM -0800, Neal Morgan wrote:
>>>>> On October 31, 2008 9:03 AM Ralf Baechle wrote
>>>>> Since quite a while I'm observing these kernel messages on a Linux x86_64
>>>>> system:
>>>>>
>>>>> sm[3270]: segfault at 3ba7f9f0 ip 79fbc9 sp 7fffe7c48e30 error 6 in
>>>> libc-2.7.so[72d000+14d000]
>>>>> sm[3493] trap stack segment ip:7f0e2a121bc9 sp:7fff3240e4a0 error:0
>>>>> sm[3773]: segfault at 3ba7f9f0 ip 79fbc9 sp 7fff55499680 error 6 in
>>>> libc-2.7.so[72d000+14d000]
>>>>
>>>> Matti: I've been seeing these across 4 servers:
>>>>
>>>> kernel: smtpserver[31693]: segfault at 00000000 eip b7c16371 esp
>>>> bf94b018 error 4
>>>>
>>>> kernel: router[9934]: segfault at 00000008 eip 0807fa95 esp bfdf5570
>>>> error 4
>>>>
>>>> The interesting thing is it only happens when booted into a 2.6.24
>>>> kernel.  If I reboot the same box into a 2.6.18 kernel everything runs
>>>> fine (and there are no segfaults).
>> Older kernels don't emit this segfault message.  It was added in
>> commit abd4f7505bafdd6c5319fe3cb5caf9af6104e17a that is for 2.6.23.  Could
>> that be why you didn't notice it earlier?
>>
>>> I do see them too with 2.6.26 kernel at zmailer.org server.
>>> A few hits per week according to kernel dmesg logs.
>>>
>>> I suspect more about glibc doing something stupid, than program really
>>> going over the edge, but these are so rare that debugging them is next
>>> to impossible.   Previously I have seen them happen after the program
>>> has called exit(0).
>>>
>>> Anyway I have turned on core dumps to be able to see what happens.
>> I've seen Zmailer stopping mail delivery or stopping accepting connections
>> on port 25.  The issue is hitting relativly infrequently but I decieded to
>> follow your example and just turned on core dumps; it is affecting sm,
>> smtpserver and router.  Lately the frequency of this issue striking
>> seems to have increased significantly - I wonder if that's due to me
>> looking more frequently after it or due to my extremly inflated mail
>> queue with over 1,700,000 stored messages.
>>
>> Ironically I seem to have gotten another router segfault just seconds
>> before I enabled core dumps ...
> 
> To close this old case - the issue went away for me after upgrading the
> system from Fedora 8 to Fedora 10.  So I assume there indeed as suspected
> by Matti was something toxic in glibc.
> 
>   Ralf
> --
> To unsubscribe from this list: send the line "unsubscribe zmailer" in
> the body of a message to majordomo@nic.funet.fi

--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Thu May 20 22:42:03 2010
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S77661Ab0ETTl7qO0RI (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Thu, 20 May 2010 22:41:59 +0300
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77668Ab0ETTl7gEm4c
	(ORCPT <rfc822;zmailer-outgoing>); Thu, 20 May 2010 22:41:59 +0300
Received: from mail.Morgan-Systems.com ([204.16.172.8]:36707 "EHLO
	mail.morgan-systems.com" rhost-flags-OK-OK-OK-OK) by nic.funet.fi
	with ESMTP id S77661Ab0ETTl6qVNMY (ORCPT
	<rfc822;zmailer@nic.funet.fi>); Thu, 20 May 2010 22:41:58 +0300
Received: from Server-16.MorganSys.net ([10.30.1.16]:30855 "HELO
	Mail.Morgan-Systems.com" whoson: "-unregistered-" smtp-auth: <none>
	TLS-CIPHER: <none> TLS-PEER-CN1: <none> rhost-flags-OK-OK-OK-FAIL)
	by Mail.Morgan-Systems.com with SMTP id S1050407Ab0ETTl0 convert rfc822-to-8bit
	(ORCPT <rfc822;zmailer@nic.funet.fi>);
	Thu, 20 May 2010 12:41:26 -0700
X-Morgan-Systems-MailScanner-Watermark:	1274989294.32891@s0vv6PKKxgAM8c/rtjzCNQ
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8BIT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: RE: [ZMailer] Zmailer crashes
Date:	Thu, 20 May 2010 12:41:26 -0700
Message-ID: <6557A87A5B462247861990180A542B14266639@server-16.MorganSys.net>
In-Reply-To: <4BF586BA.3000401@dm.uba.ar>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ZMailer] Zmailer crashes
Thread-Index: Acr4TtoWetZc01GtTnuqLLhzQpm/NgABIHrQ
References: <20081031160305.GB9632@linux-mips.org> <7D1CC61717004141A57CA6CA1C8087EC38ED0B@server-16.MorganSys.net> <20090201135244.GA8440@paja.nic.funet.fi> <20090204150955.GA24046@linux-mips.org> <20091009144600.GA19375@linux-mips.org> <4BF586BA.3000401@dm.uba.ar>
From:	"Neal Morgan" <Neal@Morgan-Systems.com>
To:	<zmailer@nic.funet.fi>
X-Morgan-Systems-MailScanner-Information: Please contact the ISP for more information
X-MailScanner-ID: 105040720124126
X-Morgan-Systems-MailScanner: Found to be clean
X-Morgan-Systems-MailScanner-From: neal@morgan-systems.com
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

> on Thursday, May 20, 2010 12:00 PM Ralf Baechle wrote:
> 
> I'm also getting segfaults from router, a few of them every week.
> It's a Debian Linux box:
> Linux mail 2.6.31.5 #1 SMP Mon Oct 26 23:42:58 ART 2009 x86_64
GNU/Linux Zmailer sources from Eugene's CVS.
> I've turned on core dumps (ulimit -Sc 51200 in the shell that
starts/restarts the router) but couldn't ever get a core file, however,
if I > signal the router process with kill -SIGSEGV pid I get a core
file (useless).
> So I decided to run gdb and attach to each router process (router -dkn
> 2) and wait...
> This is what I got when router finally segfaulted.
> Can anybody help with this gdb trace?

Rodolfo:

Hopefully Matti will be able to provide some insight on your core dump.

FWIW, my original issue with SMTPServer and segfaults went away
somewhere between upgrading Debian/kernel (to 2.6.26) and getting latest
ZMailer from CVS and rebuilding.  I am not sure which of those two fixed
it, but one of them did.

I do still get the router segfaults - like you.  However, this only
seems to be happening on my two busier machines (which happen to both be
x64).  My less busy (x86) machines are not experiencing segfaults.

Most importantly, I see no evidence the segfaults are causing mail loss
or delivery delays.  A new router process is created and things continue
as normal.  (Don't get me wrong, it would be best not to get the
segfaults...it just becomes less of a priority knowing mail is still
being delivered).

I'll look forward to suggestions from Matti.


Thanks,

Neal 

--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Thu May 20 23:04:42 2010
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S77696Ab0ETUEly0sns (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Thu, 20 May 2010 23:04:41 +0300
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77709Ab0ETUEltnHYQ
	(ORCPT <rfc822;zmailer-outgoing>); Thu, 20 May 2010 23:04:41 +0300
Received: from mail.Morgan-Systems.com ([204.16.172.8]:34992 "EHLO
	mail.morgan-systems.com" rhost-flags-OK-OK-OK-OK) by nic.funet.fi
	with ESMTP id S77696Ab0ETUEk6DOmI (ORCPT
	<rfc822;zmailer@nic.funet.fi>); Thu, 20 May 2010 23:04:40 +0300
Received: from Server-16.MorganSys.net ([10.30.1.16]:31146 "HELO
	Mail.Morgan-Systems.com" whoson: "-unregistered-" smtp-auth: <none>
	TLS-CIPHER: <none> TLS-PEER-CN1: <none> rhost-flags-OK-OK-OK-FAIL)
	by Mail.Morgan-Systems.com with SMTP id S1050135Ab0ETUEQ convert rfc822-to-8bit
	(ORCPT <rfc822;zmailer@nic.funet.fi>);
	Thu, 20 May 2010 13:04:16 -0700
X-Morgan-Systems-MailScanner-Watermark:	1274990658.29789@WjBK664DwRqOAC93cC8TJg
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8BIT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: RE: [ZMailer] Retry Order in Scheduler.conf
Date:	Thu, 20 May 2010 13:04:16 -0700
Message-ID: <6557A87A5B462247861990180A542B1426663A@server-16.MorganSys.net>
In-Reply-To: <6557A87A5B462247861990180A542B144BED@server-16.MorganSys.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ZMailer] Retry Order in Scheduler.conf
Thread-Index: AcoLxZa9rHZLN2LBS7ybqPOqGFaYmjskFkCg
References: <6557A87A5B462247861990180A542B144BED@server-16.MorganSys.net>
From:	"Neal Morgan" <Neal@Morgan-Systems.com>
To:	<zmailer@nic.funet.fi>
X-Morgan-Systems-MailScanner-Information: Please contact the ISP for more information
X-MailScanner-ID: 105013520130416
X-Morgan-Systems-MailScanner: Found to be clean
X-Morgan-Systems-MailScanner-From: neal@morgan-systems.com
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

> on Thursday, July 23, 2009 11:44 AM Neal Morgan wrote:
> 
> Is there a way to change the retry order for a particular Channel/Host
in the scheduler?
> 
> From time to time I will have a destination reject the first message
in the queue for 
> something related to content, and zmailer waits/retries patiently in
the same order
> until I either remove the offending message or the destination changes
its mind and 
> accepts the message.
> 
> I am wondering if there is a way to make it start with a different
message on the next 
> retry rather than continue trying to deliver in order.
> 
> I see an "AgeOrder" parameter in the scheduler.conf, but I don't see
any mention of it 
> in the man page, and I am not finding any alternatives to this that
look like what I want.
> 
> Does such a mechanism exist?  


For the sake of documentation, I am going to answer my own question
here.

It appears there is no opposite parm for "ageorder" in scheduler.conf.
You can disable it by commenting out the parm (e.g. "# ageorder") and
restarting zmailer.  Once disabled, scheduler seems to use a random
order instead of a strict age order.  (The answer was found in Matti's
comments in the ChangeLog from 10 May 2003).

If you are experiencing problems (for example, with AOL) where one
message is being rejected so the queue grows and grows for that
channel/host - you will want to make this change.  Be careful you only
have one scheduler.conf - or if like me you have somehow ended up with
more than one of these files in the config directories - change them all
just to be sure).

If you are concerned that randomorder will introduce delivery delays -
don't be.  My observation is zmailer gets rid of messages so fast this
is a non-issue.



Matti - A feature request: it would be nice to implement another parm
named randomorder so the choice between age order and random order is
obvious and can be overridden both globally as well as on individual
channel/hosts.
--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Thu May 20 23:29:43 2010
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S77718Ab0ETU3hpOWSA (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Thu, 20 May 2010 23:29:37 +0300
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77719Ab0ETU3hiELCc
	(ORCPT <rfc822;zmailer-outgoing>); Thu, 20 May 2010 23:29:37 +0300
Received: from mail.Morgan-Systems.com ([204.16.172.8]:34140 "EHLO
	mail.morgan-systems.com" rhost-flags-OK-OK-OK-OK) by nic.funet.fi
	with ESMTP id S77717Ab0ETU3gcGiYk (ORCPT
	<rfc822;zmailer@nic.funet.fi>); Thu, 20 May 2010 23:29:36 +0300
Received: from Server-16.MorganSys.net ([10.30.1.16]:31407 "HELO
	Mail.Morgan-Systems.com" whoson: "-unregistered-" smtp-auth: <none>
	TLS-CIPHER: <none> TLS-PEER-CN1: <none> rhost-flags-OK-OK-OK-FAIL)
	by Mail.Morgan-Systems.com with SMTP id S1050167Ab0ETU3D convert rfc822-to-8bit
	(ORCPT <rfc822;zmailer@nic.funet.fi>);
	Thu, 20 May 2010 13:29:03 -0700
X-Morgan-Systems-MailScanner-Watermark:	1274992154.78823@9o382RYcm3IB6GwcAwUAzQ
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8BIT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: RE: [ZMailer] Reorder Queue/Channel, Delete Single Message
Date:	Thu, 20 May 2010 13:29:02 -0700
Message-ID: <6557A87A5B462247861990180A542B1426663B@server-16.MorganSys.net>
In-Reply-To: <6557A87A5B462247861990180A542B142665F5@server-16.MorganSys.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ZMailer] Reorder Queue/Channel, Delete Single Message
Thread-Index: Acr14bk3eLRzbG7GR1WuEoCH9Vvb8gCdfU/A
References: <6557A87A5B462247861990180A542B142665F5@server-16.MorganSys.net>
From:	"Neal Morgan" <Neal@Morgan-Systems.com>
To:	<zmailer@nic.funet.fi>
X-Morgan-Systems-MailScanner-Information: Please contact the ISP for more information
X-MailScanner-ID: 105016720132903
X-Morgan-Systems-MailScanner: Found to be clean
X-Morgan-Systems-MailScanner-From: neal@morgan-systems.com
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

> On Monday, May 17, 2010 9:55 AM Neal Morgan wrote:
> 
> This is probably something I should already know.  Is there a way to 
> make zmailer re-order the queue for a particular channel/host when the

> top message is being rejected by the receiving end?  We continually
find 
> that aol will reject a message with a temporary error, then subsequent

> messages will queue up behind it, and the queue grows larger and
larger 
> until we take manual action to correct it.  Zmailer continues to want
to 
> deliver the messages in the original order, meaning the newer messages

> never get tried since the top message is in the way.  So, is it
possible 
> to make zmailer put the message with the temporary error at the bottom

> of the queue after some configurable number of retries?
> 
> We have been handling this manually, by deleting the offending top
message 
> from both the transport and queue directories.  Is there a
zmailer-approved 
> way to delete a single message for a channel/host?
> We've just been using "rm" for this, then forcing a resubmit on that 
> channel/host.

I am going to answer my own question for the sake of documentation.

The correct way to deal with this is to comment out the "ageorder" parm
in scheduler.conf.  This will cause the scheduler to process messages in
a random order rather than waiting for that problem message.


Matti - can you confirm these two gueses:

1) There is no way (via mailq or other utility) to forcibly reorder the
queue for a channel/host
2) There is a way to remove a single message from the queue for a
channel/host.  See the man page for "manual-expirer".  


Matti - one additional question on expirer/manual-expirer.  What is
expected in the "-m" message string parm?
	a) message ID as seen in mailq -v  for example:
<S459317Ab0ETUYK/20100520202420Z+2@SMTP.Morgan-Systems.com>
	b) spool ID as seen in syslog    for example:   S459319Ab0ETTSf
	c) inode/file name of the message    for example: 459324



--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Fri May 21 00:03:02 2010
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S77743Ab0ETVC7BNT-4 (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Fri, 21 May 2010 00:02:59 +0300
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77761Ab0ETVC6yQatQ
	(ORCPT <rfc822;zmailer-outgoing>); Fri, 21 May 2010 00:02:58 +0300
Received: from mail.dm.uba.ar ([157.92.22.1]:48963 "EHLO mail.dm.uba.ar"
	rhost-flags-OK-OK-OK-OK) by nic.funet.fi with ESMTP
	id S77743Ab0ETVC55XyDA (ORCPT <rfc822;zmailer@nic.funet.fi>);
	Fri, 21 May 2010 00:02:57 +0300
Received: from mybfyb.ffyb.uba.ar ([157.92.144.74]:1247 "EHLO [192.168.2.102]"
	smtp-auth: "rcoss" TLS-CIPHER: "DHE-RSA-AES256-SHA keybits 256/256
	version TLSv1/SSLv3" TLS-PEER-CN1: <none> rhost-flags-OK-OK-OK-FAIL)
	by mail.dm.uba.ar with SUBMITSA id S29680376Ab0ETVCr (ORCPT
	<rfc822;zmailer@nic.funet.fi>); Thu, 20 May 2010 18:02:47 -0300
X-Comment: RFC 2476 MSA function at mail.dm.uba.ar logged sender identity as: rcoss
Message-ID: <4BF5A36B.9010700@dm.uba.ar>
Date:	Thu, 20 May 2010 18:02:35 -0300
From:	Rodolfo Cossalter <rcoss@dm.uba.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-AR; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0
MIME-Version: 1.0
To:	Neal Morgan <Neal@Morgan-Systems.com>
CC:	zmailer@nic.funet.fi
Subject: Re: [ZMailer] Zmailer crashes
References: <20081031160305.GB9632@linux-mips.org> <7D1CC61717004141A57CA6CA1C8087EC38ED0B@server-16.MorganSys.net> <20090201135244.GA8440@paja.nic.funet.fi> <20090204150955.GA24046@linux-mips.org> <20091009144600.GA19375@linux-mips.org> <4BF586BA.3000401@dm.uba.ar> <6557A87A5B462247861990180A542B14266639@server-16.MorganSys.net>
In-Reply-To: <6557A87A5B462247861990180A542B14266639@server-16.MorganSys.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

El 20/05/2010 04:41 p.m., Neal Morgan escribió:
>> on Thursday, May 20, 2010 12:00 PM Ralf Baechle wrote:
>>
>> I'm also getting segfaults from router, a few of them every week.
>> It's a Debian Linux box:
>> Linux mail 2.6.31.5 #1 SMP Mon Oct 26 23:42:58 ART 2009 x86_64
> GNU/Linux Zmailer sources from Eugene's CVS.
>> I've turned on core dumps (ulimit -Sc 51200 in the shell that
> starts/restarts the router) but couldn't ever get a core file, however,
> if I>  signal the router process with kill -SIGSEGV pid I get a core
> file (useless).
>> So I decided to run gdb and attach to each router process (router -dkn
>> 2) and wait...
>> This is what I got when router finally segfaulted.
>> Can anybody help with this gdb trace?
>
> Rodolfo:
>
> Hopefully Matti will be able to provide some insight on your core dump.
>
> FWIW, my original issue with SMTPServer and segfaults went away
> somewhere between upgrading Debian/kernel (to 2.6.26) and getting latest
> ZMailer from CVS and rebuilding.  I am not sure which of those two fixed
> it, but one of them did.
>
> I do still get the router segfaults - like you.  However, this only
> seems to be happening on my two busier machines (which happen to both be
> x64).  My less busy (x86) machines are not experiencing segfaults.
>
> Most importantly, I see no evidence the segfaults are causing mail loss
> or delivery delays.  A new router process is created and things continue
> as normal.  (Don't get me wrong, it would be best not to get the
> segfaults...it just becomes less of a priority knowing mail is still
> being delivered).

Yes, the same happens here, the new router process picks up where the
segfaulted one was processing and no mail is lost.


>
> I'll look forward to suggestions from Matti.
>
>
> Thanks,
>
> Neal

Rodolfo

--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Fri May 21 14:17:32 2010
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S77945Ab0EULR1ILV5Y (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Fri, 21 May 2010 14:17:27 +0300
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77950Ab0EULR04YeC4
	(ORCPT <rfc822;zmailer-outgoing>); Fri, 21 May 2010 14:17:26 +0300
Received: from h5.dl5rb.org.uk ([81.2.74.5]:37969 "EHLO h5.dl5rb.org.uk"
	rhost-flags-OK-OK-OK-OK) by nic.funet.fi with ESMTP
	id S77945Ab0EULR0FPxls (ORCPT <rfc822;zmailer@nic.funet.fi>);
	Fri, 21 May 2010 14:17:26 +0300
Received: from h5.dl5rb.org.uk (localhost.localdomain [127.0.0.1])
	by h5.dl5rb.org.uk (8.14.3/8.14.3) with ESMTP id o4LBGxki010004;
	Fri, 21 May 2010 12:17:00 +0100
Received: (from ralf@localhost)
	by h5.dl5rb.org.uk (8.14.3/8.14.3/Submit) id o4LBGvpL010000;
	Fri, 21 May 2010 12:16:57 +0100
Date:	Fri, 21 May 2010 12:16:57 +0100
From:	Ralf Baechle <ralf@linux-mips.org>
To:	Rodolfo Cossalter <rcoss@dm.uba.ar>
Cc:	Neal Morgan <Neal@Morgan-Systems.com>, zmailer@nic.funet.fi
Subject: Re: [ZMailer] Zmailer crashes
Message-ID: <20100521111657.GA10305@linux-mips.org>
References: <20081031160305.GB9632@linux-mips.org>
 <7D1CC61717004141A57CA6CA1C8087EC38ED0B@server-16.MorganSys.net>
 <20090201135244.GA8440@paja.nic.funet.fi>
 <20090204150955.GA24046@linux-mips.org>
 <20091009144600.GA19375@linux-mips.org>
 <4BF586BA.3000401@dm.uba.ar>
 <6557A87A5B462247861990180A542B14266639@server-16.MorganSys.net>
 <4BF5A36B.9010700@dm.uba.ar>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4BF5A36B.9010700@dm.uba.ar>
User-Agent: Mutt/1.5.20 (2009-08-17)
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

On Thu, May 20, 2010 at 06:02:35PM -0300, Rodolfo Cossalter wrote:

> From: Rodolfo Cossalter <rcoss@dm.uba.ar>
> To: Neal Morgan <Neal@Morgan-Systems.com>
> CC: zmailer@nic.funet.fi

Neal, it would be useful if you had not removed me from cc.  This list
receives so little email that without cc I might not notice a posting
for ages.

> >Hopefully Matti will be able to provide some insight on your core dump.
> >
> >FWIW, my original issue with SMTPServer and segfaults went away
> >somewhere between upgrading Debian/kernel (to 2.6.26) and getting latest
> >ZMailer from CVS and rebuilding.  I am not sure which of those two fixed
> >it, but one of them did.
> >
> >I do still get the router segfaults - like you.  However, this only
> >seems to be happening on my two busier machines (which happen to both be
> >x64).  My less busy (x86) machines are not experiencing segfaults.
> >
> >Most importantly, I see no evidence the segfaults are causing mail loss
> >or delivery delays.  A new router process is created and things continue
> >as normal.  (Don't get me wrong, it would be best not to get the
> >segfaults...it just becomes less of a priority knowing mail is still
> >being delivered).
> 
> Yes, the same happens here, the new router process picks up where the
> segfaulted one was processing and no mail is lost.

For me the issue didn't cause any data loss and it eventually went away
when I upgraded the system to a newer Linux distribution.  I'm now
Zmailer on Fedora 12 where I've encountered a different issue, see
the "Zmailer breaks on Fedora 12" thread starting on November 23.

  Ralf
--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Mon Jul 26 21:31:06 2010
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S77030Ab0GZSbGAYpTI (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Mon, 26 Jul 2010 21:31:06 +0300
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77048Ab0GZSbFsSwQY
	(ORCPT <rfc822;zmailer-outgoing>); Mon, 26 Jul 2010 21:31:05 +0300
Received: from h5.dl5rb.org.uk ([81.2.74.5]:45339 "EHLO h5.dl5rb.org.uk"
	rhost-flags-OK-OK-OK-OK) by nic.funet.fi with ESMTP
	id S77030Ab0GZSbFQ0J1Y (ORCPT <rfc822;zmailer@nic.funet.fi>);
	Mon, 26 Jul 2010 21:31:05 +0300
Received: from h5.dl5rb.org.uk (localhost.localdomain [127.0.0.1])
	by h5.dl5rb.org.uk (8.14.4/8.14.3) with ESMTP id o6QIV2TR021597
	for <zmailer@nic.funet.fi>; Mon, 26 Jul 2010 19:31:03 +0100
Received: (from ralf@localhost)
	by h5.dl5rb.org.uk (8.14.4/8.14.4/Submit) id o6QIV2jo021595
	for zmailer@nic.funet.fi; Mon, 26 Jul 2010 19:31:02 +0100
Date:	Mon, 26 Jul 2010 19:31:02 +0100
From:	Ralf Baechle <ralf@linux-mips.org>
To:	zmailer@nic.funet.fi
Subject: [ZMailer] SELinux policy for Zmailer
Message-ID: <20100726183102.GA17166@linux-mips.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.20 (2009-08-17)
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

I wonder if anybody has already written a SELinux policy for Zmailer?

  Ralf
--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Mon Aug  2 14:05:07 2010
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S77358Ab0HBLFE3Pgss (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Mon, 2 Aug 2010 14:05:04 +0300
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77346Ab0HBLFEXMYAA
	(ORCPT <rfc822;zmailer-outgoing>); Mon, 2 Aug 2010 14:05:04 +0300
Received: (mea@paja.nic.funet.fi) by nic.funet.fi id S76996Ab0HBLFD400AY
	(ORCPT <rfc822;zmailer@nic.funet.fi>);
	Mon, 2 Aug 2010 14:05:03 +0300
Date:	Mon, 2 Aug 2010 14:05:03 +0300
From:	Matti Aarnio <mea@nic.funet.fi>
To:	Ralf Baechle <ralf@linux-mips.org>
Cc:	zmailer@nic.funet.fi
Subject: Re: [ZMailer] SELinux policy for Zmailer
Message-ID: <20100802110503.GA10304@paja.nic.funet.fi>
References: <20100726183102.GA17166@linux-mips.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100726183102.GA17166@linux-mips.org>
User-Agent: Mutt/1.4.2.1i
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

On Mon, Jul 26, 2010 at 07:31:02PM +0100, Ralf Baechle wrote:
> I wonder if anybody has already written a SELinux policy for Zmailer?

No.  While the Linux distributions I use have it, I am running
them without policy.

Learning to use SELinux in enforced mode has never gotten enough
priority in my work or hobby so far...

>   Ralf
-- 
/Matti Aarnio	<mea@nic.funet.fi>
--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Mon Aug  2 16:28:12 2010
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S77342Ab0HBN2M1UY0Q (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Mon, 2 Aug 2010 16:28:12 +0300
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77353Ab0HBN2MWEdjI
	(ORCPT <rfc822;zmailer-outgoing>); Mon, 2 Aug 2010 16:28:12 +0300
Received: from h5.dl5rb.org.uk ([81.2.74.5]:50209 "EHLO h5.dl5rb.org.uk"
	rhost-flags-OK-OK-OK-OK) by nic.funet.fi with ESMTP
	id S76996Ab0HBN2Llq19Y (ORCPT <rfc822;zmailer@nic.funet.fi>);
	Mon, 2 Aug 2010 16:28:11 +0300
Received: from h5.dl5rb.org.uk (localhost.localdomain [127.0.0.1])
	by h5.dl5rb.org.uk (8.14.4/8.14.3) with ESMTP id o72DS9OK016709;
	Mon, 2 Aug 2010 14:28:09 +0100
Received: (from ralf@localhost)
	by h5.dl5rb.org.uk (8.14.4/8.14.4/Submit) id o72DS9Rq016707;
	Mon, 2 Aug 2010 14:28:09 +0100
Date:	Mon, 2 Aug 2010 14:28:08 +0100
From:	Ralf Baechle <ralf@linux-mips.org>
To:	Matti Aarnio <mea@nic.funet.fi>
Cc:	zmailer@nic.funet.fi
Subject: Re: [ZMailer] SELinux policy for Zmailer
Message-ID: <20100802132808.GB3244@linux-mips.org>
References: <20100726183102.GA17166@linux-mips.org>
 <20100802110503.GA10304@paja.nic.funet.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100802110503.GA10304@paja.nic.funet.fi>
User-Agent: Mutt/1.5.20 (2009-12-10)
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

On Mon, Aug 02, 2010 at 02:05:03PM +0300, Matti Aarnio wrote:

> On Mon, Jul 26, 2010 at 07:31:02PM +0100, Ralf Baechle wrote:
> > I wonder if anybody has already written a SELinux policy for Zmailer?
> 
> No.  While the Linux distributions I use have it, I am running
> them without policy.
> 
> Learning to use SELinux in enforced mode has never gotten enough
> priority in my work or hobby so far...

On my various servers I'm running a fair pile of rather dated software of
at best uncertain security status and some software that fairly regularly
has security issues - I just say PHP and the noise of people trying to
kick the doors has turned into the sound of an infinite number of monkeys
driving bulldozers through the front yard ...

I've got a mostly working policy now.  It's still rather ugly and
occasionally I see either zmailer or one of the zmailer users doing a
somewhat more rare operation that need policy tuning.

To simplify the policy I'm wondering if some of zmailers files should be
moved from the current default location to other directories, in particular
the .pid files to /var/run/zmailer/.  Maybe also the sockets and
.zmailer.SNMP.block.

On occasion SELinux also finds odd application behaviour so unexpectedly
it also turned into a bit of a crystall ball into odd application behaviour.

  Ralf
--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

From zmailer-owner@nic.funet.fi Mon Feb  7 14:20:35 2011
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi via listexpand
	id S76199Ab1BGMUe7b8Ac (ORCPT <rfc822;zmailer-log@nic.funet.fi>);
	Mon, 7 Feb 2011 14:20:34 +0200
Received: (majordom@paja.nic.funet.fi) by nic.funet.fi id S77024Ab1BGMUex5LEc
	(ORCPT <rfc822;zmailer-outgoing>); Mon, 7 Feb 2011 14:20:34 +0200
Received: from mail.Morgan-Systems.com ([204.16.172.8]:40681 "EHLO
	mail.morgan-systems.com" rhost-flags-OK-OK-OK-OK) by nic.funet.fi
	with ESMTP id S76199Ab1BGMUeLXFNA (ORCPT
	<rfc822;zmailer@nic.funet.fi>); Mon, 7 Feb 2011 14:20:34 +0200
Received: from Server-16.MorganSys.net ([10.30.1.16]:31514 "HELO
	Mail.Morgan-Systems.com" smtp-auth: <none> TLS-CIPHER: <none>
	TLS-PEER-CN1: <none> rhost-flags-OK-OK-OK-FAIL)
	by Mail.Morgan-Systems.com with SMTP id S1475120Ab1BGMUb convert rfc822-to-8bit
	(ORCPT <rfc822;zmailer@nic.funet.fi>);
	Mon, 7 Feb 2011 04:20:31 -0800
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8BIT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: [ZMailer] cfgread.c - Debian 6/Squeeze
Date:	Mon, 7 Feb 2011 04:20:30 -0800
Message-ID: <CFC179D35F8E224C9A541F8DF2CD9DB3030D8B@server-16.MorganSys.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: cfgread.c - Debian 6/Squeeze
Thread-Index: AcvGwWlO7pTVDDNYQsqeaFeQe6FQjA==
From:	"Neal Morgan" <Neal@Morgan-Systems.com>
To:	<zmailer@nic.funet.fi>
Sender:	zmailer-owner@nic.funet.fi
Precedence: bulk
X-Mailing-List:	zmailer@nic.funet.fi
List-ID: <zmailer.nic.funet.fi>
Return-Path: <zmailer-owner@nic.funet.fi>
X-Envelope-To: <"/pub/unix/mail/zmailer/listlog/zmailer"> (uid 0)
X-Orcpt: rfc822;zmailer-log@nic.funet.fi
Original-Recipient: rfc822;zmailer-log@nic.funet.fi

Greetings:

After installing the newly released Debian 6 upgrade, and rebuilding
Zmailer from source, I found smtpserver failing with a message about
being unable to read the policy database:

"smtpserver policy database problem, code: 2"

I spent a good deal of time troubleshooting, and found the policy
database value used in policytest.c was wrong.  I was seeing evidence of
string replacements not being made entirely, for example, a debug
statement inserted where the policy db was opened showed this:

000- btree->open('$MLVAR/db/smsmtp-policy.db',BTREE, RDONLY) ret=2

After more digging, I found that the replacement made for function
dollarexpand in cfgread.c for the variable dbtype was the culprit.
Changing the memcpy under the "Copy down" comment to a strcpy seems to
fix the problem:


/* Copy down */
//strcpy((char*)(s0+len), str);
memcpy(s0+len, str, strlen((char*)str));


It has been a long time since I did any serious C coding: I am quite
rusty at pointers, memcpy, strcpy, etc.  This change appears to have
fixed the problem, but I would appreciate some extra eyes on this code
to confirm this was the correct fix.  Matti/Eugene/Others, can you have
a look at this and let me know if this is the right way to go?


Thanks,

Neal Morgan
--
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi

