From: Infomatik <in...@ma...> - 2004-06-21 10:34:21
|
=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 20 June 2004 22:03, you wrote: > > I think this task is not for an email client to do, it is an MTA decisi= on > > based on the successfull user login > > Sometimes it is, sometimes rewriting outgoing domains with the MTA is > not feasible or is not practical. > bullshit, what you describe here are spammer technics=20 a MTA which allows sending mail by not existing user is probably an open re= lay=20 and certainly possible a spam source > > which indeed could by anything even an IP address or localhost :) and > > that is not ok > > Config problem on the system administrator's part. another big bullshit from you "localhost" and IP addresses are part of the Internet and so are part of an= =20 email system a problem comes up when somebody claims to be pdonthink@localhost as=20 sender ... still bigger when the MTA let it through - and you try to tell m= e=20 that is supposed to be so > great. Sure, you can do all the rewriting with your MTA, but this > presumes that you only have local users and limits your ability to have > both "jo...@do..." and "jo...@do...". Not a very good system > if you ask me.=20 any mailserver today can have the same usr under different domain names and the issue is not that I can, the issue is that I MUST do it at MTA level like I told you before, if giving this option to the user, and my MTA let i= t=20 through I have an incorrect configured system - and not contrary like you=20 claim most mail servers have the option for "address must exist if claimed to be= =20 local" - that is legacy protection under spam and relay concerns today even if a usr do write his sender address wrong and it goes through on a=20 system configured by a not experienced sysadm it would most probably be=20 rejected with 451 or 550 by the receiver MTA (if configured strictly) so instead given the usr possibilities to do wrong we shoud help him to do = it=20 right and easier. > > nonono > > I can have a server where run SM and I can setup it to access it ONLY as > > sm.domain.com > > Why would you do that? My virtual domains can all log into their email > using their own domain, which is a better solution IMHO: > mail.domainA.com, mail.domainB.com, etc. And all with ONE SM > installation. > The wonderful is that you can use different approaches. There are rules=20 defined in the RFCs and within them you can go free but like i see here you= r=20 issue is "YOUR solution is the only one" and any who do not agree get shut= =20 down. I do not care by which name you get your users to your server and you=20 shouldn't do it either for others - but you can not presume that whatever t= he=20 guy typed in is the host portion of his e-mail address ... even if it is so= =20 in your case. Jo=E3o =2D --=20 Infomatik =A0=A0=A0=A0=A0=A0=A0=A0implementamos asas na sua rede. (18)222.3345=A0=A0=A0=A0(18)8112.7007=A0=A0=A0(18)9773.1053 _______________________________________________________ Participe na lista de seguran=E7a, =A0=A0=A0=A0=A0=A0=A0=A0recebendo as mais importantes not=EDcias na hora: Envie uma e-mail para li...@ma... com o texto: =A0=A0=A0=A0=A0=A0=A0=A0subscribe sec...@ma... _______________________________________________________ GPG Public Key http://info.matik.com.br/info.asc Mensagens sem assinatura GPG n=E3o s=E3o nossas. Messages without GPG signature are not from us. _______________________________________________________ =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA1rkUN1twiAYpIUoRAknWAJwJvsdRda2Zp7ZXO/zJ89E+jRCeDgCfYqkP ndFt1aIW09xpe78mWIufKdk=3D =3DIVFO =2D----END PGP SIGNATURE----- |