I wanted to share my latest observation with everyonehi kyleI have been thinking about the problemThe problem stems from the fact that smarteremail considers messages arriving from external emails differently than those present on the server.I try to explain myself better with an exampleSuppose I have a xtest.com domain on my sm serverwith an email email@example.com configuredNow, an email arrives from firstname.lastname@example.org, antispam, spf, dkim etc. is applied. etc.Instead, an email arrives from an external ip: xx.xx.xx.xx which has as sender email@example.com recipient firstname.lastname@example.org or any other email on the serversm in the basic configuration asks the user for authentication. If I disable the auth for local users it creates a security problemIn my opinion it should behave the same way as it does if the email is not on the serverThat is to apply the rules of antispam and so on normally, in particular the spfAnd so if the score is high it ends up in spamIn this way I can safely put the client's web server IP in the SPF, because it does not create a security problem
Trouble logging in? Simply enter your email address OR username in order to reset your password.
For faster and more reliable delivery, add email@example.com to your trusted senders list in your email software.