Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.I can read the title/subject of previous email already sent in the code of next emails sent !!!
It's like if the subject was cached for all next emails : New emails titles are not printed in code.
This is a big problem because personnal informations like names are sometimes printed in subject.
With this bug, those personal information are printed in code and sent to another person when next email is sent.
It not usual for everybody to read the email code... but some emails clients - like K-9 mail on android - really display the subject from code... so the receiver can see another title complety out of purpose...
I am not sure about which email module is responsable about that... : may be this problem is coming from other emailing module like mailsystem or echo.
| Comment | File | Size | Author |
|---|
Comments
Comment #2
Utkarsh_Mishra CreditAttribution: Utkarsh_Mishra at OpenSense Labs for DrupalFit commentedthis patch rebuild the form with some defaults value so that fields should be good as new for new mail.
Comment #3
salvisWhat do you mean with "in the code"? What exactly is the problem that you're seeing.
#2 looks like it's destroying useful functionality...
Comment #4
Joran Lafleuriel CreditAttribution: Joran Lafleuriel commentedHi Salvis...
Sorry for coming back and responding to you a so long time after your demand.
But I just saw that this issue is still a pb for me. I don't understand if the htmlmail module is directcly responsible of that.
Mailsystem, Echo or Simplenews could be.
I meant that when I inspect the hmtl code of a received email, I can read that most of headers tags are wrongs.
They comes from a previous sent email.... as if previous page sent by email was cached.
In my case it's a very bad problem of security because some websites I manage sends me notifications when users logs in.
The notification is sent in html with Htmlmail / Mailsystem / Echo.
Then if I send a newsletter just after, the email html code contains headers with personnals informations of who connected just before !!!!!!!!
I have to stop this... because receivers cand read non appropriate datas if they inspect the received html code.
I've started to stop sending email from drupal with personnal information.... I agree.
But the issue is still here.
I use Drupal 7, PHP 7.1 whith opcache and memcached, custom Omega Five template.
I will switch to bootstrap custom template soon... and see if the issue persists
I hope this can help. I go on searching by my side.
Comment #5
Joran Lafleuriel CreditAttribution: Joran Lafleuriel commentedMy Metatag conf is set to keep a cache... This could be the reason why wrong header is sent....
Comment #6
salvisHave you been able to try turning off Metatag's cache? Is Metatag even involved in generating the email content? That is unusual.
I understand that this is a serious issue, but I don't know what to do about it.
It seems that there are only two of you who have this issue — there must be something special in your set-up...
Comment #7
Joran Lafleuriel CreditAttribution: Joran Lafleuriel commentedHi Salvis. Thank you for your help.
I think more and more that Metatag cache option is responsible.
As you suggest, I just proceed to a new test :
I suppose that Metatag cache is an important option for load performance, so we would prefer to keep it ON.
And what if Simplenew was able to empty the cache once before sending a email test or the entire spool...This could be a solution.... but Simplenews is not the only module to send emails.
And if Html Mail could empty Metatag cache before sending ?.... What about Simplenews cache option which is great for spool sending ?
Complicated as usual.... ;-)
For more precisions here you are my conf :
Drupal 7.65
Html mail 7.x-2.71
Echo 7.x-1.9,
Simplenews 7.x-1.1+1-dev,
Metatag 7.x-1.25
Comment #8
salvisThank you for following through with testing.
I think, this needs to be addressed in Metatag, or at least they need to look into it.
Caching is typically an optional offer. If it works, you take it, but if it doesn't work, you can ask the provider (Metatag) to improve it. They may find that they need help from a third party (Simplenews or HTML Mail) to do it properly, but it's not the third party's job to interfere and fight.
Comment #9
DamienMcKennaThis is all very weird. I haven't used Simplenews to know how it's generating emails - does it take the compete rendered output of a page and send that? Does the URL of that page change for each newsletter or is it the same URL each time?