Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 29 subscribers
  • Views 3613 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SMTP PROXY broken after firmware migration from SFOS 17.1.4 MR-4 to SFOS 17.5.4 MR-4-1

CloudManager

Yesterday we upgraded an XG running on Microsoft Azure from SFOS 17.1.4 MR-4 to SFOS 17.5.4 MR-4-1.

The upgrade appeared to progress normally, however it was observed that outbound mail was not working upon completion.  The instance is not licensed for EMAIL, and uses the proxy to deliver mail to an external MTA.

The EXIM configuration file located at;

SFV2C4_AZ01_SFOS 17.5.4 MR-4-1# cat /cfs/proxy/smtp/conf/exim_macro.conf

Had a CRLF inserted into the user password which in this case was a long API KEY.  We found it would work again if a shorter password was entered via web admin.  Unfortunately this is not a work around for us as the external mail provider requires with use of the API key to authenticate.

If you are considering upgrading to SFOS 17.5.4 MR-4-1 you may want to check this is not going to be an issue before upgrading.

We have an open case #8762920 for this issue.  Awaiting escalation.

 

 

 



This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to Aditya Patel

    So far escalation has not reached a person with appropriate level of competency to deploy a work around or a fix.

  • 0 in reply to Aditya Patel

    Hello Aditya,

    Is there a projected release version that will include a fix for this? Continuous failed authentications to my external mail server have resulted in my IP address being greylisted. My mail server provider has whitelisted my IP, but they are only will to do this a week at a time.

    I've had to roll back to the previous version to avoid being greylisted again.

    Alternatively, can you provide parameters for a password that won't be corrupted in the exim config file?

    Kind regards,

    Jonathan

  • 0 in reply to J_87586

    Your reported issue is identify as bug and reference id for the same is NC-46145.

    Development reference number:

    NC-46145

    Current Status:

    Assigned to release

    Issue type:

    Defect


    Your issue with the above reference number has been assigned to a release. 

    Current plans are to include this fix as part of SF 17.5 MR6. Currently the release is planned to be released towards the end of May 2019

  • 0 in reply to CloudManager

    We installed SFOS v17.5.6 MR6 and the bug appears to be fixed. We consider this issue resolved.