Hello!
Thanks for your idea but that was not my question.
It relates to the Return path definition in the email module and I do not know where to change.
Alex would know. I had to play a lot before I found out about *.eml! Now I do not know about sending emails by any user.
What I meant, to make it more clear, is that when the user sends an email and if the recipient does not exists, then the emails cannot be received back into his or her account because the returnpath is that of default@server.com and not the user defined by FROM line. For e.g.
If the user is Alex@gt.com and he sends email to bill@gates.com
Now bill@gates.com does not exists.
So the email needs to come back.
When the email was sent, it contained the return path as either root@gt.com nouser@gt.com or anonymous@gt.com!
When the email gets returned it will land into those three default email box and not to Alex@gt.com, even though the FROM address was defined as Alex@gt.com
Thats the problem. To pass the variable to the returnpath.
Alex, what do you think about some magic tags of
Return Path: <GT::xx::<%user%>@domain%>
Can this be done by those magical tags?
Can all the templates, including the *.eml + email.cgi, etc parse those magical tags?
Thanks for your idea but that was not my question.
It relates to the Return path definition in the email module and I do not know where to change.
Alex would know. I had to play a lot before I found out about *.eml! Now I do not know about sending emails by any user.
What I meant, to make it more clear, is that when the user sends an email and if the recipient does not exists, then the emails cannot be received back into his or her account because the returnpath is that of default@server.com and not the user defined by FROM line. For e.g.
If the user is Alex@gt.com and he sends email to bill@gates.com
Now bill@gates.com does not exists.
So the email needs to come back.
When the email was sent, it contained the return path as either root@gt.com nouser@gt.com or anonymous@gt.com!
When the email gets returned it will land into those three default email box and not to Alex@gt.com, even though the FROM address was defined as Alex@gt.com
Thats the problem. To pass the variable to the returnpath.
Alex, what do you think about some magic tags of
Return Path: <GT::xx::<%user%>@domain%>
Can this be done by those magical tags?
Can all the templates, including the *.eml + email.cgi, etc parse those magical tags?