It's a good idea to keep a logical separation between the sending MTA and the receiving MTA (separate hostnames at the least, separate machines/instances is best because you can manage security policy better).
Do plan on keeping the SMTP operations separate from the web application, and if your application is going to read email, plan on building spamfiltering in from the beginning.
It's more about maintaining separation of concerns, back in the late '90s I dealt with a web app that was written as one massive perl CGI that was called from the webserver and from the web users .forward; it was ugly, buggy and if you added the right headers to your email you could do sql injections.
Run the mailreader as a separate user, have it talk to the data layer on it's own, basic informational hygiene.
It's a good idea to keep a logical separation between the sending MTA and the receiving MTA (separate hostnames at the least, separate machines/instances is best because you can manage security policy better).
Do plan on keeping the SMTP operations separate from the web application, and if your application is going to read email, plan on building spamfiltering in from the beginning.