With DASP, our users were able to send email as if it came from their own domains, even though we used localhost as the smtp hostname internally. We just set the From/ReplyTo to their addresses and send away. 1. With Everleap, we're now using sm14.internetmailserver.net and NetworkCredentials. Are we risking our domain getting blacklisted by doing this (different domain outbound from our mail server)? 2. We could start storing clients' own SMTP hostnames and credentials in our db and use those for their own outbound emails from our application. Does anyone foresee any issues with that approach? I mean, their smtp servers blocking a send from with the Everleap environment since multi-domain emails would be originating from our domain? I suspect either options above would work since email clients are many and send emails from various environments as long as the credentials are ok. Having said that, 3. I couldn't send email when running from my local machine running on IIS as localhost. I still used Everleap's sm14 mailserver and credentials. Send mail code worked when moved from my local env to EL. Anyone have any comments/experience/advice on the above 3 items? Thanks in advance!