Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: DBMail: users

dbmail / forwarding / spf / envelope

 

 

DBMail users RSS feed   Index | Next | Previous | View Threaded


h.reindl at thelounge

Jan 9, 2011, 7:33 PM

Post #1 of 8 (620 views)
Permalink
dbmail / forwarding / spf / envelope

Does dbmail anything like gmail by forwarding messages
i have not seen - seems to be straight forwarding

Below afaik a perfect sample from gmail

* Sender is "h.reindl [at] thelounge"
* Rcpt: "reindl.harald [at] gmail"
* My gmail-Account always forwards to my office-address

please take a look at the envelope abd the spf-check from our
barracuda-spamfirewall, without making this changes the
messages would be blocked by strict spf because
it shows my sender-address and is coming from the google-server
_______________

Received: from barracuda.thelounge.net (barracuda.thelounge.net [10.0.0.20]) (using TLSv1
with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested)
by mail.thelounge.net (Postfix) with ESMTPS id 4A344A3
for <h.reindl [at] thelounge>; Mon, 10 Jan 2011 04:21:11 +0100 (CET)
X-ASG-Debug-ID: 1294629666-03bcd9407b51fc70001-NZZS9d
Received: from mail-qw0-f46.google.com (mail-qw0-f46.google.com [209.85.216.46])
by barracuda.thelounge.net with ESMTP id DBsKQViB0BfFJKRl
for <h.reindl [at] thelounge>; Mon, 10 Jan 2011 04:21:07 +0100 (CET)
X-Barracuda-Envelope-From: reindl.harald+caf_=h.reindl=thelounge.net [at] gmail
X-Barracuda-Apparent-Source-IP: 209.85.216.46
Received-SPF: pass (barracuda.thelounge.net: domain of gmail.com designates
209.85.216.46 as permitted sender) client-ip=209.85.216.46;
envelope-from=reindl.harald+caf_=h.reindl=thelounge.net [at] gmail;
Received: by qwa26 with SMTP id 26so19352331qwa.19
for <h.reindl [at] thelounge>; Sun, 09 Jan 2011 19:21:06 -0800 (PST)
Received: by 10.229.189.14 with SMTP
id dc14mr24604116qcb.58.1294629666121; Sun, 09 Jan 2011 19:21:06 -0800 (PST)
X-Forwarded-To: h.reindl [at] thelounge
X-Forwarded-For: reindl.harald [at] gmail h.reindl [at] thelounge
_______________

yes i know i'm on holiday and must be total crazy plaing with mysql, dbmail
and reading docs the whole time :-)

regards
harry

--

Mit besten Grüßen, Reindl Harald
the lounge interactive design GmbH
A-1060 Vienna, Hofmühlgasse 17
CTO / software-development / cms-solutions
p: +43 (1) 595 3999 33, m: +43 (676) 40 221 40
icq: 154546673, http://www.thelounge.net/
Attachments: signature.asc (0.25 KB)


tabris at tabris

Jan 9, 2011, 7:37 PM

Post #2 of 8 (607 views)
Permalink
Re: dbmail / forwarding / spf / envelope [In reply to]

On 1/9/11 7:33 PM, Reindl Harald wrote:
> Does dbmail anything like gmail by forwarding messages
> i have not seen - seems to be straight forwarding
>

Strange question, DBmail is not an MTA.

What you ask seems to be a responsibility for your MTA (postfix, exim,
sendmail, etc).

> Below afaik a perfect sample from gmail
>
> * Sender is "h.reindl [at] thelounge"
> * Rcpt: "reindl.harald [at] gmail"
> * My gmail-Account always forwards to my office-address
>
> please take a look at the envelope abd the spf-check from our
> barracuda-spamfirewall, without making this changes the
> messages would be blocked by strict spf because
> it shows my sender-address and is coming from the google-server
> _______________
>
> Received: from barracuda.thelounge.net (barracuda.thelounge.net [10.0.0.20]) (using TLSv1
> with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested)
> by mail.thelounge.net (Postfix) with ESMTPS id 4A344A3
> for <h.reindl [at] thelounge>; Mon, 10 Jan 2011 04:21:11 +0100 (CET)
> X-ASG-Debug-ID: 1294629666-03bcd9407b51fc70001-NZZS9d
> Received: from mail-qw0-f46.google.com (mail-qw0-f46.google.com [209.85.216.46])
> by barracuda.thelounge.net with ESMTP id DBsKQViB0BfFJKRl
> for <h.reindl [at] thelounge>; Mon, 10 Jan 2011 04:21:07 +0100 (CET)
> X-Barracuda-Envelope-From: reindl.harald+caf_=h.reindl=thelounge.net [at] gmail
> X-Barracuda-Apparent-Source-IP: 209.85.216.46
> Received-SPF: pass (barracuda.thelounge.net: domain of gmail.com designates
> 209.85.216.46 as permitted sender) client-ip=209.85.216.46;
> envelope-from=reindl.harald+caf_=h.reindl=thelounge.net [at] gmail;
> Received: by qwa26 with SMTP id 26so19352331qwa.19
> for <h.reindl [at] thelounge>; Sun, 09 Jan 2011 19:21:06 -0800 (PST)
> Received: by 10.229.189.14 with SMTP
> id dc14mr24604116qcb.58.1294629666121; Sun, 09 Jan 2011 19:21:06 -0800 (PST)
> X-Forwarded-To: h.reindl [at] thelounge
> X-Forwarded-For: reindl.harald [at] gmail h.reindl [at] thelounge
> _______________
>
> yes i know i'm on holiday and must be total crazy plaing with mysql, dbmail
> and reading docs the whole time :-)
>
> regards
> harry
>
>
>
> _______________________________________________
> DBmail mailing list
> DBmail [at] dbmail
> http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
Attachments: signature.asc (0.25 KB)


