- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2FA via E-Mail does not work after upgrading Fortigate 100F from 7.4.0 to 7.4.4
Dear Fortinet Community.
We have upgraded our Fortiagte 100F from version 7.4.0 to 7.4.4. After that it seems so that users which we have defined to get mails for 2FA when connecting to SSL VPN will not receive emails with the 2FA code anymore. Other emails for triggers for instance still work. So it does not seem to be a mail account issue. But the emails with the 2FA code will not be sent anymore. I have created a testuser in order to check it. Mails will not received and they are not in SPAM or Quarantine or so.
Does anyone of you have ever experieced this? Or probably know a solution for this circumstance?
Any answer or hint is much appreciated.
With kindest Regards
FortiLover :)
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You have probably run into this unfortunate change:
There are no "nice" solutions to this, as far as I am aware, just what is mentioned in the article.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Now there is a solution. Installing a newer version (7.4.5) is the solution for us.
The article from @pminarik has been updated. Here are to solutions mentioned in the article.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Are you using a custom SMTP server or the default one from Fortinet, to send the emails?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I use a custom one. And it seems so that this SMTP Server works fine as the normal emails from the fortigate will received. With normal emails I mean emails I use for triggers. So emailing normaly works and it is just not working after the update for 2FA E-Mail codes. I can see that it worked before the update from 7.4.0 to 7.4.4
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You have probably run into this unfortunate change:
There are no "nice" solutions to this, as far as I am aware, just what is mentioned in the article.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dear @pminarik
Thats it. You are a genius! I think thats it. For me it is a bug in the current version so we think about a rollback. Let's see. i need t think about it... probably sleep one or two nights about it and try to find a good decision. Thank you very much again! This is very very helpful man!!! Thank you!!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I agree with you, a static reply-to should not be enforced onto custom servers.
For the default Fortinet one sure, makes sense there, for others definitely not.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Now there is a solution. Installing a newer version (7.4.5) is the solution for us.
The article from @pminarik has been updated. Here are to solutions mentioned in the article.
![](/skins/images/314F488D15A2016126B094729A0E57E8/responsive_peak/images/icon_anonymous_message.png)