Hi,
Aaron Stone wrote:
I don't think we can let the MTA do the forwards because we don't have a way
of communicating "forward this message to so and so..." to the MTA. We
definitely can't let the MTA be fully in charge because we want the forward
configuration to be in the database and not in some text file or something.
I completely agree with that. The aliases table should be in the database.
I'm sure that the various database user map patches to Postgres could help
handle this, but it puts a pretty stringent requirement onto the MTA.
I'm going to keep the forwards in there for now and remove the bounces. If we
can figure out a good way to pass forwards back to the MTA let's go for it!
I guess it would be better to keep things in DBMail 2.0 as they are
(possibly correcting bounce behaviour), and do these major changes in
the next release.
Ilja
Aaron
Ilja Booij <[EMAIL PROTECTED]> said:
Hi,
Seems like a good idea to me. Let the MTA do what the MTA does best, and
let DBMail store the emails. Along the same lines: Can't we use the MTA
sending forwards and domain forwards in the same manner?
Ilja
Aaron Stone wrote:
Based on my reading, I think that DBMail should not generate bounces at all.
Rather, appropriate temporary-failure and permanent-failure return codes
should come from dbmail-smtp and DSN codes from dbmail-lmtpd, along with
additional descriptive text in both cases, and the MTA will do the rest.
If this is the case, I can remove the bounce call from pipe.c right now; I'm
working on refining the delivery chain to produce appropriate error codes for
various failure conditions. Making sure to emit bounce codes for situations
which would have called the bounce() function won't be too hard.
Aaron
Ilja Booij <[EMAIL PROTECTED]> said:
dbmail currently uses the Return-Path header. If it cannot find such a
header, it uses the From header.
What would you suggest we do: search for the Sender and/or Errors-To
header and use that as a return address? Does this always work?
thanks,
Ilja
Christian G. Warden wrote:
I'm pretty sure this has been discussed before, but dbmail doesn't
seem to generate bounces correctly. I don't generate bounces within
dbmail so I've never noticed this.
Here is a bounce I got from a dbmail user in response to a message sent
to the dbmail list.
It does a few things wrong. The envelope sender is not <> as it should
be, and the message is sent to the address in the From header rather
than the envelope sender.
How does dbmail determine the sender of a message that a bounce must be
sent to? It doesn't look like the MTA of the user in question adds a
header with the envelope sender, but Errors-To and Sender would be
better choices than From.
xn
----- Forwarded message from [EMAIL PROTECTED] -----
Date: Tue, 3 Feb 2004 23:32:23 +0200 (EET)
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: DBMAIL: delivery failure
This is the DBMAIL-SMTP program.
I'm sorry to inform you that your message, addressed to naso,
could not be delivered due to the following error.
*** Mailbox of user naso is FULL ***
If you think this message is incorrect please contact [EMAIL PROTECTED]
Header of your message follows...
--- header of your message ---
Received: from twister.fastxs.net (unknown [213.214.98.20])
by mail.netel.bg (Postfix) with ESMTP
id C69575C004FF; Tue, 3 Feb 2004 23:32:16 +0200 (EET)
Received: from twister.fastxs.net (localhost [127.0.0.1])
by twister.fastxs.net (Postfix) with ESMTP
id 2E7E37BE71; Tue, 3 Feb 2004 22:32:02 +0100 (CET)
Received: from cayenne.xerus.org (adsl-66-51-218-170.dslextreme.com
[66.51.218.170])
by twister.fastxs.net (Postfix) with ESMTP id C58A87B46F
for <dbmail@dbmail.org>; Tue, 3 Feb 2004 22:30:59 +0100 (CET)
Received: from safron ([192.168.1.5] helo=safron.xerus.org)
by cayenne.xerus.org with esmtp (Exim 4.30 #1 (Debian))
id 1Ao886-0007C2-3t
for <dbmail@dbmail.org>; Tue, 03 Feb 2004 13:30:46 -0800
Received: from cwarden by safron.xerus.org with local (Exim 3.36 #1 (Debian))
id 1Ao88J-00071c-00
for <dbmail@dbmail.org>; Tue, 03 Feb 2004 13:30:59 -0800
From: "Christian G. Warden" <[EMAIL PROTECTED]>
To: dbmail@dbmail.org
Subject: Re: [Dbmail] dbmail-smtp and imap folders
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.4i
Sender: [EMAIL PROTECTED]
Errors-To: [EMAIL PROTECTED]
X-BeenThere: dbmail@dbmail.org
X-Mailman-Version: 2.0.10
Precedence: bulk
Reply-To: dbmail@dbmail.org
List-Help: <mailto:[EMAIL PROTECTED]>
List-Post: <mailto:dbmail@dbmail.org>
List-Subscribe: <https://mailman.fastxs.nl/mailman/listinfo/dbmail>,
<mailto:[EMAIL PROTECTED]>
List-Id: <dbmail.dbmail.org>
List-Unsubscribe: <https://mailman.fastxs.nl/mailman/listinfo/dbmail>,
<mailto:[EMAIL PROTECTED]>
List-Archive: <https://mailman.fastxs.nl/pipermail/dbmail/>
Date: Tue, 3 Feb 2004 13:30:59 -0800
--- end of header ---
----- End forwarded message -----
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
--
IC&S
Stadhouderslaan 57
3583 JD Utrecht
PGP-key:
http://www.ic-s.nl/keys/ilja.txt
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
--
IC&S
Stadhouderslaan 57
3583 JD Utrecht
PGP-key:
http://www.ic-s.nl/keys/ilja.txt
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
--
IC&S
Stadhouderslaan 57
3583 JD Utrecht
PGP-key:
http://www.ic-s.nl/keys/ilja.txt
