We had complaints from partner that the confirmation emails from the
site appeared to be from 'belgium-reps', say, in your mail client if
the email was From: belgium-reps@example.com
To address this problem, this commit adds an instance configuration
setting for the real name that should be used in the From: line of
confirmation emails and answer notification emails. (This can be
any unicode string, and it will be encoded sensibly by Django's
smtp backend.)
Coverage increased (+0.007%) to 98.087% when pulling cff740c9e76fe2382a015b8d0ae7867419e83449 on customize-from-real-name into da7d97cad89a80587e4ff4ca7d957bb505a0b684 on alpaca.
Coverage increased (+0.007%) to 98.087% when pulling cff740c9e76fe2382a015b8d0ae7867419e83449 on customize-from-real-name into da7d97cad89a80587e4ff4ca7d957bb505a0b684 on alpaca.
Coverage increased (+0.007%) to 98.087% when pulling e1d6175f03da09c756e92e4a142cb96ea005c19d on customize-from-real-name into da7d97cad89a80587e4ff4ca7d957bb505a0b684 on alpaca.
We had complaints from partner that the confirmation emails from the site appeared to be from 'belgium-reps', say, in your mail client if the email was From: belgium-reps@example.com
To address this problem, this commit adds an instance configuration setting for the real name that should be used in the From: line of confirmation emails and answer notification emails. (This can be any unicode string, and it will be encoded sensibly by Django's smtp backend.)