h.reindl at thelounge

Jan 9, 2011, 7:43 PM

Post #3 of 8 (594 views)
Permalink
Re: dbmail / forwarding / spf / envelope [In reply to]

Am 10.01.2011 04:37, schrieb tabris:

> On 1/9/11 7:33 PM, Reindl Harald wrote:
>> Does dbmail anything like gmail by forwarding messages
>> i have not seen - seems to be straight forwarding
>
> Strange question, DBmail is not an MTA.
> What you ask seems to be a responsibility for your MTA (postfix, exim, sendmail, etc).

Hm not really

* MTA receives a message and delivers over lmtp
* dbmail looks in alias-table and see the forward
* dbmail generates a new message and gives it to the mta
* the mta does not and should not touch this message

It happens the same as with my autoreply below (to you *g*)

* psotfix/pickup will fetch the message from dbmail
* uid=493 is dbmail on fedora/redhat

Jan 10 04:37:59 mail postfix/pickup[15589]: 0C675AD: uid=493 from=<h.reindl [at] thelounge>
Jan 10 04:37:59 mail postfix/cleanup[15595]: 0C675AD: message-id=<20110110033759.0C675AD [at] mail>
Jan 10 04:37:59 mail postfix/lmtp[15596]: E560A97: to=<h.reindl [at] thelounge>, relay=127.0.0.1[127.0.0.1]:24,
delay=0.13, delays=0.02/0.01/0/0.1, dsn=2.0.0, status=sent (215 Recipient <h.reindl [at] thelounge> OK)
Jan 10 04:37:59 mail postfix/qmgr[3780]: E560A97: removed
Jan 10 04:37:59 mail postfix/qmgr[3780]: 0C675AD: from=<h.reindl [at] thelounge>, size=1377, nrcpt=1 (queue active)
Jan 10 04:38:00 imap-login: Info: proxy(h.reindl [at] thelounge): disconnecting 212.95.7.237
Jan 10 04:38:01 mail postfix/smtp[15599]: Host offered STARTTLS: [mail.oswalddental.net]
Jan 10 04:38:07 mail postfix/smtp[15599]: 0C675AD: to=<tabris [at] tabris>,
relay=mail.oswalddental.net[75.147.251.245]:25, delay=8.8, delays=0.01/0.01/2.1/6.8, dsn=2.0.0, status=sent (250
2.0.0 Ok: queued as 99066602A027)

>> Below afaik a perfect sample from gmail
>>
>> * Sender is "h.reindl [at] thelounge"
>> * Rcpt: "reindl.harald [at] gmail"
>> * My gmail-Account always forwards to my office-address
>>
>> please take a look at the envelope abd the spf-check from our
>> barracuda-spamfirewall, without making this changes the
>> messages would be blocked by strict spf because
>> it shows my sender-address and is coming from the google-server
>> _______________
>>
>> Received: from barracuda.thelounge.net (barracuda.thelounge.net [10.0.0.20]) (using TLSv1
>> with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested)
>> by mail.thelounge.net (Postfix) with ESMTPS id 4A344A3
>> for <h.reindl [at] thelounge>; Mon, 10 Jan 2011 04:21:11 +0100 (CET)
>> X-ASG-Debug-ID: 1294629666-03bcd9407b51fc70001-NZZS9d
>> Received: from mail-qw0-f46.google.com (mail-qw0-f46.google.com [209.85.216.46])
>> by barracuda.thelounge.net with ESMTP id DBsKQViB0BfFJKRl
>> for <h.reindl [at] thelounge>; Mon, 10 Jan 2011 04:21:07 +0100 (CET)
>> X-Barracuda-Envelope-From: reindl.harald+caf_=h.reindl=thelounge.net [at] gmail
>> X-Barracuda-Apparent-Source-IP: 209.85.216.46
>> Received-SPF: pass (barracuda.thelounge.net: domain of gmail.com designates
>> 209.85.216.46 as permitted sender) client-ip=209.85.216.46;
>> envelope-from=reindl.harald+caf_=h.reindl=thelounge.net [at] gmail;
>> Received: by qwa26 with SMTP id 26so19352331qwa.19
>> for <h.reindl [at] thelounge>; Sun, 09 Jan 2011 19:21:06 -0800 (PST)
>> Received: by 10.229.189.14 with SMTP
>> id dc14mr24604116qcb.58.1294629666121; Sun, 09 Jan 2011 19:21:06 -0800 (PST)
>> X-Forwarded-To: h.reindl [at] thelounge
>> X-Forwarded-For: reindl.harald [at] gmail h.reindl [at] thelounge
>> _______________
>>
>> yes i know i'm on holiday and must be total crazy plaing with mysql, dbmail
>> and reading docs the whole time :-)
>>
>> regards
>> harry
>>
>>
>>
>> _______________________________________________
>> DBmail mailing list
>> DBmail [at] dbmail
>> http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
>

