Yup. That's exactly what my client said as well. It's Sage 100's fault! Below is what my client's IT people told me they did. Oddly enough the fix was in active directory (which I assume must somehow link to the Exchange server?). I'm not a real expert on Exchange server. "the only thing I did was lookup in the administrators account in active directory what email addresses were aliases of administrator@xxxxxx-inc.com and mas200@xxxxxxxx-inc.com was listed as one. I deleted it from the administrator account as an alias and moved it to the AR account as an alias and everything started working." In the above, MAS200 was a generic e-mail account. AR@xxxxxx-inc.com was an e-mail set up to be the return address for S/O invoices. When the e-mails sent to their customers they were getting mas200@xxxx-inc.com. E-mails sent back to my client as copies ended up saying postmaster or administrator@xxxxx-inc.com. I can't say that I truly understand it, but that's what worked for them.
↧