Recipients getting "You may need a MIME compliant mail"?

Support General Configuration
1

Suddenly some of my recipients are getting encoded emails that they can’t read. Looks like Axigen is sending MIME encoded emails that the recipients cant decode? They are using Google GMAIL webmail clients and Yahoo webmail clients and Office 365 webmail clients. What is going on here?

This is a MIME message. You may need a MIME compliant mail user agent.
–===axigen=1234772200948186997632206918375499813496=axigen===
Content-Transfer-Encoding: quoted-printable

–===axigen=1234772200948186997632206918375499813496=axigen===
Content-Type: multipart/alternative;

boundary=“===axigen=9424783733965445700375118879119527346766=axigen===”

This is a MIME message. You may need a MIME compliant mail user agent.
–===axigen=9424783733965445700375118879119527346766=axigen===
Content-Type: text/plain;
charset=“utf-8”
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

2

Please mention your axigen version and OS and mail client (X-Mailer).
if you are using webmail please tell me whats your browser version.

3

Mail client: I am sending mail from the Axigen Webmail portal.
Axigen server version: 10.2.2.35
Webmail version: 10.2.2

4

Same problem here, running latest Version 10.2.2.75.0

Mails composed using the Axigen Webmail in HTML are not displayed on major webmail portals or even blocked by some Mailserver, most likely because of „wrong“ MIME encoding.

Plaintext message work without problem with the same receipients when composed as plaintext on the Axigen Webmail.

Any update/workarounds on this issue?

Edit: we are using an evaluation license which adds a footer to all outgoing emails. Might this be the reason for the problem?

UPDATE:
The problem indeed only exists when using an evaluation license, most likely because of the “forced” footer that is being added in the evaluation version.

5

I have gotten in contact with support last night as well.
I have seen an entry in the old forums from 2009, where people were complaining about this ridiculous footer as well.

For the life of me: I still can’t understand why Axigen sticks to this footer - Especially without notifying potential customers about this!

6

Just opening this one back up on a ‘Wing & Prayer’ that someone might have the answer for this.

I’m experiencing this on a list of accounts… but not all accounts.

I’ve isolated this to…
Sending an email from Webmail with a basic attachment like a PDF file or Excel file. Email content has a signature with a basic jpeg image logo.

Email arrives at some mail clients as ‘This is a MIME message. You may need a MIME compliant mail user agent.’

Receiving the same email on iPhone or Google Workspace webmail all looks good.

Remove the image in the email Signature and all works perfectly as well.

The confusing part is… I have a few client accounts running and this one happens on some, but not all accounts. Each account email signature are all setup exactly the same.

Can anyone help out here?

7

bump
I am using the free axigen version as well and run into this problem with some addresses. For example gmx .

Any idea what the issue might be on the current version? I disabled the footer already but no change.

Thanks a lot in advance.