--

Mit besten Grüßen, Reindl Harald
the lounge interactive design GmbH
A-1060 Vienna, Hofmühlgasse 17
CTO / software-development / cms-solutions
p: +43 (1) 595 3999 33, m: +43 (676) 40 221 40
icq: 154546673, http://www.thelounge.net/
Attachments: signature.asc (0.25 KB)


tabris at tabris

Jan 9, 2011, 7:58 PM

Post #4 of 8 (597 views)
Permalink
Re: dbmail / forwarding / spf / envelope [In reply to]

On 1/9/11 7:43 PM, Reindl Harald wrote:
> Am 10.01.2011 04:37, schrieb tabris:
>
>> On 1/9/11 7:33 PM, Reindl Harald wrote:
>>> Does dbmail anything like gmail by forwarding messages
>>> i have not seen - seems to be straight forwarding
>> Strange question, DBmail is not an MTA.
>> What you ask seems to be a responsibility for your MTA (postfix, exim, sendmail, etc).
> Hm not really
>
> * MTA receives a message and delivers over lmtp
> * dbmail looks in alias-table and see the forward
> * dbmail generates a new message and gives it to the mta
> * the mta does not and should not touch this message
>
> It happens the same as with my autoreply below (to you *g*)
>
> * psotfix/pickup will fetch the message from dbmail
> * uid=493 is dbmail on fedora/redhat
>

I still think I do not understand the question... perhaps b/c you are
not showing what it looks like when I send you an email to your
@thelounge.net, and it is fwded to gmail. If gmail is allowed to send
mail as you and your SPF record does not say so and msgs are lost b/c of
that... then that's your fault for not adding an mx:gmail.com to your SPF.

> Jan 10 04:37:59 mail postfix/pickup[15589]: 0C675AD: uid=493 from=<h.reindl [at] thelounge>
> Jan 10 04:37:59 mail postfix/cleanup[15595]: 0C675AD: message-id=<20110110033759.0C675AD [at] mail>
> Jan 10 04:37:59 mail postfix/lmtp[15596]: E560A97: to=<h.reindl [at] thelounge>, relay=127.0.0.1[127.0.0.1]:24,
> delay=0.13, delays=0.02/0.01/0/0.1, dsn=2.0.0, status=sent (215 Recipient <h.reindl [at] thelounge> OK)
> Jan 10 04:37:59 mail postfix/qmgr[3780]: E560A97: removed
> Jan 10 04:37:59 mail postfix/qmgr[3780]: 0C675AD: from=<h.reindl [at] thelounge>, size=1377, nrcpt=1 (queue active)
> Jan 10 04:38:00 imap-login: Info: proxy(h.reindl [at] thelounge): disconnecting 212.95.7.237
> Jan 10 04:38:01 mail postfix/smtp[15599]: Host offered STARTTLS: [mail.oswalddental.net]
> Jan 10 04:38:07 mail postfix/smtp[15599]: 0C675AD: to=<tabris [at] tabris>,
> relay=mail.oswalddental.net[75.147.251.245]:25, delay=8.8, delays=0.01/0.01/2.1/6.8, dsn=2.0.0, status=sent (250
> 2.0.0 Ok: queued as 99066602A027)
>
>>> Below afaik a perfect sample from gmail
>>>
>>> * Sender is "h.reindl [at] thelounge"
>>> * Rcpt: "reindl.harald [at] gmail"
>>> * My gmail-Account always forwards to my office-address
>>>
>>> please take a look at the envelope abd the spf-check from our
>>> barracuda-spamfirewall, without making this changes the
>>> messages would be blocked by strict spf because
>>> it shows my sender-address and is coming from the google-server
>>> _______________
>>>
>>> Received: from barracuda.thelounge.net (barracuda.thelounge.net [10.0.0.20]) (using TLSv1
>>> with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested)
>>> by mail.thelounge.net (Postfix) with ESMTPS id 4A344A3
>>> for <h.reindl [at] thelounge>; Mon, 10 Jan 2011 04:21:11 +0100 (CET)
>>> X-ASG-Debug-ID: 1294629666-03bcd9407b51fc70001-NZZS9d
>>> Received: from mail-qw0-f46.google.com (mail-qw0-f46.google.com [209.85.216.46])
>>> by barracuda.thelounge.net with ESMTP id DBsKQViB0BfFJKRl
>>> for <h.reindl [at] thelounge>; Mon, 10 Jan 2011 04:21:07 +0100 (CET)
>>> X-Barracuda-Envelope-From: reindl.harald+caf_=h.reindl=thelounge.net [at] gmail
>>> X-Barracuda-Apparent-Source-IP: 209.85.216.46
>>> Received-SPF: pass (barracuda.thelounge.net: domain of gmail.com designates
>>> 209.85.216.46 as permitted sender) client-ip=209.85.216.46;
>>> envelope-from=reindl.harald+caf_=h.reindl=thelounge.net [at] gmail;
>>> Received: by qwa26 with SMTP id 26so19352331qwa.19
>>> for <h.reindl [at] thelounge>; Sun, 09 Jan 2011 19:21:06 -0800 (PST)
>>> Received: by 10.229.189.14 with SMTP
>>> id dc14mr24604116qcb.58.1294629666121; Sun, 09 Jan 2011 19:21:06 -0800 (PST)
>>> X-Forwarded-To: h.reindl [at] thelounge
>>> X-Forwarded-For: reindl.harald [at] gmail h.reindl [at] thelounge
>>> _______________
>>>
>>> yes i know i'm on holiday and must be total crazy plaing with mysql, dbmail
>>> and reading docs the whole time :-)
>>>
>>> regards
>>> harry
>>>
>>>
>>>
>>> _______________________________________________
>>> DBmail mailing list
>>> DBmail [at] dbmail
>>> http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
Attachments: signature.asc (0.25 KB)


