Hi Fredrik,

I was wrong, 75 is returned. It is defined in debug.c:

debug.c:#define EXIT_CODE 75

So if you need to change it you can change the EXIT_CODE value and recompile.

Best regards,

Eelco

fredrik heeft op donderdag, 1 aug 2002 om 03:12 (Europe/Amsterdam) het volgende geschreven:

Hi!

If using Qmail, 64 would be considered a hard error resulting in a bouce of the
message.
Could you add something in the config telling dbmail if it is beeing triggered by
postfix or qmail?

I'm submitting the qmail error codes below.

0 delivery successful. Continue with next command. (Normal)
99 delivery successful. Don't sent to next command.
100 har error permanent failiure. (Like user does not exist).
111 soft error. Put back in queue and retry later.


          Currently 64, 65, 70, 76, 77, 78, and 112 are considered
          hard errors, and all other codes are considered soft errors,
          but command should avoid relying on this.

More info on http://www.qmail.org/man/man8/qmail-command.html


Fredrik

[EMAIL PROTECTED] wrote:

Hi Michah,

This is true, dbmail will send a signal (64 i believe) to postfix to let
it know that the message should be put back into the queue instead of
being dropped.

The weird thing is that the message is eventually delivered. If it
happends again, please send me a copy of the message.

Thanks!

Eelco

On Tue, 30 Jul 2002, Micah Stevens wrote:

Date: Tue, 30 Jul 2002 14:04:34 -0700
From: Micah Stevens <[EMAIL PROTECTED]>
Reply-To: dbmail@dbmail.org
To: dbmail@dbmail.org
Subject: Re: [Dbmail] Death by signal 11

Hi Eelco,

Thanks for your interest, if you recall reading a previous post I made to
the list, I was having a problem with messages being redelivered many
times. As I'm looking at this report (I posted the whole thing below for your reference) It appears that this is probably related. You'll notice that there are 398 deferrals, and 398 signal 11 errors. If Postfix sees the signal 11 error, perhaps will it keep the message in the queue and try and deliver it later? I was receiving the mail in the database, so perhaps after inserting the data dbmail-smtp it was dying. This problem that I had was cleared up by updating from the CVS version I had to the CVS snapshot
as of the 30th.

I'd love to forward you a copy of one of the deferred mails, but I erased
them all with the dbmail-maintenance program this morning.

-Micah




To: [EMAIL PROTECTED]
Subject: raincross-tech.com Daily Mail Report for Tuesday, 30 July 2002
Date: Tue, 30 Jul 2002 04:02:08 -0700 (PDT)
From: [EMAIL PROTECTED] (root)


Grand Totals
------------
messages
12 received
26 delivered
0 forwarded
16 deferred (398 deferrals)
0 bounced
0 rejected
38890 bytes received
139607 bytes delivered
5 senders
4 sending hosts/domains
7 recipients
3 recipient hosts/domains

