Am Montag 01 Februar 2010 19:01:02 schrieb Timo Sirainen:
It's beginning to sound like I should add lmtp_headers setting where
you could do all kinds of interesting things like:
That'd be great!
+1
--
Mit freundlichen Grüßen / Best Regards
Dominik
signature.asc
Description: This is a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 1 Feb 2010, Timo Sirainen wrote:
It's beginning to sound like I should add lmtp_headers setting where
you could do all kinds of interesting things like:
lmtp_headers = \
Return-Path: %f\n \
Envelope-To: %t\n \
X-Envelope-To: %t\n \
On 1.2.2010, at 8.38, Andreas Schulze wrote:
In the first case there are *no* Return-Path and Delivered-To Headers.
In the (most common) second case the *are* present.
Why these Headers are not included while using the LMTP-Server?
I guess I could add Return-Path header. I could also add
Timo Sirainen t...@iki.fi writes:
In the first case there are *no* Return-Path and Delivered-To Headers.
In the (most common) second case the *are* present.
Why these Headers are not included while using the LMTP-Server?
I agree about the Return-Path missing, but the Delivered-To is
specific
Timo Sirainen t...@iki.fi wrote:
On 1.2.2010, at 8.38, Andreas Schulze wrote:
In the first case there are *no* Return-Path and Delivered-To Headers.
In the (most common) second case the *are* present.
Why these Headers are not included while using the LMTP-Server?
I guess I could add
On 02/01/2010 10:32 AM Timo Sirainen wrote:
I guess I could add Return-Path header. I could also add Delivered-To as long
as there is only a single recipient, but adding it for multiple recipients
would make everything much more difficult than I'd like.
I was wondering about Delivered-To
On Mon, 2010-02-01 at 17:24 +0100, Pascal Volk wrote:
On 02/01/2010 10:32 AM Timo Sirainen wrote:
I guess I could add Return-Path header. I could also add Delivered-To as
long as there is only a single recipient, but adding it for multiple
recipients would make everything much more
On 2010-02-01 11:32 AM, Timo Sirainen t...@iki.fi wrote:
On Mon, 2010-02-01 at 17:24 +0100, Pascal Volk wrote:
On 02/01/2010 10:32 AM Timo Sirainen wrote:
I guess I could add Return-Path header. I could also add Delivered-To as
long as there is only a single recipient, but adding it for
On 02/01/2010 05:37 PM Charles Marcus wrote:
On 2010-02-01 11:32 AM, Timo Sirainen t...@iki.fi wrote:
On Mon, 2010-02-01 at 17:24 +0100, Pascal Volk wrote:
What about a X-Original-To header?
Is that any different from Delivered-To?
It's a X-$WHATEVER-header.
As mentioned by Nicolas: Postfix
On 1 February 2010 11:32, Timo Sirainen t...@iki.fi wrote:
On 1.2.2010, at 8.38, Andreas Schulze wrote:
In the first case there are *no* Return-Path and Delivered-To Headers.
In the (most common) second case the *are* present.
Why these Headers are not included while using the LMTP-Server?
On Mon, 2010-02-01 at 19:05 +0200, Warren Baker wrote:
There is also Exim's Envelope-To: header which is sometimes useful for
a catchall maildrop scenario. Fetchmail, by default, also makes use of
X-Envelope-To:. If i remember right sendmail can be configured to add
X-Envelope-To:.
Which,
On Mon, 2010-02-01 at 20:01 +0200, Timo Sirainen wrote:
It's beginning to sound like I should add lmtp_headers setting where
you could do all kinds of interesting things like:
lmtp_headers = \
Return-Path: %f\n \
Envelope-To: %t\n \
X-Envelope-To: %t\n \
X-Original-To: %t\n \
Noel Butler wrote:
On Mon, 2010-02-01 at 20:01 +0200, Timo Sirainen wrote:
It's beginning to sound like I should add lmtp_headers setting where
you could do all kinds of interesting things like:
lmtp_headers = \
Return-Path: %f\n \
Envelope-To: %t\n \
X-Envelope-To: %t\n \
Hello,
I just installed dovecot2-beta2 and configured the lmtp-server + postfix (no
virtual users)
postfix:
mail_version = 2.7-20100117
mailbox_transport = lmtp:unix:lmtp-server
lmtp_assume_final = yes
dovecot:
service lmtp {
executable = lmtp
protocol = lmtp
unix_listener
14 matches
Mail list logo
