-
-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature regression: Sender's Name & Email Address #102
Comments
Hi @kunalsood, Thanks for reaching out. I changed this recently when I was simplifying some things in Kill the Newsletter! It’s something we can bring back, yes, but it’s annoying to migrate data, so I’ll wait for more people to ask for this before I do the work. Thanks. |
I ended up implemeting this in version 2.0.6 because there were some other data migrations to do. |
Hi @leafac, Thanks! I do have a concern regarding the new implementation though. My Morning Brew newsletter feed now has author tags that look something like the following :-
or
I'm curious where these email addresses are coming from? I ask because as far as I'm aware, Moring Brew only send emails from email addresses that look like I'm seeing a similar issue with other newsletters as well. For example, my feed of TLDR Newsletter now contains author tags that look like:-
While in my email, these newsletters come from Could these author tags be containing the reply-to emails & not the actual sender's info? |
Yes, you got it. Right now we’re picking up the email address from the I’ll look into this… |
@leafac Thanks for your efforts! Out of curiosity, where were you getting sender's info from prior to sometime around May 5, 2024? Until that point of time, IIRC, the author tags used to look something like these:-
|
I think we used to get that information from the message |
As of recently, the author tags on all item in all my feeds look like :-
Is there any chance we can go back to reporting the real sender's name & email address?
The text was updated successfully, but these errors were encountered: