Add message about rerouting before send

Indranil Roy → made their first commit to this issue’s fork.

Hi, I am currently working on this feature.

Hi,
thanks a lot for your interest in this feature.
Please feel free to share here your progress.
Happy to contribute

Hi @afagioli
Sorry right now i am stuck in some other issue so i cant work on this issue right now

Indranil Roy → closed merge request !64

Merge request 64 read.

What about adding rerouting address $config->get("address") to message?

It would something be like:

$this->t( "Reroute_email module is <b>enabled</b>, rerouting is <b>enabled</b>. Every mails sent from by this website will be delivered to %dest", ["%dest" =>  $config->get("address") ] );

Indranil Roy → closed merge request !65

Hi @afagioli, @Gaurav Gupta, @Indranil Roy,
thanks for your contribution and interest in the module!

Honestly, it can be a bit weird and annoying for developers, content managers, and others while browsing the site (if such a status message is literally on every page).

From my experience, it is even better to configure a module like this:
https://www.drupal.org/project/environment_indicator →
So everyone can clearly understand which instance is on (like dev, staging, or prod).

Otherwise, if such status messages are still needed, this might be considered a project-related request (not a contrib module feature).

Also, please be aware that the status of the rerouting is always available on the status report page (/admin/reports/status).

Hopefully, you will find this message helpful!

Honestly, it can be a bit weird and annoying for developers...

​
@bohart, acknowledging the utmost understanding for your personal opinion, I must point out that the need for this issue confirms the exact opposite.

It is also worth to say this issue is not addressed to the coder, but to the UI designer with a wider view of the use case. I'm not sure content manager I work with will ever see that message. Not our use case.

The issue is thus confirmed.

Thanks to the whole module team for facing this issue though.
​

Feature in subject is now part of reroute email BE →