View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0025619||mantisbt||custom fields||public||2019-03-18 11:40||2021-01-11 17:26|
|Summary||0025619: $g_limit_email_domains impacts custom e-mail fields, which is unexpected from its documentation|
The Admin Guide here:
"$g_limit_email_domains - Only allow and send email to addresses in the given domain(s). This is useful as a security feature and it is also useful in cases like Sourceforge where its servers are only limited to send emails to SourceForge email addresses in order to avoid spam. $g_limit_e- mail_domains = array( 'users.sourceforge.net', 'sourceforge.net' );"
After setting this to:
$g_limit_email_domains = array( 'rogue-research.com' );
I am no longer able to edit issues that use a 'custom field' of 'e-mail' type, mantis will report:
APPLICATION ERROR 0001303
My customers of course don't have emails in my own domain. :)
From its documentation, I wouldn't have expected that $g_limit_email_domains limit what can go into database fields, but only to limit emails that mantis actually sends out.
|Tags||No tags attached.|
Hmmm, I just tried in Mantis 2.23.0 on a test server, and don't seem to reproduce it anymore...
Did someone fix this?
I'll try again on my production server once I update it too...
I don't think this has been touched. Maybe it was caused by your setup. Please let us know after checking, whether the problem is indeed fixed, so we can resolve this issue.
I've finally tried on my production server (now 2.23.0), and this bug does reproduce.
What logs or steps would be helpful to debug this?
So I just searched the Mantis codebase, and find:
So indeed the behaviour I'm seeing does indeed seem to be what the code is doing, and indeed does not match the documentation.
Question is: which is wrong, the code or the docs?
Personally, I'd say the code is buggy. I'd like to constrain my server from sending email outside my company, but that doesn't mean I want to forbid custom database fields from using external email addresses.
Behavior was introduced in 1.2.1 when implementing 0011610