Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
Option to set envelope-from explicitly like in older versions #629
I have my own domain name and prefer using mailaddresses with that domain name for anything public, including some mailing lists.
However, my ISP won't allow sending mail from "foreign" mail addresses.
My current workaround is to set the mail address given by my ISP as From, and the one with my domain name as Reply-To. This works, but is clumsy to use on mailing lists, as responses to my mail end up being sent both to the list and to myself, and because it reveals the address I really meant to keep private.
In older versions of YAM (2.3? 2.4?), there was a possibility to configure the envelope-from address, IIRC in the "hidden" config file section. It would be great if this possibility would return, except now of course as something you could set for each specific identity.
This would make it possible for me to have my "foreign" mail address in the From field while having YAM give the SMTP server the allowed address as envelope-from.
I can hardly remember what this "envelope-from" functionality you are pointing at former versions really did, but AFAIR this was also removed during the change in identity management because using a different envelope-from (MAIL FROM: in SMTP communication) address than the from (FROM: in email) address resulted in having these kind of emails being identified as SPAM these days. So please give some example (in terms of showing email headers and what you exactly mean) so that we can better investigate this. But I still feel that using a different email address in the SMTP communication than used in the email RFC822 header would simply result in risking that you domain would sooner or later end up in a public SPAM list.
Better would be if you would register your public domain to your ISP in a way that they also accept emails coming from this domain. Or if you have registered that domain at a different provider you should be able to convince that provider to provide you a SMTP connection to which you could send your emails to. Anything else would really just be a workaround that modern SPAM engine would recognize as potential SPAM an flag your emails accordingly.
On 27/06-2016 at 00:40:01 UTC, Jens Maus wrote:
You may be right about the spam identification risk, I haven't thought about
Your understanding of what I had in mind is otherwise spot on. I was
I've been looking through my old Sent folders, but it doesn't look like the
Edit: And now I found such an example. A mail I sent to a number of BCC:
I enclose an LhA with the headers in the one I received back.
That would of course solve it, if only they would accept it. It's worth a
I have registered the domain at a DNS service (Gratisdns.dk) which also
They do also offer a mail hotel, which would give me the opportunity to use
I could of course ask them if I could please use their SMTP server (without
*/L][_* _ // Yet another | Niels Bache, Groenlandsvej 12 B