Jump to content

WebMail, IPhone and photo attachments


Recommended Posts

When emailing a photo to my SpamCop WebMail from my IPhone (via my Yahoo.com email) the email arrives but no photo arrives.

When I email a photo to my Yahoo.com email account, the photo arrives.

When I email from my Yahoo.com to my SpamCop WebMail account, the photo arrives.

Any idea why emailing from my IPhone to my WebMail account fails to attach the photo?

Link to comment
Share on other sites

Any idea why emailing from my IPhone to my WebMail account fails to attach the photo?

The question posed doesn't seem to match the scenario described. From your description, it would seem to be an issue with the way Yahoo decides to handle your "to-be-forwarded" e-mail. How do the MIME header lines and body components look, as cmpared to what Yahoo 'saw' and what Yahoo 'delivered' ????

Link to comment
Share on other sites

The question posed doesn't seem to match the scenario described. From your description, it would seem to be an issue with the way Yahoo decides to handle your "to-be-forwarded" e-mail. How do the MIME header lines and body components look, as cmpared to what Yahoo 'saw' and what Yahoo 'delivered' ????

How do I view these?

Link to comment
Share on other sites

How do I view these?

Easy answer would be "View Source" of the e-mails. The MIME Boundary Lines are defined in the header, then used to'set-off' each different section of the bode .. the plain-text, the HTML, the attached file, etc.

Perhaps there's a bit of a need for more of an explanation of just how you are trying to do what you describe .. For insctance, you stated "emailing a photo to my SpamCop WebMail from my IPhone (via my Yahoo.com email)" .... but then later state "email a photo to my Yahoo.com email account" .... what is actually different between these two actions? I think what I'm not quite understanding is why AT&T isn't involved in your description, followed by the apparent missing step in just how the "via Yahoo.com email" is configured.

For example, is the issue actually at the "upload the attached photo" to the Yahoo e-mail server moment, based on the scenario of you being logged into the Yahoo server and attempting to compose the e-mail on-line ...?????

Link to comment
Share on other sites

  • 11 months later...

Hi,

I think I am experiencing the same (or a similar) issue.

When my wife sends me photo or html attachments from her iPhone (iOS 4.0.2) to my spamcop account via the Hotmail SMTP servers they get corrupted and the attachments do not work (examining the raw mail reveals that the mail doesn't have a blank line between the MIME header and body as in this SpamAssassin rule[1]). See example mangled contents below[2].

If the same mail is sent to a gmail account via the same hotmail SMTP setting it arrives at the other side unmangled and does have such a line included[3].

Sending from the iPhone using the same process except via gmail or spamcop SMTP servers also arrives at spamcop unmangled[4].

It looks to me like there may be some problem with spamcop processing mails sent by hotmail SMTP correctly, or maybe hotmail tweaks things just enough that a strict spamcop mail server program doesn't accept the way the blank like is encoded but gmail etc. does?

Any thoughts, suggestions or especially fixes welcome :)

Thanks,

Fred

[1]

SpamAssassin Rule: MISSING_MIME_HB_SEP

Standard description: Missing blank line between MIME header and body

Explanation

The format for e-mail requires a blank line between the headers and the body of a message, the lack of one causes this rule to fire.

[2] Sent from iPhone mail application through hotmail account to spamcop account, corrupted:

Return-Path: <xxxx[at]hotmail.com>
Delivered-To: spamcop-net-xxxx[at]spamcop.net
Received: (qmail 1773 invoked from network); 12 Aug 2010 11:35:39 -0000
X-spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on filter7
X-spam-Level: *****
X-spam-Status: hits=5.8 tests=MISSING_MIME_HB_SEP,TVD_SPACE_RATIO,TW_DX,TW_XB,
	TW_XL version=3.2.4
Received: from unknown (192.168.1.86)
  by filter7.cesmail.net with QMQP; 12 Aug 2010 11:35:39 -0000
Received: from blu0-omc4-s8.blu0.hotmail.com (65.55.111.147)
  by mxin2.cesmail.net with SMTP; 12 Aug 2010 11:35:12 -0000
Received: from BLU0-SMTP37 ([65.55.111.135]) by blu0-omc4-s8.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);
	 Thu, 12 Aug 2010 04:35:36 -0700
