It looks like putting in a destination smtp email address in the Terastation Pro II for email notifications causes the source smtp address for these messages to be the same as the recipient address. Since my email filters block receiving messages that appear to be from myself, this causes a block on notification messages from these Terastations.
For example, if you send notifications to billybob@domain.com, the source smtp address on these notification messages also shows up also as "billybob@domain.com"!
Every other device or piece of software that I have ever used (in 20 years in IT) that allows email notifications offers a "send from" source smtp address configurable option as well as a "send to" address option. This only makes sense to me, (to have the sender's address be different from the recipient's address) but appears to be missing from the Terastation Pro II options. There does not appear to be any mention of this behavior in the manual either.
Is there any way to have the source smtp address be customizable, so that it could be "terastation-pro-II-51@domain.com", or some such?
Thanks for your thoughts.
It doesn't appear to be an option, as you've said. I'll forward this feature request to our corporate office.
same issue with my new 4TB Terastation, retiring soon, need to have emails "from" some more descriptive name, not the user who created the notification elements. any update to this subject?
I'm bumping this zombie thread to see if this was ever resolved? Trying to set up email alerting on a customers NAS to my ticketing system, which requires a particular email address to be received from.
Now that I have backups set up, I may have to return the NAS and buy another NAS that supports typing a from email address..
Wow srs zombie thread.
You just log into the server as whomever you want the email to be sent from? I'm not so sure that customizing who the email is from is a standard feature on most NAS devices. I looked at a few other units' interfaces and this appears to be pretty standard stuff.
(http://i66.tinypic.com/2is9qno.jpg)
Eastmarch:
Regarding your comment "I'm not so sure that customizing who the email is from is a standard feature on most NAS devices." intrigues me.
Every other device I have in my shop allows me to set the source email address, except the TeraStation. Whether a swtich, SAN or a NAS device, all of them allow me to set the "From" address.
The inability to do that on the TeraStation causes email notifications to be caught in our spam filter because I'm sending an email to myself. I can't believe this is still not resolved.
Quote from: Dorroc99 on July 18, 2016, 10:44:16 AM
Every other device I have in my shop allows me to set the source email address, except the TeraStation. Whether a swtich, SAN or a NAS device, all of them allow me to set the "From" address.
Not true, same with Synolgoy and QNAP.
Well, regardless, the TS5000 Firmware 3.41 that released yesterday added this functionality. So hooray!
Browser ID: smf
(is_webkit)
Templates: 1:
Printpage (default).
Sub templates: 4:
init,
print_above,
main,
print_below.
Language files: 1:
index+Modifications.english (default).
Style sheets: 0:
.
Hooks called: 80 (
showintegrate_autoload, integrate_pre_load, integrate_load_session, integrate_verify_user, integrate_pre_load_theme, integrate_user_info, integrate_load_board, integrate_board_info, integrate_pre_load_theme, integrate_allowed_to_general, integrate_simple_actions, integrate_allowed_to_general, integrate_load_theme, integrate_pre_log_stats, integrate_actions, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_codes, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_pre_parsebbc, integrate_smileys, integrate_smileys, integrate_post_parsebbc, integrate_pre_parsebbc, integrate_smileys, integrate_smileys, integrate_post_parsebbc, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_menu_buttons, integrate_current_action, integrate_theme_context, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general)
Files included: 27 - 1055KB. (
show./index.php, ./Settings.php, (Cache)/db_last_error.php, (Sources)/QueryString.php, (Sources)/Subs.php, (Sources)/Subs-Auth.php, (Sources)/Errors.php, (Sources)/Load.php, (Sources)/Security.php, (Sources)/Subs-Compat.php, (Sources)/Subs-Db-mysql.php, (Sources)/Cache/CacheApi.php, (Sources)/Cache/CacheApiInterface.php, (Sources)/StopForumSpam.php, (Sources)/Subs-Charset.php, (Sources)/Unicode/Metadata.php, (Sources)/Unicode/QuickCheck.php, (Sources)/Session.php, (Sources)/Logging.php, (Sources)/Class-BrowserDetect.php, (Sources)/Unicode/RegularExpressions.php, (Sources)/Unicode/CaseUpper.php, (Sources)/Unicode/CaseTitle.php, (Current Theme)/languages/index.english.php, (Current Theme)/languages/Modifications.english.php, (Sources)/Printpage.php, (Current Theme)/Printpage.template.php)
Memory used: 734KB.
Tokens:
post-login.
Queries used: 10.
[Show Queries]