James Thornton <[EMAIL PROTECTED]> writes: > My university mail account, [EMAIL PROTECTED], is forwarded to my > primary account via a .forward file: > > bash-2.04$ cat .forward > [EMAIL PROTECTED] > > When an uncomfirmed user sends mail to [EMAIL PROTECTED], a > confirmation request is sent as [EMAIL PROTECTED] If > the original sender replies to the confirmation request, another > confirmation request is sent confirming the confirmation, and it is in > the form of [EMAIL PROTECTED] (which is an > invalid address). > > What is the best way for dealing with this scenario?
It depends on what, exactly, you want to have happen and possibly on what MTA the CS department at Baylor uses. Let me list a couple possibilities and you can decide what you want to do. We'll go from there. 1) Mail sent to your Baylor account is forwarded like today and all further interaction with the sender uses your primary email address instead of the Baylor address ([EMAIL PROTECTED], IOW). 2) Mail sent to your Baylor account is forwarded but all further interaction with the sender regarding this piece of mail uses the Baylor address ([EMAIL PROTECTED]). Depending on the university's MTA, either is possible and you should decide which scenario you prefer before we try to solve the problem. The LOGFILE_INCOMING entries for the incoming message and the confirmation reply (that gets re-confirmed) will be helpful, though. Tim _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
