Re: [exim] OT(?): 1und1 (Kundenserver) using unusable Envelo…

Top Page
Delete this message
Reply to this message
Author: Heiko Schlittermann
Date:  
To: exim-users
Subject: Re: [exim] OT(?): 1und1 (Kundenserver) using unusable Envelope-From?
Hello Jan,

Jan Doberstein <jan.doberstein@???> (Di 21 Nov 2006 14:41:42 CET):
> Hi Heiko,
>
> Heiko Schlittermann wrote:
> > is there anybody out, who could confirm that the German ISP 1und1 uses
> > quite useless sender addresses for relaying mails from its customers to
> > outside world?
>
> maybe i can clarify, cause i know a bit about the 1and1 mailsystem. we
> quit not using nemesis, but have similar function in our exim setup.
> >
> > 2006-11-20 16:14:11 1GmAqP-0003rO-3w \
> >     <= SRS0=zmI/=FA=arnold.schlittermann.de=arnold@??? \
> >     H=moutng.kundenserver.de [212.227.126.171] \
> >     P=esmtp S=1216 id=20061120151358.GD11857@???
> > 2006-11-20 16:14:12 1GmAqP-0003rO-3w \
> >     => arnold@??? \
> >     R=amavis T=amavis H=eth1.tigger.schlittermann.de [212.80.235.129]
> > 2006-11-20 16:14:12 1GmAqP-0003rO-3w \
> >     Completed

>
>
> if you had an adress within the nemesis and forward this adress to an
> outsite domain (it mean external adress) it will do an srs (we do it the
> same way).


Hm, that's visible in the lines above, they do SRS. There's nothing
wrong with doing this.

> srs sendback work fine, but must also pass all acl checks and filter ...


And that's exactly what doesn't do. Bounce(!) mail (mail with "<>"
sender) to a SRS generated address doesn't work. But should.

I refuse to send bounces with not null sender, because that seems to be
Quatsch and not according the rules ... (?)

> just little idea, cause i didn't know any problems and we exchange a lot
> of mail with 1and1 ...


Did you ever try to bounce(!) some mail back to 1und1?


    Best regards from Dresden
    Viele Grüße aus Dresden
    Heiko Schlittermann
-- 
 SCHLITTERMANN.de ---------------------------- internet & unix support -
 Heiko Schlittermann HS12-RIPE -----------------------------------------
 gnupg encrypted messages are welcome - key ID: 48D0359B ---------------
 gnupg fingerprint: 3061 CFBF 2D88 F034 E8D2  7E92 EE4E AC98 48D0 359B -