X-Originating-IP: [120.153.222.5]
X-Originating-Email: [xxxx[at]hotmail.com]
Message-ID: <BLU0-SMTP37BB0F2926022FA68474478A970[at]phx.gbl>
Return-Path: xxxx[at]hotmail.com
Received: from [10.218.81.146] ([120.153.222.5]) by BLU0-SMTP37.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);
	 Thu, 12 Aug 2010 04:35:31 -0700
Subject: Test9
From: xxxx <xxxx[at]hotmail.com>
Content-Type: multipart/mixed; boundary=Apple-Mail-5-510503636
Date: Thu, 12 Aug 2010 21:34:57 +1000
To: xxxx <xxxx[at]spamcop.net>
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (iPhone Mail 8A400)
X-Mailer: iPhone Mail (8A400)
X-OriginalArrivalTime: 12 Aug 2010 11:35:34.0295 (UTC) FILETIME=[7A204A70:01CB3A12]
X-SpamCop-Checked: 
X-SpamCop-Disposition: Blocked SpamAssassin=5


--Apple-Mail-5-510503636
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii


--Apple-Mail-5-510503636
Content-Disposition: inline;
	filename=photo.JPG
Content-Type: image/jpeg;
	name=photo.JPG
Content-Transfer-Encoding: base64
/9j/4AAQSkZJRgABAQEASABIAAD/4QMaRXhpZgAATU0AKgAAAAgADAEOAAIAAAAMAAAAngEPAAIA
AAAGAAAAqgEQAAIAAAAHAAAAsAESAAMAAAABAAEAAAEaAAUAAAABAAAAuAEbAAUAAAABAAAAwAEo

[3] Sent from iPhone mail application through hotmail account to gmail account, works fine:

Delivered-To: xxxx[at]gmail.com
Received: by 10.220.176.9 with SMTP id bc9cs17556vcb;
		Thu, 12 Aug 2010 04:34:17 -0700 (PDT)
Received: by 10.213.34.77 with SMTP id k13mr78478ebd.77.1281612856219;
		Thu, 12 Aug 2010 04:34:16 -0700 (PDT)
Return-Path: <xxxx[at]hotmail.com>
Received: from blu0-omc4-s22.blu0.hotmail.com (blu0-omc4-s22.blu0.hotmail.com [65.55.111.161])
		by mx.google.com with ESMTP id a59si3391516eei.68.2010.08.12.04.34.14;
		Thu, 12 Aug 2010 04:34:16 -0700 (PDT)
Received-SPF: pass (google.com: domain of xxxx[at]hotmail.com designates 65.55.111.161 as permitted sender) client-ip=65.55.111.161;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of xxxx[at]hotmail.com designates 65.55.111.161 as permitted sender) smtp.mail=xxxx[at]hotmail.com
Received: from BLU0-SMTP73 ([65.55.111.136]) by blu0-omc4-s22.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);
	 Thu, 12 Aug 2010 04:34:13 -0700
X-Originating-IP: [120.153.222.5]
X-Originating-Email: [xxxx[at]hotmail.com]
Message-ID: <BLU0-SMTP73F29580A0CF626F42A4988A970[at]phx.gbl>
Return-Path: xxxx[at]hotmail.com
Received: from [10.218.81.146] ([120.153.222.5]) by BLU0-SMTP73.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);
	 Thu, 12 Aug 2010 04:34:11 -0700
Subject: Test8
From: xxxx <xxxx[at]hotmail.com>
Content-Type: multipart/mixed; boundary=Apple-Mail-4-510424922
Date: Thu, 12 Aug 2010 21:33:39 +1000
To: xxxx[at]gmail.com
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (iPhone Mail 8A400)
X-Mailer: iPhone Mail (8A400)
X-OriginalArrivalTime: 12 Aug 2010 11:34:13.0145 (UTC) FILETIME=[49C1C890:01CB3A12]


--Apple-Mail-4-510424922
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii




--Apple-Mail-4-510424922
Content-Disposition: inline;
	filename=photo.JPG
Content-Type: image/jpeg;
	name=photo.JPG
Content-Transfer-Encoding: base64

/9j/4AAQSkZJRgABAQEASABIAAD/4QMaRXhpZgAATU0AKgAAAAgADAEOAAIAAAAMAAAAngEPAAIA
AAAGAAAAqgEQAAIAAAAHAAAAsAESAAMAAAABAAEAAAEaAAUAAAABAAAAuAEbAAUAAAABAAAAwAEo

