Jump to content

[Resolved] eM Client Forward As Attachment

Recommended Posts

I'm testing eM Client as a replacement for Windows Live Mail and can't seem to get SpamCop to process my forwarded emails. If I forward a spam email from Windows Live Mail it processes perfectly but if I forward the same email via eM Client it is rejected as being unable to parse. Does anyone have a clue what might be happening?

Link to comment
Share on other sites

Was hopping that someone familiar with eM would reply

What is common in these cases is that the application does not correctly forward the email, usually making modifications to the header of the attached spam.

In your case can you open your email, reporting the spam, and look at the underlying code, by using <ctrl> U.  Following you email you should see something link

Content-Type: message/rfc822;
 name="Attached Message"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="Attached Message"

X-Account-Key: account5

Followed by the attached email (X-Account-Key: is the first line of the attached)  The blank line is important.

Link to comment
Share on other sites

This is what I get...

From: QuickMedInsurance <FastMedCare@mobilepoisk.ru>

To: "C.B. McCoy" <radio-man@msn.com>

Subject: Find More Phenomenal Discounts

Date: Thu, 13 Apr 2017 03:18:33 +0000

Message-Id: <B3491F8BD80C22914D4801BDA969AF8F@mobilepoisk.ru>

Reply-To: QuickMedInsurance <FastMedUpdate@online-marketing148.ru>

Mime-Version: 1.0

Content-Type: text/html; charset=utf-8

Content-Transfer-Encoding: quoted-printable

Content-Disposition: inline

Link to comment
Share on other sites

From what you provided it would appear that eM is not including the header.  This is a common issue.  The writers of some applications don't understand why users would want to forward the unseen header.


Link to comment
Share on other sites

  • 4 weeks later...


This topic is now archived and is closed to further replies.

  • Create New...