h.reindl at thelounge

Jan 9, 2011, 8:04 PM

Post #5 of 8 (600 views)
Permalink
Re: dbmail / forwarding / spf / envelope [In reply to]

Am 10.01.2011 04:58, schrieb tabris:

> I still think I do not understand the question... perhaps b/c you are
> not showing what it looks like when I send you an email to your
> @thelounge.net, and it is fwded to gmail. If gmail is allowed to send
> mail as you and your SPF record does not say so and msgs are lost b/c of
> that... then that's your fault for not adding an mx:gmail.com to your SPF.

This is not your choice in case of forwarding

Simple Example:

* tabris [at] tabris -> h.reindl [at] uwc
* the server has a forward to "h.reindl [at] thelounge" (dbmail_aliases)
* dbmail straight forwards your message
* without touching the envelope it leaves yours
* YOU have the control of your spf

Normally this message would be blocked and receives me only
because our external server for uwc.net is not using the MX
for our main-domain and is a trustable forwarder
Attachments: signature.asc (0.25 KB)


h.reindl at thelounge

Jan 9, 2011, 8:20 PM

Post #6 of 8 (589 views)
Permalink
Re: dbmail / forwarding / spf / envelope [In reply to]

Additional info:

http://en.wikipedia.org/wiki/Email_forwarding

> In the Sender Policy Framework (SPF), the domain-name in the envelope sender
> remains subject to policy restrictions. Therefore, SPF generally disallows plain
> message-forwarding. Intra domain redirection complies with SPF as long as the
> relevant servers share a consistent configuration. Mail servers that practise
> inter-domain message-forwarding may break SPF even if they don't implement SPF
> themselves, i.e. they neither apply SPF checks nor publish SPF records.[6] Sender
> Rewriting Scheme provides for a generic forwarding mechanism compatible with SPF.

This is why gmail changes the message and instead use "h.reindl [at] thelounge"
as envelope makes "reindl.harald+caf_=h.reindl=thelounge.net [at] gmail"

Since dbmail makes the forwarding and is the only instance who is knowing to 100%
at this time that it is a forwarding, including to know both sides of the
forward i would say this is the right place for envelope-rewrite because
i have no idea with which rukes postfix could do this afterwards

X-Barracuda-Envelope-From: reindl.harald+caf_=h.reindl=thelounge.net [at] gmail
X-Barracuda-Apparent-Source-IP: 209.85.216.46
Received-SPF: pass (barracuda.thelounge.net: domain of gmail.com designates
209.85.216.46 as permitted sender) client-ip=209.85.216.46;
envelope-from=reindl.harald+caf_=h.reindl=thelounge.net [at] gmail;


