Joe, as far as I know Google has changed its security activities in April. Especially attached pictures will be blocked/rejected.

If you send a mail via WebAccess and add a jpeg into your mail body or if  your signature contains a jpeg logo, then this information will be transformed into an image file (img) which will be blocked by Google mail. However if you attach a jpeg to your mail, then this file stays jpeg and Gmail does not block.

If I do the same tests with GW18.4 web or Windows client, then embedded jpegs stay jpegs and jpeg logos in your signature do not cause problems. All mails will be accepted at Google.

WebAccess will be not changed or enhanced because it is out of support. I fear the same for GW18.0 ...

So this is my experience from several environments

Hi Diethmar,

WebAccess for 18.4 will not be fixed?  This issue is caused by our users making signatures with inline images pasted in a "weird" way.  I can't go back and fix 2 million  messages that were made wrong.

Every time our users try to forward one of these "bad" messages the mail is blocked and the users do not report the failure for over a month.

I am not sure what can be done to fix the issue, I know we can fix it going forward.

Thanks,

Joe

JoeAtWork said:

WebAccess for 18.4 will not be fixed?

correct, there is no WebAccess beyond 18.2 as that component is end of life,   with the replacement being GW Web client that is docker based so no more messing with Tomcat and related issues.  So the fix is for you to upgrade your system and implement the GW Web client as a replacement of old WebAccess (I came across a very early version on CD today from about 25 years ago)

That is awesome news KonecnyA!

Will this new product will fix the issue with gsmtp or do our users need to re-create their signatures?

GWWeb does not appear to have this problem and doesn't require the recreation of the sigs as far as I am aware of.

I agree to Andy, the new web client does not have a problem with "old" signatures ...

In the beginning the new web client was too weak to replace WebAccess. But now I see that customers are satisfied and like the new client (I know there is still space for improvement ...).

How about attached messages that from a year ago that are forwarded as an attachment. 

I am dealing with this now as there is a customer and two of our employees that send multiple emails to them and now the supervisor has all three message chains she is forwarding as html messages.  Today with the full client this too is failing with the gsmtp error. :-(

I assume that WebAccess "prepares" (renders) mails in a very special way. So if your GroupWise windows client takes these mails and forward them, mails will not be changed (re-rendered). So mails containing image files will stay without changes. If your Windows clients forwards those mails to GMail, they will contain image files and will be blocked. But the original cause is WebAccess! Independent of age ...

This is my assumption - I did not check or prove it ...

We have just started to notice this issue, since we no longer relay our mail to a third party and send directly out from our gwia.

Anything that has some sort of image in the signature  will get rejected by gmail with this error. I was able to send the same email to outlook with no issues.

  Response: 552 5.7.0 message content and attachment content guidelines. u15-20020a05622a14cf00b003b82e71264asi4488581qtx.401 - gsmtp

We are running GW 18.4.1 build 140419 and my client is 141027 (not using the web client). What is a workaround to this? Getting all users to change their signatures?? 

I would not recommend having the GroupWise GWIA SMTP gateway talk directly outbound on the Internet.  The GWIA gateway does not implement all the new requirements for Outbound SMTP handshaking.  You must use an upstream SMTP service to do the outbound DKIM, SPF, ADSP, DMARC, etc handshakes that the GWIA cannot do.