SYSTEM WARNING: 'date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.' in '/usr/share/mantis/www/core.php' line 264

0004557: Invalid data goes from web-GUI to mail-relay config files - MantisBT
MantisBT - Endian Firewall
View Issue Details
0004557Endian FirewallProxy - SMTPpublic2013-07-28 19:382014-04-30 15:36
0004557: Invalid data goes from web-GUI to mail-relay config files
If SMTP proxy has to relay e-mails to a different mailserver and that server listens on a non-standard SMTP port, then you must enter the port number after the destination host in the Postfix config files in this format: [x.x.x.x]:xxxxx
If IP-address and port number is entered in this format to the "Mailserver IP" text-box at "Proxy > SMTP > Incoming domains > Add a domain" page, then config files (etc/postfix/transport and /etc/postfix/relay_domains) will have this invalid format: [[x.x.x.x]:xxxxx]
This makes Postfix unable to relay e-mails to the destination host. Manual correction of config files must be done after every apply or restart.
1.) Open EFW web-GUI.
2.) Go to "Proxy > SMTP > Incoming domains > Add a domain" page.
3.) Enter an incoming domain and a Mailserver IP with non-standard SMTP port, for example: []:2525
4.) Click on Add button.
5.) After adding incoming domain, check these Postifx config files: etc/postfix/transport and /etc/postfix/relay_domains
6.) SMTP destination host is in invalid format: [[]:2525]
7.) Postfix can not use invalid format to relay e-mails.
No tags attached.
Issue History
2013-07-28 19:38JackDNew Issue
2013-08-26 08:37luca-endianAssigned To => luca-endian
2013-08-26 08:37luca-endianStatusnew => acknowledged
2014-04-30 15:35AnonymousStatusacknowledged => resolved
2014-04-30 15:35AnonymousResolutionopen => fixed
2014-04-30 15:36AnonymousStatusresolved => closed

There are no notes attached to this issue.