Closed (works as designed)
Project:
SMTP Authentication Support
Version:
6.x-1.0-beta4
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
31 Aug 2009 at 14:45 UTC
Updated:
26 Apr 2016 at 23:15 UTC
Jump to comment: Most recent
Comments
Comment #1
oadaeh commentedIt is not the purpose of this module to convert tokens, but to provide an alternate method of sending e-mail, other than the default PHP method. The tokens should be converted by the module with which you used to create the message.
Comment #2
mtndan commentedOk, so then the core triggers and actions modules are not doing token replacement correctly?
Comment #3
oadaeh commentedI don't know, as I don't use them.
Comment #4
jairgee commentedI am having the same problem, and would appreciate someone looking into it. I can't believe that it is a problem with the core Drupal system. The tokens that are described in the Action configuration are passed directly through (i.e., the e-mail that is sent includes the token variable names in the body of the e-mail, exactly as they are written).
I am not a programmer in any sense, but I am somewhat tech savvy. My first thought is that the contents of the Subject and Body are passed into/through the SMTP module as strings/literals, rather than being (pre)processed for tokens.
If anyone has any input on why this could be happening, or how to work around it, I would be greatly appreciative.
Comment #5
simon georges commentedThere currently is no patch, so setting status to "active".
Comment #6
franzjairgee, that's very unlikely. The SMTP module only inserts itself on the process of sending (drupal_mail_wrapper). The "tokenization" happens inside hook_mail implementations (you can read about it on the Drupal API). By the way, one of the tokens on the issue description is misspelled.
Comment #7
wundo commentedClosing very old (dead) issues, if you think this is still relevant please re-open.