Project

General

Profile

Actions

Bug #22129

closed

Non-RFC-conformant email adresses

Added by Jan Loderhose almost 15 years ago. Updated over 13 years ago.

Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2010-02-17
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.3
PHP Version:
5.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

"LoginWarnings" send by the TYPO3 Backend are send from email address "no_reply@no_reply.no_reply". This is a hard coded value and non-conformant to official standards. RFC 2606 - Reserved Top Level DNS Names [1] names ".invalid" as TLD "intended for use in online construction of domain names that are sure to be invalid and which it is obvious at a glance are invalid."

The currently used from address may cause problems (bounces, blacklisting of server etc) with picky mail servers and they were right, one may say. Hardcoding this value makes manual changes of this value unreasonable since every update resets the email adresses.

To keep TYPO3 a sustainable CMS I propose the following changes in the core:
Move the from address of warning mails to $TYPO3_CONF_VARS. Default value is the RFC-conformant from address . The address is customizable by the TYPO3 administrator. Blanking the value triggers the use of the postmaster address defined by the web server configuration if applicable.

[1] http://www.faqs.org/rfcs/rfc2606.html

Define [BE][warning_email_addr] and [BE][warning_mode].
Log into your system.

(issue imported from #M13560)


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Feature #22447: When sending mail, use TYPO3_CONF_VAR for default from address if no other address is providedClosedJeff Segars2010-04-14

Actions
Related to TYPO3 Core - Bug #19365: Make "t3lib_beUserAuth->notifyHeader" configurableRejected2008-09-22

Actions
Actions

Also available in: Atom PDF