[TYPO3-core] RFC #9407: Bug: Make "t3lib_beUserAuth->notifyHeader" configurable

[Thorben Kapp]

Hi,

I wasn't really sure about the default value but I thought the email 
header is only used for this notification and warning feature at the be 
login. So I decided to set the default value to the currently used 
"no_reply" and if one would like to use this feature it must be 
configured properly.

A basic domain would be an idea but this email is already at the base of 
configuration. Where would you configure the domain to use here. Besides 
that value is not only a domain, it can contain the full mail header so 
it should be fully configurable, I think.

By the way, I noticed the problem with the email because a customer uses 
this feature and our mail server rejected the mail because of the 
senders address. So it is only a problem when using this feature and the 
default value should not cause a problem here.


Thorben



On 10/01/2010 10:36 AM, Markus Klein wrote:
> Hi.
>
> Basically a good idea, but I'm not really comfortable with the default
> value.
> Since the receiving server will not be able to resolve the sender's domain
> name, it's likely that all these mails will be marked as spam.
>
> I'd be cool if we could introduce a kind of default sender address used
> throughout the whole core then. This address should be configurable. A
> possible default value could be something like webmaster@<real domain>. I'm
> not quite sure where this<real domain>  should be defined, since this
> applies to BE and FE.
>
> Regards
> Markus
>
>> -----Original Message-----
>> From: typo3-team-core-bounces at lists.typo3.org [mailto:typo3-team-core-
>> bounces at lists.typo3.org] On Behalf Of Thorben Kapp
>> Sent: Friday, October 01, 2010 10:25 AM
>> To: typo3-team-core at lists.typo3.org
>> Subject: [TYPO3-core] RFC #9407: Bug: Make "t3lib_beUserAuth-
>>> notifyHeader" configurable
>>
>> This is an SVN patch request.
>>
>> Type: Bugfix
>>
>> Bugtracker reference: http://bugs.typo3.org/view.php?id=9407
>>
>> Branches: TYPO3_4-3, TYPO3_4-4, trunk
>>
>> Problem: t3lib_beUserAuth->notifyHeader is hardcoded to 'From: TYPO3
>> Login notify<no_reply at no_reply.no_reply>' in class.t3lib_beuserauth.php,
>> line 85.
>>
>> Solution: Make it configurable
>>
>> Notes: To test this enter your email address in the user settings of your
> be
>> user account and activate the check box "Notify me by email, when
>> somebody logs in from my account". Configure the email header via install
>> tool. Log out and log in again to receive the mail.
>>
>>
>> Thorben
>