Sage 100

I've got a client that is having issues with paperless office generated email getting rejected spam filters for a large number of customers. This started happening a several weeks ago with just a couple of customers; then more and more customer's are rejecting them every week. they have more than 60 customers now that are rejecting the emails sent from Sage100. They have kept a list and manually send the same invoice PDF file with the same subject line, same sender, and same body of the email. the manually sent one goes through just fine. their IT staff can't seem to help; and since the email is sent fine through exchange (I think they use exchange), I'm not sure what else to try. We have tried changing the body and subject line on the email that did not help. Does anyone have any similar experience with this or thoughts on what to do next?

I have had the IT department increase the limits in Exchange, especially the recipient and sender limits and that resolved the issue.

Hello David, many possible causes here. Are they using simple SMTP relay via Exchange connector or are you authenticating? The ""Email"" tab in Company Maintenance should tell you. If using authentication, are the Sender that is setup in Forms Maintenance and the account being used to authenticate the same account? Are they same domain? This could be reverse DNS issue by recipient SPAM filters if answer to 3rd question = no. It's **not** likely it is a domain blacklist issue (can happen if any user on sender's domain is infected with SPAM malware, they can be without knowing it), otherwise the 2nd attempts would be getting caught too. It may be in house filter system if sending in pretty large volume. If they have a filter they're using in house, may need to add the Sender setup in 100 as ""Bulk Sender"" or other such term. Have seen this before too. Hope this helps.

There are a number of spam lists for them to check and get removed from. It can be associated to an IP address

https://www.smtp2go.com

@NicoleRonchetti suggested SMTP2GO on another thread. It worked for our customer having the same issue

ok,The authentication user name and the ""sender"" user name were different; so, I sent the screen shot of the email setup to their IT. They are suggesting we take the user name and domain out since they don't require authentication.

the SMTP encryption is set to TLS/STARTTLS any problem with that?

If using simple relay without authentication SMTP encryption is not being used. TLS / STARTTLS is only used with authenticated communication. Not looking at selection, but believe there is None or something similar. That's what you want to use if able to relay.

Also, if change and test fails let IT know they'll need to setup a connector on Exchange to allow relays from the IP or subnet on which the server / workstations reside. If using Advanced then it can be the server IP, if Standard use the subnet the workstations are on as they actually do the processing with Standard and those IPs are what's seen on Exchange side.

On a tangential note, we are seeing lots of issues with the version of TLS being used as many service providers are phasing out TLS 1.0 and requiring TLS 1.2...

Every time email stops working or won't start for us, it has been a matter of the exchange server not explicitly trusting the Sage 100 box.

As an update, we are still fighting with this, the emails send out from Exchange just fine. but our client's customers don't get them because they are being bounced as unacceptable/spam emails. I tried telling the client that there is not much I can do in Sage once they leave exchange, but their answer was they can basically send the exact same email manually and it doesn't get rejected so it must be something in Sage causing it to get rejected. I can't really argue that point.

Ohh, if it's at all like Act, there has to be a (SSL?) certificate on the sender's server that says it's trusted in order for certain bulk emails to be accepted by email servers. I'm in way over my head here, but when I do eblasts, we had to make one of these certs to increase my ""delivereds."" I'm grasping.

I am far from an expert so take this FWIW - I think Sage sends via SMTP and you may have to authenticate the smtp email differently than Exchange? This talks about Gmail authentication but similar concept (I think) https://support.google.com/mail/answer/180707?co=GENIE.Platform%3DAndroid&hl=en

David, per you last comments above when the client sends ""exact same email manually"" how are they doing this? Are they using PL again via the Viewer resend function, or are they using their local email client to send from personal account as attachment? Leading to... is the sender the same? It is either with the sender or somehow the bulk operation is being flagged as such. The good news is it doesn't seem to be a domain level blacklist issue. Since mentioning customers, I am assuming we're talking about AR and / or SO invoices / orders, correct? If so, then another assumption is we're talking about multiple customers with various filtering systems which makes it more complicated to figure out cause. In case of DD stubs, have seen bulk get flagged which dictates sender needing to be added as approved bulk sender because so many are being sent to same domain (usually internal). That doesn't seem to be the issue here. Always a puzzle.

@AndyAdkisson - We are talking about S/O Invoices. it is multiple customers, and my customers IT is trying to find out if there is any commonality between all these customers. When they send it manually they have been opening outlook and attaching a PDF of the invoice. I learned yesterday that they were scanning a printed copy of the invoice and attaching that copy instead of attaching the PDF created by Sage. I asked them to try attaching the PDF that was created during invoice printing. I didn't really think that would make a difference, but I'm glad I had them try. She just emailed me this morning that when she attached the Sage PDF to an email directly from outlook, when she hit send, outlook popped up a warning that ""Microsoft may not be able to open the attached file"" She sent me copy of that PDF and I could open it just fine. I asked her to send me a screen shot of the exact popup. maybe we are actually on to something here!

Sounds like it. Like AV, most SPAM filtering systems are frequently updated (automated) with new detection mechanisms / algorithms. Something common is getting flagged whether that's sender, filename format, subject line, something. Hope you get it figured out.

here is the message she got once; however we have not yet confirmed that this happens due to the Sage created PDF. She got the message once but has tried sending more several times (same PDF and others) and she has not gotten the message again. (sigh)

This looks like a recent issue per update from Microsoft. If it's what is being talked about in thread link, then suspect it's getting flagged at individual Outlook recipient level rather than corporate SPAM level. Likely another auto-update will later correct if that's the case. See link... https://social.technet.microsoft.com/Forums/office/en-US/94f10c8d-6c1e-4fce-a3c2-644da20d7b2a/this-item-contains-attachments-that-are-potentially-unsafe-recipients-using-microsoft-outlook-may?forum=outlook

From discussion link... ""For what it's worth, the issue seems to be with the length of the filename. I haven't done extensive testing to determine what the cutoff is, but an 89 character file name does trigger the warning while a 10 character filename does not. If you have a long filename, try shortening it to see if that makes a difference.