message deferral detail
-----------------------
pipe
398 Command died with signal 11: "/usr/local/sbin/dbmail-smtp"
Warnings
--------
cleanup
10 database /etc/postfix/virtual.db is older than source file /etc...
postfix-script
1 /var/spool/postfix/etc/passwd and /etc/passwd differ
smtpd
7 database /etc/postfix/virtual.db is older than source file /etc...
Fatal Errors: none
Panics: none
Per-Day Traffic Summary
date received delivered deferred bounced rejected
--------------------------------------------------------------------
2002-07-28 0 0 256
2002-07-29 10 24 142
2002-07-30 2 2
Per-Hour Traffic Daily Average
time received delivered deferred bounced rejected
--------------------------------------------------------------------
00:00-01:00 0 0 3 0 0
01:00-02:00 0 0 5 0 0
02:00-03:00 0 0 5 0 0
03:00-04:00 0 0 2 0 0
04:00-05:00 1 0 11 0 0
05:00-06:00 0 0 10 0 0
06:00-07:00 0 0 10 0 0
07:00-08:00 0 0 7 0 0
08:00-09:00 0 0 10 0 0
09:00-10:00 0 0 9 0 0
10:00-11:00 0 4 5 0 0
11:00-12:00 1 2 5 0 0
12:00-13:00 0 0 5 0 0
13:00-14:00 0 0 5 0 0
14:00-15:00 1 1 3 0 0
15:00-16:00 0 0 5 0 0
16:00-17:00 0 0 5 0 0
17:00-18:00 0 0 1 0 0
18:00-19:00 0 0 5 0 0
19:00-20:00 0 0 5 0 0
20:00-21:00 1 1 5 0 0
21:00-22:00 0 0 5 0 0
22:00-23:00 0 0 5 0 0
23:00-24:00 0 0 5 0 0
Host/Domain Summary: Message Delivery (top 10)
sent cnt bytes defers avg dly max dly host/domain
-------- ------- ------- ------- ------- -----------
18 132103 290 31.7 h 67.5 h raincross-tech.com
7 6518 108 38.5 h 67.7 h 2dogspetsupply.com
1 986 0 1.0 s 1.0 s 9250x.com
Host/Domain Summary: Messages Received (top 10)
msg cnt bytes host/domain
-------- ------- -----------
5 27154 raincross-tech.com
5 4275 9250x.com
1 5789 oscommerce.com
1 1672 charge.he.net
top 10 Senders by message count
-------------------------------
5 [EMAIL PROTECTED]
4 [EMAIL PROTECTED]
1 [EMAIL PROTECTED]
1 [EMAIL PROTECTED]
1 [EMAIL PROTECTED]
top 10 Recipients by message count
----------------------------------
6 [EMAIL PROTECTED]
6 [EMAIL PROTECTED]
5 [EMAIL PROTECTED]
4 [EMAIL PROTECTED]
3 [EMAIL PROTECTED]
1 [EMAIL PROTECTED]
1 [EMAIL PROTECTED]
top 10 Senders by message size
------------------------------
26168 [EMAIL PROTECTED]
5789 [EMAIL PROTECTED]
4275 [EMAIL PROTECTED]
1672 [EMAIL PROTECTED]
986 [EMAIL PROTECTED]
top 10 Recipients by message size
---------------------------------
62716 [EMAIL PROTECTED]
56507 [EMAIL PROTECTED]
10026 [EMAIL PROTECTED]
5655 [EMAIL PROTECTED]
2854 [EMAIL PROTECTED]
986 [EMAIL PROTECTED]
863 [EMAIL PROTECTED]


At 09:46 PM 7/30/2002 +0200, you wrote:
Hi Michah,

I'm very curious about your segfault. Could you send me the e-mail message on which dbmail-smtp dies? (postcat on the queue file will do the trick)

Thanks,

Eelco


On 30-07-2002 20:02, "Micah Stevens" <[EMAIL PROTECTED]> wrote:

Hi,

I'm using:

Postfix 1.1.10 with the mysql patch.
MySQL 4.0.2-2
DBMail - I'm not sure how to find out this version, I got it from CVS on
7-28-02. I assume that would be after the bugfix you spoke of?

This version was an upgrade that solved some other problems I was having
with pop3d crashing.

-Micah




At 06:31 PM 7/30/2002 +0200, you wrote:
Hi Micah,

What version are you using?
There was a 'bug' in previous version which was caused by \0 in a the pipe stream from postfix. The dbmail-smtp program assumed that this could
not be
happening. This should however be fixed in the newest release.

What dbase are you using as backend?

Best regards,

Eelco


_______________________________________________
Dbmail mailing list
Dbmail@dbmail.org
https://mailman.fastxs.nl/mailman/listinfo/dbmail


__________________________
E.J.A. van Beek
ICT Manager
IC&S
T: +31 30 2322878
F: +31 30 2322305

PGP-key:
www.ic-s.nl/keys/eelco.txt

_______________________________________________
Dbmail mailing list
Dbmail@dbmail.org
https://mailman.fastxs.nl/mailman/listinfo/dbmail

_______________________________________________
Dbmail mailing list
Dbmail@dbmail.org
https://mailman.fastxs.nl/mailman/listinfo/dbmail

Reply via email to