Am 10.01.2011 04:58, schrieb tabris:
> On 1/9/11 7:43 PM, Reindl Harald wrote:
>> Am 10.01.2011 04:37, schrieb tabris:
>>
>>> On 1/9/11 7:33 PM, Reindl Harald wrote:
>>>> Does dbmail anything like gmail by forwarding messages
>>>> i have not seen - seems to be straight forwarding
>>> Strange question, DBmail is not an MTA.
>>> What you ask seems to be a responsibility for your MTA (postfix, exim, sendmail, etc).
>> Hm not really
>>
>> * MTA receives a message and delivers over lmtp
>> * dbmail looks in alias-table and see the forward
>> * dbmail generates a new message and gives it to the mta
>> * the mta does not and should not touch this message
>>
>> It happens the same as with my autoreply below (to you *g*)
>>
>> * psotfix/pickup will fetch the message from dbmail
>> * uid=493 is dbmail on fedora/redhat
>>
>
> I still think I do not understand the question... perhaps b/c you are
> not showing what it looks like when I send you an email to your
> @thelounge.net, and it is fwded to gmail. If gmail is allowed to send
> mail as you and your SPF record does not say so and msgs are lost b/c of
> that... then that's your fault for not adding an mx:gmail.com to your SPF.
>
>> Jan 10 04:37:59 mail postfix/pickup[15589]: 0C675AD: uid=493 from=<h.reindl [at] thelounge>
>> Jan 10 04:37:59 mail postfix/cleanup[15595]: 0C675AD: message-id=<20110110033759.0C675AD [at] mail>
>> Jan 10 04:37:59 mail postfix/lmtp[15596]: E560A97: to=<h.reindl [at] thelounge>, relay=127.0.0.1[127.0.0.1]:24,
>> delay=0.13, delays=0.02/0.01/0/0.1, dsn=2.0.0, status=sent (215 Recipient <h.reindl [at] thelounge> OK)
>> Jan 10 04:37:59 mail postfix/qmgr[3780]: E560A97: removed
>> Jan 10 04:37:59 mail postfix/qmgr[3780]: 0C675AD: from=<h.reindl [at] thelounge>, size=1377, nrcpt=1 (queue active)
>> Jan 10 04:38:00 imap-login: Info: proxy(h.reindl [at] thelounge): disconnecting 212.95.7.237
>> Jan 10 04:38:01 mail postfix/smtp[15599]: Host offered STARTTLS: [mail.oswalddental.net]
>> Jan 10 04:38:07 mail postfix/smtp[15599]: 0C675AD: to=<tabris [at] tabris>,
>> relay=mail.oswalddental.net[75.147.251.245]:25, delay=8.8, delays=0.01/0.01/2.1/6.8, dsn=2.0.0, status=sent (250
>> 2.0.0 Ok: queued as 99066602A027)
>>
>>>> Below afaik a perfect sample from gmail
>>>>
>>>> * Sender is "h.reindl [at] thelounge"
>>>> * Rcpt: "reindl.harald [at] gmail"
>>>> * My gmail-Account always forwards to my office-address
>>>>
>>>> please take a look at the envelope abd the spf-check from our
>>>> barracuda-spamfirewall, without making this changes the
>>>> messages would be blocked by strict spf because
>>>> it shows my sender-address and is coming from the google-server
>>>> _______________
>>>>
>>>> Received: from barracuda.thelounge.net (barracuda.thelounge.net [10.0.0.20]) (using TLSv1
>>>> with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested)
>>>> by mail.thelounge.net (Postfix) with ESMTPS id 4A344A3
>>>> for <h.reindl [at] thelounge>; Mon, 10 Jan 2011 04:21:11 +0100 (CET)
>>>> X-ASG-Debug-ID: 1294629666-03bcd9407b51fc70001-NZZS9d
>>>> Received: from mail-qw0-f46.google.com (mail-qw0-f46.google.com [209.85.216.46])
>>>> by barracuda.thelounge.net with ESMTP id DBsKQViB0BfFJKRl
>>>> for <h.reindl [at] thelounge>; Mon, 10 Jan 2011 04:21:07 +0100 (CET)
>>>> X-Barracuda-Envelope-From: reindl.harald+caf_=h.reindl=thelounge.net [at] gmail
>>>> X-Barracuda-Apparent-Source-IP: 209.85.216.46
>>>> Received-SPF: pass (barracuda.thelounge.net: domain of gmail.com designates
>>>> 209.85.216.46 as permitted sender) client-ip=209.85.216.46;
>>>> envelope-from=reindl.harald+caf_=h.reindl=thelounge.net [at] gmail;
>>>> Received: by qwa26 with SMTP id 26so19352331qwa.19
>>>> for <h.reindl [at] thelounge>; Sun, 09 Jan 2011 19:21:06 -0800 (PST)
>>>> Received: by 10.229.189.14 with SMTP
>>>> id dc14mr24604116qcb.58.1294629666121; Sun, 09 Jan 2011 19:21:06 -0800 (PST)
>>>> X-Forwarded-To: h.reindl [at] thelounge
>>>> X-Forwarded-For: reindl.harald [at] gmail h.reindl [at] thelounge
>>>> _______________
>>>>
>>>> yes i know i'm on holiday and must be total crazy plaing with mysql, dbmail
>>>> and reading docs the whole time :-)
>>>>
>>>> regards
>>>> harry
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> DBmail mailing list
>>>> DBmail [at] dbmail
>>>> http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

--

Mit besten Grüßen, Reindl Harald
the lounge interactive design GmbH
A-1060 Vienna, Hofmühlgasse 17
CTO / software-development / cms-solutions
p: +43 (1) 595 3999 33, m: +43 (676) 40 221 40
icq: 154546673, http://www.thelounge.net/
Attachments: signature.asc (0.25 KB)


daniel at gosi

Jan 10, 2011, 12:25 AM

Post #7 of 8 (636 views)
Permalink
Re: dbmail / forwarding / spf / envelope [In reply to]

I think what you need to look into is SRS: http://de.wikipedia.org/wiki/Sender_Rewriting_Scheme

Kind regards,
Daniel

Am 10.01.2011 um 05:20 schrieb Reindl Harald:

