Plugin yìí kò tíì ṣe àyẹ̀wò pẹ̀lú àwọn ìtújáde mẹ́ta pàtàkì tó kẹ́yìn ti WordPress. Ó lè jẹ́ pé a kò tọ́jú tàbí ṣe àtìlẹ́yìn fún un mọ́, ó sì lè ní àwọn ọ̀ràn ìbámu nígbà tí a bá lò ó pẹ̀lú àwọn ẹ̀yà WordPress tuntun.

HW Override Default Sender

Àpèjúwe

Overrides WordPress default e-mail sender information (WordPress wordpress@yourdomain.com) including Reply-Path with information you provided. The default e-mail sender information is typically used for WordPress standard e-mails like “new user registration” and similar e-mails.

For standard WordPress installation this plugin will use the Sitename and admin e-mail address provided in the general settings. For multi-network installations it will use network name and e-mail address provided in the network admin general settings.

For more info, visit http://webartisan.se/hw-override-default-sender/

Ìgbéwọlẹ̀

Use standard installation process for a plug-in:

  1. Install HW Override Default E-mail either via the WordPress.org plugin directory, or by uploading the files to your server.
  2. Activate the plugin through the ‘Plugins’ menu in WordPress.

FAQ

Will it override all e-mails?

No. It will only intervene if it detects that the e-mail about to be sent has the WordPress default sender information. It means that existing plugins, filters or in other way specified e-mail sender information will be untouched and still work as expected.

What about Reply-Path?

It will always override the Reply-Path header if not prohibited by your server configuration. It will do so by setting the Reply-Path e-mail address to the same address as the From value.

Àwọn àgbéyẹ̀wò

Kò sí àwọn àgbéyẹ̀wò fún plugin yìí.

Àwọn Olùkópa & Olùgbéejáde

“HW Override Default Sender” jẹ́ ètò ìṣàmúlò orísun ṣíṣí sílẹ̀. Àwọn ènìyàn wọ̀nyí ti ṣe ìkópa sí plugin yìí.

Àwọn Olùkópa

Túmọ̀ “HW Override Default Sender” sí èdè rẹ.

Ṣe o nífẹ̀ẹ́ sí ìdàgbàsókè?

Ṣàwárí koodu, ṣàyẹ̀wò ibi ìpamọ́ SVN, tàbí ṣe àgbékalẹ̀ sí àkọsílẹ̀ ìdàgbàsókè nípasẹ̀ RSS.

Àkọsílẹ̀ àwọn àyípadà

1.0

  • First version. Why go beta?