Re: [courier-users] Local delivery based on solely SMTP

This is a MIME GnuPG-signed message. If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.
The Internet standard for MIME PGP messages, RFC 2015, was published in 1996.
To open this message correctly you will need to install E-mail or Usenet
software that supports modern Internet standards.

--===============0838885425==
Content-Type: multipart/signed;
boundary="=_mimegpg-commodore.email-scan.com-16729-1184884183-0002";
micalg=pgp-sha1; protocol="application/pgp-signature"

This is a MIME GnuPG-signed message. If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.
The Internet standard for MIME PGP messages, RFC 2015, was published in 1996.
To open this message correctly you will need to install E-mail or Usenet
software that supports modern Internet standards.

--=_mimegpg-commodore.email-scan.com-16729-1184884183-0002
Content-Type: text/plain; format=flowed; charset="US-ASCII"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Ryan Parlee writes:

>
> I have a need to perform local delivery based solely on the user that is
> authenticated with SMTP. The logic I'm trying to accomplish looks like this:
>
>
> 1. Joe's email client connects to my Courier via SMTP
>
> 2. Joe's email client provides credentials and Courier authenticates as user
> Joe@Domain.com
>
> 3. Courier allows the connection, but rather than deliver to
> Bob@AnotherDomain.com, Courier does a local delivery to a Maildir
>
>
> Later, another process will pickup mail in the Maildir via POP3 and do some
> other formatting to the message before finally queuing it to be delivered as
> normal (i.e. to Bob@AnotherDoamin.com)
>
>
>
> Note that the original email will look like this:
>
> From: Joe@Domain.com
> To: Bob@AnotherDomain.com
> Subject: Hi

No it won't.

There's absolutely no reason why someone can't authenticate as address A,
send a message with the return address set to B, and put address C in the
headers.

> Courier's normal behavior is to simply relay the message, and NOT do a local
> delivery? Is there some way to force a local delivery based on the fact
> that "Joe@Domain.com" is the authenticated user?

Nope.



--=_mimegpg-commodore.email-scan.com-16729-1184884183-0002
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQBGn+XXx9p3GYHlUOIRAoyFAJ9AjL/KmDCzeZ0H8jGMm4lHZR9VZQCfTwXM
XyEQ5m7G97MBApPH7s5hgR0=
=hUDS
-----END PGP SIGNATURE-----

--=_mimegpg-commodore.email-scan.com-16729-1184884183-0002--


--===============0838885425==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
--===============0838885425==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users

--===============0838885425==--