[4] Sent from iPhone mail application through gmail account to spamcop account, works fine:

Return-Path: <xxxx[at]gmail.com>
Delivered-To: spamcop-net-xxxx[at]spamcop.net
Received: (qmail 6671 invoked from network); 12 Aug 2010 13:11:09 -0000
X-spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on filter7
X-spam-Level: **
X-spam-Status: hits=2.9 tests=TVD_SPACE_RATIO version=3.2.4
Received: from unknown (192.168.1.86)
  by filter7.cesmail.net with QMQP; 12 Aug 2010 13:11:09 -0000
Received: from mail-pv0-f176.google.com (74.125.83.176)
  by mxin2.cesmail.net with SMTP; 12 Aug 2010 13:10:39 -0000
Received: by pvg3 with SMTP id 3so500661pvg.21
		for <xxxx[at]spamcop.net>; Thu, 12 Aug 2010 06:11:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
		d=gmail.com; s=gamma;
		h=domainkey-signature:received:received:subject:from:content-type
		 :message-id:date:to:content-transfer-encoding:mime-version:x-mailer;
		bh=iJ48avzM1dW/l7q/Oi6ONkqxk5JhwuA+9GiPzbJvgjw=;
		b=Q29eapbqezBBF00LD3fugOdSp5Y0qfkhF0gPQ0/q8tnATgsEv2Kf5Y4kWBMglV7gLa
		 2HXNmHYPpG8HwJ+4+hrZJl4G+D5DVOVotOhgHaH7hR8JYevtWi6FUGVBvldrIMzHJ6fm
		 +II2veKjIDPiVUJkaw7p+VaOYWD++gXRClYfo=
DomainKey-Signature: a=rsa-sha1; c=nofws;
		d=gmail.com; s=gamma;
		h=subject:from:content-type:message-id:date:to
		 :content-transfer-encoding:mime-version:x-mailer;
		b=LKGq80UCDBLRVTLDne/CUNWx7bED35qou9XOEDqYFMdpY0Y1Bj1wHMMilUgeNxvSTu
		 IG0s10US/NOazawGiH6k3HP2ajFhKwTLs0OJKSqn7Itn91SRM6FrSAUox9VkghveXtNx
		 JXBiHnMi0EXgwagm7Wz2SNVICidAGU2KlkBoc=
Received: by 10.114.76.3 with SMTP id y3mr94806waa.11.1281618663458;
		Thu, 12 Aug 2010 06:11:03 -0700 (PDT)
Return-Path: <xxxx[at]gmail.com>
Received: from [192.168.2.36] (124-169-8-185.dyn.iinet.net.au [124.169.8.185])
		by mx.google.com with ESMTPS id c24sm2334929wam.19.2010.08.12.06.10.55
		(version=TLSv1/SSLv3 cipher=RC4-MD5);
		Thu, 12 Aug 2010 06:11:02 -0700 (PDT)
Subject: Test13 bis2
From: xxxx <xxxx[at]gmail.com>
Content-Type: multipart/mixed; boundary=Apple-Mail-10-516232821
Message-Id: <926155D0-E13E-470B-8C16-D440C3FF9FCC[at]gmail.com>
Date: Thu, 12 Aug 2010 23:10:27 +1000
To: xxxx <xxxx[at]spamcop.net>
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (iPhone Mail 8A400)
X-Mailer: iPhone Mail (8A400)
X-SpamCop-Checked: 74.125.83.176 124.169.8.185 
X-SpamCop-Whitelisted: xxxx[at]gmail.com


--Apple-Mail-10-516232821
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii




--Apple-Mail-10-516232821
Content-Disposition: inline;
	filename=photo.JPG
Content-Type: image/jpeg;
	name=photo.JPG
Content-Transfer-Encoding: base64

/9j/4AAQSkZJRgABAQEASABIAAD/4QMaRXhpZgAATU0AKgAAAAgADAEOAAIAAAAMAAAAngEPAAIA
AAAGAAAAqgEQAAIAAAAHAAAAsAESAAMAAAABAAEAAAEaAAUAAAABAAAAuAEbAAUAAAABAAAAwAEo

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...