> Additional info:
>
> http://en.wikipedia.org/wiki/Email_forwarding
>
>> In the Sender Policy Framework (SPF), the domain-name in the envelope sender
>> remains subject to policy restrictions. Therefore, SPF generally disallows plain
>> message-forwarding. Intra domain redirection complies with SPF as long as the
>> relevant servers share a consistent configuration. Mail servers that practise
>> inter-domain message-forwarding may break SPF even if they don't implement SPF
>> themselves, i.e. they neither apply SPF checks nor publish SPF records.[6] Sender
>> Rewriting Scheme provides for a generic forwarding mechanism compatible with SPF.
>
> This is why gmail changes the message and instead use "h.reindl [at] thelounge"
> as envelope makes "reindl.harald+caf_=h.reindl=thelounge.net [at] gmail"
>
> Since dbmail makes the forwarding and is the only instance who is knowing to 100%
> at this time that it is a forwarding, including to know both sides of the
> forward i would say this is the right place for envelope-rewrite because
> i have no idea with which rukes postfix could do this afterwards
>
> X-Barracuda-Envelope-From: reindl.harald+caf_=h.reindl=thelounge.net [at] gmail
> X-Barracuda-Apparent-Source-IP: 209.85.216.46
> Received-SPF: pass (barracuda.thelounge.net: domain of gmail.com designates
> 209.85.216.46 as permitted sender) client-ip=209.85.216.46;
> envelope-from=reindl.harald+caf_=h.reindl=thelounge.net [at] gmail;
>
>
> Am 10.01.2011 04:58, schrieb tabris:
>> On 1/9/11 7:43 PM, Reindl Harald wrote:
>>> Am 10.01.2011 04:37, schrieb tabris:
>>>
>>>> On 1/9/11 7:33 PM, Reindl Harald wrote:
>>>>> Does dbmail anything like gmail by forwarding messages
>>>>> i have not seen - seems to be straight forwarding
>>>> Strange question, DBmail is not an MTA.
>>>> What you ask seems to be a responsibility for your MTA (postfix, exim, sendmail, etc).
>>> Hm not really
>>>
>>> * MTA receives a message and delivers over lmtp
>>> * dbmail looks in alias-table and see the forward
>>> * dbmail generates a new message and gives it to the mta
>>> * the mta does not and should not touch this message
>>>
>>> It happens the same as with my autoreply below (to you *g*)
>>>
>>> * psotfix/pickup will fetch the message from dbmail
>>> * uid=493 is dbmail on fedora/redhat
>>>
>>
>> I still think I do not understand the question... perhaps b/c you are
>> not showing what it looks like when I send you an email to your
>> @thelounge.net, and it is fwded to gmail. If gmail is allowed to send
>> mail as you and your SPF record does not say so and msgs are lost b/c of
>> that... then that's your fault for not adding an mx:gmail.com to your SPF.
>>
>>> Jan 10 04:37:59 mail postfix/pickup[15589]: 0C675AD: uid=493 from=<h.reindl [at] thelounge>
>>> Jan 10 04:37:59 mail postfix/cleanup[15595]: 0C675AD: message-id=<20110110033759.0C675AD [at] mail>
>>> Jan 10 04:37:59 mail postfix/lmtp[15596]: E560A97: to=<h.reindl [at] thelounge>, relay=127.0.0.1[127.0.0.1]:24,
>>> delay=0.13, delays=0.02/0.01/0/0.1, dsn=2.0.0, status=sent (215 Recipient <h.reindl [at] thelounge> OK)
>>> Jan 10 04:37:59 mail postfix/qmgr[3780]: E560A97: removed
>>> Jan 10 04:37:59 mail postfix/qmgr[3780]: 0C675AD: from=<h.reindl [at] thelounge>, size=1377, nrcpt=1 (queue active)
>>> Jan 10 04:38:00 imap-login: Info: proxy(h.reindl [at] thelounge): disconnecting 212.95.7.237
>>> Jan 10 04:38:01 mail postfix/smtp[15599]: Host offered STARTTLS: [mail.oswalddental.net]
>>> Jan 10 04:38:07 mail postfix/smtp[15599]: 0C675AD: to=<tabris [at] tabris>,
>>> relay=mail.oswalddental.net[75.147.251.245]:25, delay=8.8, delays=0.01/0.01/2.1/6.8, dsn=2.0.0, status=sent (250
>>> 2.0.0 Ok: queued as 99066602A027)
>>>
>>>>> Below afaik a perfect sample from gmail
>>>>>
>>>>> * Sender is "h.reindl [at] thelounge"
>>>>> * Rcpt: "reindl.harald [at] gmail"
>>>>> * My gmail-Account always forwards to my office-address
>>>>>
>>>>> please take a look at the envelope abd the spf-check from our
>>>>> barracuda-spamfirewall, without making this changes the
>>>>> messages would be blocked by strict spf because
>>>>> it shows my sender-address and is coming from the google-server
>>>>> _______________
>>>>>
>>>>> Received: from barracuda.thelounge.net (barracuda.thelounge.net [10.0.0.20]) (using TLSv1
>>>>> with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested)
>>>>> by mail.thelounge.net (Postfix) with ESMTPS id 4A344A3
>>>>> for <h.reindl [at] thelounge>; Mon, 10 Jan 2011 04:21:11 +0100 (CET)
>>>>> X-ASG-Debug-ID: 1294629666-03bcd9407b51fc70001-NZZS9d
>>>>> Received: from mail-qw0-f46.google.com (mail-qw0-f46.google.com [209.85.216.46])
>>>>> by barracuda.thelounge.net with ESMTP id DBsKQViB0BfFJKRl
>>>>> for <h.reindl [at] thelounge>; Mon, 10 Jan 2011 04:21:07 +0100 (CET)
>>>>> X-Barracuda-Envelope-From: reindl.harald+caf_=h.reindl=thelounge.net [at] gmail
>>>>> X-Barracuda-Apparent-Source-IP: 209.85.216.46
>>>>> Received-SPF: pass (barracuda.thelounge.net: domain of gmail.com designates
>>>>> 209.85.216.46 as permitted sender) client-ip=209.85.216.46;
>>>>> envelope-from=reindl.harald+caf_=h.reindl=thelounge.net [at] gmail;
>>>>> Received: by qwa26 with SMTP id 26so19352331qwa.19
>>>>> for <h.reindl [at] thelounge>; Sun, 09 Jan 2011 19:21:06 -0800 (PST)
>>>>> Received: by 10.229.189.14 with SMTP
>>>>> id dc14mr24604116qcb.58.1294629666121; Sun, 09 Jan 2011 19:21:06 -0800 (PST)
>>>>> X-Forwarded-To: h.reindl [at] thelounge
>>>>> X-Forwarded-For: reindl.harald [at] gmail h.reindl [at] thelounge
>>>>> _______________
>>>>>
>>>>> yes i know i'm on holiday and must be total crazy plaing with mysql, dbmail
>>>>> and reading docs the whole time :-)
>>>>>
>>>>> regards
>>>>> harry
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> DBmail mailing list
>>>>> DBmail [at] dbmail
>>>>> http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
>
> --
>
> Mit besten Grüßen, Reindl Harald
> the lounge interactive design GmbH
> A-1060 Vienna, Hofmühlgasse 17
> CTO / software-development / cms-solutions
> p: +43 (1) 595 3999 33, m: +43 (676) 40 221 40
> icq: 154546673, http://www.thelounge.net/
>
>
>
> _______________________________________________
> DBmail mailing list
> DBmail [at] dbmail
> http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

