|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Subject: Re: ETRN too fast!
From: Robert A. Rosenberg (bob.rosenberg
digitscorp.com)Date: Thu Sep 28 2000 - 11:09:03 CDT
- Next message: Robert A. Rosenberg: "Re: ETRN too fast!"
- Previous message: Daniel Roesen: "Re: ETRN too fast!"
- In reply to: Rask Ingemann Lambertsen: "Re: ETRN too fast!"
- Next in thread: Len Conrad: "Re: ETRN too fast!"
- Reply: Robert A. Rosenberg: "Re: ETRN too fast!"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
At 03:01 AM 09/28/2000 +0200, Rask Ingemann Lambertsen wrote:
>Should you still want to overburden Wietze with new things to add to
>Postfix, try ESMTP ATRN (RFC 2645), but IMHO, it fills a much needed gap.
>ETRN doesn't have the security problems of ATRN and is much simpler to
>implement in the server as well as in the client.
What security problems are you thinking of. To issue ATRN (and ask that the
provider's SMTP Server connect to you for MTA-to-MTA forwarding after
turning the connection around) you must first have issued an AUTH. The AUTH
insures that the ATRN issuer is allowed to accept the email.
- Next message: Robert A. Rosenberg: "Re: ETRN too fast!"
- Previous message: Daniel Roesen: "Re: ETRN too fast!"
- In reply to: Rask Ingemann Lambertsen: "Re: ETRN too fast!"
- Next in thread: Len Conrad: "Re: ETRN too fast!"
- Reply: Robert A. Rosenberg: "Re: ETRN too fast!"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]