For delivery of e-invoices via APR or some other method (10.2.500 seems to have a built in set of controls for this, but probably uses the same underling mechanisms), the SMTP server/port/account used is the one defined in the Company configuration. This SMTP is also used for any other mail sent out of Epicor, such as BPMs.
Currently, I use a local SMTP that we set up in the networked environment. This allows lots of flexibility for account impersonation (i.e. who is the “from” address) and has no real limits on how many emails can be sent. This mostly works well for e-invoices, but fails to excel at delivery when the recipient conforms to higher levels of email filtering (think of hospital IT systems). Many of our customers are simply blocking any non-trusted sources of emails, so the natural thought is to use a email API rather than attempting to have our local server white listed.
I have also tried using an Office 365 account configuration, but I see several glaring downsides that I hope others can speak to their experience.
For starters, there is an API limit on email from a 365 account to 30 emails/minute. Haven’t tested this, but a simple daily batch of invoices being sent via APR would exhaust this API limit as I image the tasks are all submitted to the O365 API at once…
Secondly, O365 allows for “send as” type permissions, but this requires additional configuration within O365. Given the need to configure this at the company level, it also becomes problematic for any BPM/system emails that do not conform to the strict sender permissions required by O365.
I have looked into Gmail API as well, but it’s the same set of issues with even more API limits.
What are others using for this?