_______________________________________________
DBmail mailing list
DBmail [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail


h.reindl at thelounge

Jan 10, 2011, 4:27 AM

Post #8 of 8 (583 views)
Permalink
Re: dbmail / forwarding / spf / envelope [In reply to]

Thats right, but i can not implement it in dbmail :-(

Some dirty hack using SRS for all mails on postfix-side
is not a real solution because non-forwards should
never be touched

regards
harry

Am 10.01.2011 09:25, schrieb Daniel Urstöger:
> I think what you need to look into is SRS: http://de.wikipedia.org/wiki/Sender_Rewriting_Scheme
>
> Kind regards,
> Daniel
>
> Am 10.01.2011 um 05:20 schrieb Reindl Harald:
>
>> Additional info:
>>
>> http://en.wikipedia.org/wiki/Email_forwarding
>>
>>> In the Sender Policy Framework (SPF), the domain-name in the envelope sender
>>> remains subject to policy restrictions. Therefore, SPF generally disallows plain
>>> message-forwarding. Intra domain redirection complies with SPF as long as the
>>> relevant servers share a consistent configuration. Mail servers that practise
>>> inter-domain message-forwarding may break SPF even if they don't implement SPF
>>> themselves, i.e. they neither apply SPF checks nor publish SPF records.[6] Sender
>>> Rewriting Scheme provides for a generic forwarding mechanism compatible with SPF.
>>
>> This is why gmail changes the message and instead use "h.reindl [at] thelounge"
>> as envelope makes "reindl.harald+caf_=h.reindl=thelounge.net [at] gmail"
>>
>> Since dbmail makes the forwarding and is the only instance who is knowing to 100%
>> at this time that it is a forwarding, including to know both sides of the
>> forward i would say this is the right place for envelope-rewrite because
>> i have no idea with which rukes postfix could do this afterwards
>>
>> X-Barracuda-Envelope-From: reindl.harald+caf_=h.reindl=thelounge.net [at] gmail
>> X-Barracuda-Apparent-Source-IP: 209.85.216.46
>> Received-SPF: pass (barracuda.thelounge.net: domain of gmail.com designates
>> 209.85.216.46 as permitted sender) client-ip=209.85.216.46;
>> envelope-from=reindl.harald+caf_=h.reindl=thelounge.net [at] gmail;
>>
>>
>> Am 10.01.2011 04:58, schrieb tabris:
>>> On 1/9/11 7:43 PM, Reindl Harald wrote:
>>>> Am 10.01.2011 04:37, schrieb tabris:
>>>>
>>>>> On 1/9/11 7:33 PM, Reindl Harald wrote:
>>>>>> Does dbmail anything like gmail by forwarding messages
>>>>>> i have not seen - seems to be straight forwarding
>>>>> Strange question, DBmail is not an MTA.
>>>>> What you ask seems to be a responsibility for your MTA (postfix, exim, sendmail, etc).
>>>> Hm not really
>>>>
>>>> * MTA receives a message and delivers over lmtp
>>>> * dbmail looks in alias-table and see the forward
>>>> * dbmail generates a new message and gives it to the mta
>>>> * the mta does not and should not touch this message
>>>>
>>>> It happens the same as with my autoreply below (to you *g*)
>>>>
>>>> * psotfix/pickup will fetch the message from dbmail
>>>> * uid=493 is dbmail on fedora/redhat
>>>>
>>>
>>> I still think I do not understand the question... perhaps b/c you are
>>> not showing what it looks like when I send you an email to your
>>> @thelounge.net, and it is fwded to gmail. If gmail is allowed to send
>>> mail as you and your SPF record does not say so and msgs are lost b/c of
>>> that... then that's your fault for not adding an mx:gmail.com to your SPF.
>>>
>>>> Jan 10 04:37:59 mail postfix/pickup[15589]: 0C675AD: uid=493 from=<h.reindl [at] thelounge>
>>>> Jan 10 04:37:59 mail postfix/cleanup[15595]: 0C675AD: message-id=<20110110033759.0C675AD [at] mail>
>>>> Jan 10 04:37:59 mail postfix/lmtp[15596]: E560A97: to=<h.reindl [at] thelounge>, relay=127.0.0.1[127.0.0.1]:24,
>>>> delay=0.13, delays=0.02/0.01/0/0.1, dsn=2.0.0, status=sent (215 Recipient <h.reindl [at] thelounge> OK)
>>>> Jan 10 04:37:59 mail postfix/qmgr[3780]: E560A97: removed
>>>> Jan 10 04:37:59 mail postfix/qmgr[3780]: 0C675AD: from=<h.reindl [at] thelounge>, size=1377, nrcpt=1 (queue active)
>>>> Jan 10 04:38:00 imap-login: Info: proxy(h.reindl [at] thelounge): disconnecting 212.95.7.237
>>>> Jan 10 04:38:01 mail postfix/smtp[15599]: Host offered STARTTLS: [mail.oswalddental.net]
>>>> Jan 10 04:38:07 mail postfix/smtp[15599]: 0C675AD: to=<tabris [at] tabris>,
>>>> relay=mail.oswalddental.net[75.147.251.245]:25, delay=8.8, delays=0.01/0.01/2.1/6.8, dsn=2.0.0, status=sent (250
>>>> 2.0.0 Ok: queued as 99066602A027)
>>>>
>>>>>> Below afaik a perfect sample from gmail
>>>>>>
>>>>>> * Sender is "h.reindl [at] thelounge"
>>>>>> * Rcpt: "reindl.harald [at] gmail"
>>>>>> * My gmail-Account always forwards to my office-address
>>>>>>
>>>>>> please take a look at the envelope abd the spf-check from our
>>>>>> barracuda-spamfirewall, without making this changes the
>>>>>> messages would be blocked by strict spf because
>>>>>> it shows my sender-address and is coming from the google-server
>>>>>> _______________
>>>>>>
>>>>>> Received: from barracuda.thelounge.net (barracuda.thelounge.net [10.0.0.20]) (using TLSv1
>>>>>> with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested)
>>>>>> by mail.thelounge.net (Postfix) with ESMTPS id 4A344A3
>>>>>> for <h.reindl [at] thelounge>; Mon, 10 Jan 2011 04:21:11 +0100 (CET)
>>>>>> X-ASG-Debug-ID: 1294629666-03bcd9407b51fc70001-NZZS9d
>>>>>> Received: from mail-qw0-f46.google.com (mail-qw0-f46.google.com [209.85.216.46])
>>>>>> by barracuda.thelounge.net with ESMTP id DBsKQViB0BfFJKRl
>>>>>> for <h.reindl [at] thelounge>; Mon, 10 Jan 2011 04:21:07 +0100 (CET)
>>>>>> X-Barracuda-Envelope-From: reindl.harald+caf_=h.reindl=thelounge.net [at] gmail
>>>>>> X-Barracuda-Apparent-Source-IP: 209.85.216.46
>>>>>> Received-SPF: pass (barracuda.thelounge.net: domain of gmail.com designates
>>>>>> 209.85.216.46 as permitted sender) client-ip=209.85.216.46;
>>>>>> envelope-from=reindl.harald+caf_=h.reindl=thelounge.net [at] gmail;
>>>>>> Received: by qwa26 with SMTP id 26so19352331qwa.19
>>>>>> for <h.reindl [at] thelounge>; Sun, 09 Jan 2011 19:21:06 -0800 (PST)
>>>>>> Received: by 10.229.189.14 with SMTP
>>>>>> id dc14mr24604116qcb.58.1294629666121; Sun, 09 Jan 2011 19:21:06 -0800 (PST)
>>>>>> X-Forwarded-To: h.reindl [at] thelounge
>>>>>> X-Forwarded-For: reindl.harald [at] gmail h.reindl [at] thelounge
>>>>>> _______________
>>>>>>
>>>>>> yes i know i'm on holiday and must be total crazy plaing with mysql, dbmail
>>>>>> and reading docs the whole time :-)
>>>>>>
>>>>>> regards
>>>>>> harry
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> DBmail mailing list
>>>>>> DBmail [at] dbmail
>>>>>> http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
>>
>> --
>>
>> Mit besten Grüßen, Reindl Harald
>> the lounge interactive design GmbH
>> A-1060 Vienna, Hofmühlgasse 17
>> CTO / software-development / cms-solutions
>> p: +43 (1) 595 3999 33, m: +43 (676) 40 221 40
>> icq: 154546673, http://www.thelounge.net/
>>
>>
>>
>> _______________________________________________
>> DBmail mailing list
>> DBmail [at] dbmail
>> http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
>
> _______________________________________________
> DBmail mailing list
> DBmail [at] dbmail
> http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

--

Mit besten Grüßen, Reindl Harald
the lounge interactive design GmbH
A-1060 Vienna, Hofmühlgasse 17
CTO / software-development / cms-solutions
p: +43 (1) 595 3999 33, m: +43 (676) 40 221 40
icq: 154546673, http://www.thelounge.net/
Attachments: signature.asc (0.25 KB)

DBMail users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.