On Tue, Oct 26, 2004 at 06:14:30PM -0700, Jeff Chan wrote:
> On Tuesday, October 26, 2004, 11:43:38 AM, snowjack snowjack wrote:
> > On Tue, 26 Oct 2004 13:37:38 -0400 (EDT), "Ron Johnson"
> > <[EMAIL PROTECTED]> said:
> >> Seems to me that using some kind of Milter (I'd do it in Mimedefang,
> >> but that's because I'm already using it) you could do something like:
> >>
> >> Does user exist? Process normally
> >> Did user ever exist? Bounce.
> >> User never existed? Do something like the old spamshield
> >> (deny access to the sending system. Choose your method)
> > Pedantic nit-pick of the day:
> > I'm sure you meant reject instead of bounce, right?
>
> "Bounce" to some means reject. "Bounce" to others means forward.
Well, "bounce" (in this context) generally means that the receiving MTA
accepts the message and then returns ("bounces") it back to the sender;
rejecting a message at the MTA level simply tells the /sending/ MTA that
the message wasn't accepted - it's then the sending MTA's job to
"bounce" the message back to the user.
> For me, it always meant reject. As far as I can tell bounce
> meaning reject is a server term and bounce meaning forward
> is something from userland.
Well Pine, Eudora, mutt, and some other programs have a "bounce" feature
(which is indeed entirely separate) - but this is different from
forwarding a message - it's basically resending the original message
with as little as possible changed (usually resent-to and resent-from
headers are added, the envelope-sender is changed, and new Received
lines are added).
So really, we're talking about 4 or so separate things here.
