XF 2.2 Integrating into email mailer

[stromb0li]

Is there a way I can extend the mailer so when an email is sent by XenForo for any purpose (either before or after) for any purpose (i.e. password reset, watched thread, DM, activity summary, etc) I can access properties of the message (particularly, the subject).

 

[Sim]

Do a class extension on \XF\Mail\Mail and then over-ride the setContent function.

 

[stromb0li]

Thank you! I ended up extending queue to try and get closer to the actual sending of the message and that seems to have done the trick!

Cheers!

 

[Sim]

Just be aware that not every message gets sent via the mail queue - some are sent directly.

 

[stromb0li]

Appreciate the heads up!

This is the add-on I was working on for context: https://xenforo.com/community/resources/email-log.9418/

It's open source, so if you have thoughts on the approach with more context, would love if you had a few mins to PR a change

 

[stromb0li]

Sorry for double post, but you are exactly correct, I'm starting to see which methods send mail directly; password reset being one of them. When extending the class for setContent, how do execute my setContent method after setContent happens? I'd prefer to not copy the code out of the Mail.php file into the setContent method of my class, then add the few lines I need thereafter.

 

[Jeremy P]

Just call the parent first.

public function setContent($subject, $htmlBody, $textBody = null): Mail
{
    $mail = parent::setContent($subject, $htmlBody, $textBody);

    // ... whatever you need to do

    return $mail;
}

 

[stromb0li]

Just call the parent first.

public function setContent($subject, $htmlBody, $textBody = null): Mail
{
    $mail = parent::setContent($subject, $htmlBody, $textBody);

    // ... whatever you need to do

    return $mail;
}

Just gave this a go, but it ends up causing an infinite loop since it triggers itself when calling the parent

 

[Jeremy P]

You’d have to post the full approach you’re using, calling a parent method won’t result in an infinite loop. Virtually all method extensions in every add-on call the parent method (it’s important to do so for add-on interoperability).

 

[stromb0li]

Nevermind, this was user error on my part.