Problems receiving e-mail from Yahoo RRS feed

  • Question

  • I work for a company using Outlook 2007 and Microsoft Exchange. Our users periodically receive garbled e-mail messages from an Yahoo e-mail address. If there is an attachment, generally we just see the header in them message body and a whole string of characters where the attachment should be. This does not happen all the time but enough to concern us. I have tried reproducing this error a number of ways but have been unable to do. I do not know if it has to do from where the sender is located and what servers the they go through for their Yahoo? Any thoughts would be appreciated!!

    Here is a sample:

    From: xxxxx@yahoo.com [mailto:xxxxx@yahoo.com]
    Sent: Wednesday, July 07, 2010 10:11 AM

    Received: from [] by web53802.mail.re2.yahoo.com via HTTP; Wed, 07 Jul 2010 10:10:38 PDT
    X-Mailer: YahooMailRC/420.4 YahooMailWebService/
    References: <F9CD53D80A8A9843A88AC1EDEEB1C49C01FFAF1...
    Date: Wed, 7 Jul 2010 10:10:38 -0700 (PDT)
    From: x x<x@yahoo.com>
    Subject: Re: subject
    to: x x<x@x.com>
    In-Reply-To: <F9CD53D80A8A9843A88AC1EDEEB1C49C01FFAF1...
    MIME-Version: 1.0
    Content-Type: multipart/mixed; boundary="0-2034340211-1278522638=:93578...
    X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.8161:2.4.5,1.2.40,4.0.166
    definitions=2010-07-07_03:2010-02-06,201... signatures=0
    X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0
    bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx
    engine=5.0.0-1005130000 definitions=main-1007070069

    Content-Type: multipart/alternative; boundary="0-1420381799-1278522638=:93578...

    Content-Type: text/plain; charset=utf-8
    Content-Transfer-Encoding: quoted-printable

    Frist name: x=0AMiddle Name: Xx=0ALast name: x=0A=0boDY message=
    =0Aadobe form=
    at.=0A=0A=0AThanks \=0x=0A=0A=0A=0A=0A_____________________...
    _______=0AFrom: x<x@intelliquote.com>=0ATo: x@yahoo=
    .com=0ASent: Tue, July 6, 2010 2:17:05 PM=0ASubject: xsubject=0A=0A =0AHi x,=0AI am following up on x=E2=80=99s body=
    lication. Can you please verify xE2=80=99s =0Afull legal name? =0A=0A =
    =0AThank you,=x=x=0A=0A5170 GoldenParkway=
    =0Asomewhere, CA 11111=0Atoll free\fax: 111-111-1111=0Aemail: x@=
    *****************=0A=0AThis e-mail communication contains CONFIDENTIAL INFO=
    RMATION WHICH ALSO MAY BE =0ALEGALLY PRIVILEGED and which is intended only =
    for the use of the intended =0Arecipients identified above. If you are not =
    the intended recipient of this =0Acommunication, you are hereby notified th=
    at any use, dissemination, =0Adistribution, downloading, or copying of this=
    communication is strictly =0Aprohibited. If you have received this communi=
    cation in error, please immediately =0Anotify us by e-mail or by telephone =
    at phne number and delete the communication =0Aand destroy all copies. Tha=
    nk you for your cooperation.=0A=0A=0A
    Content-Type: multipart/related; boundary="0-904534753-1278522638=:93578"

    Content-Type: text/html; charset=utf-8
    Content-Transfer-Encoding: quoted-printable

    Friday, October 18, 2013 10:51 PM


All replies

  • If that's an accurate representation of the message then the problem lies on the sender's side.

    There's an empty line following the "Subject:" header. That signals an end of the message headers and everything that follows is part of the message body.

    If you have an anti-virus or anti-spam system between your server and the Internet that, too, may be the source of the problem.

    --- Rich Matheisen MCSE&I, Exchange MVP

    Saturday, October 19, 2013 4:10 PM
  • What is interesting is it can happen intermittently.  Sometimes e-mails from Yahoo e-mali comes through fine but most times it does not.  The only Anti-Virus we use is on the client machines and on the server itself.  I would think if the Anti-Virus were the issue this would be happening on more e-mail.  Below is another sample just in case you see anything different that may help.








    Received: from [] by web162603.mail.bf1.yahoo.com via HTTP; Tue, 15 Oct 2013 09:00:53 PDT

    X-Rocket-MIMEInfo: 002.001,Q29ycmVjdAoKCgoKT24gVHVlc2RheSwgT2N0b2JlciAxNSwgMjAxMyA4OjU5IEFNLCBUaW0gV2lydHogPHR3aXJ0ekBpbnRlbGxpcXVvdGUuY29tPiB3cm90ZToKICAKVGhhbmtzIEdhcnkuwqAgQ29vcnMgbGlnaHQgaXMgZmluZS7CoCBGb3Igd2hhdGV2ZXIgcmVhc29uIHlvdXIgWWFob28gZS1tYWlsIGNhbWUgdGhyb3VnaCBnYXJibGVkIHNvIGp1c3Qgd2FudGVkIHRvIHZlcmlmeSB0aGUgYWRkcmVzcyBhcyAxNjAwIFNsaWdlciBNaW5lIFJvYWQsIEdyZWVud29vZCBDQS4KClRoYW5rIHlvdSwgCsKgIApUaW0BMAEBAQE-

    X-Mailer: YahooMailWebService/

    References: <x@x.com> <F9CD53D80A8A9843A88AC1EDEEB1C49C03D86E9D@xcom>

    Message-ID: <1381852853.56616.YahooMailNeo@web162603.mail.bf1.yahoo.com>

    Date: Tue, 15 Oct 2013 09:00:53 -0700 (PDT)

    From: Gary Deeds <x@yahoo.com>

    Reply-To: Gary Deeds <x@yahoo.com>

    Subject: Re:

    to: x<x@intelliquote.com>

    In-Reply-To: <F9CD53D80A8A9843A88AC1EDEEB1C49C03D86E9D@x.com>

    MIME-Version: 1.0

    Content-Type: multipart/alternative; boundary="-704123553-925725095-1381852853=:56616"

    X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794,1.0.431,0.0.0000

     definitions=2013-10-15_06:2013-10-15,2013-10-15,1970-01-01 signatures=0

    X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0

     phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx

     scancount=1 engine=6.0.2-1305240000 definitions=main-1310150067


    Content-Type: text/plain; charset=iso-8859-1

    Content-Transfer-Encoding: quoted-printable

    Correct=0A=0A=0A=0A=0AOn Tuesday, October 15, 2013 8:59 AM, x<x

    x@x.com> wrote:=0A  =0AThanks x.=A0 x.=A0 ==0A=0AThank you=

    , =0A=A0 ==0AIT Systems Support =xA@x.com =0AVo=

    ice\Fax: (x)xxx-xxxx=0Ax Insurance Services =0Ax==0AEl Dorado x =0A=0AFollow x:=0A=


    *=0A=0AThis e-mail communication contains CONFIDENTIAL INFORMATION WHICH AL=

    SO MAY BE LEGALLY PRIVILEGED and which is intended only for the use of the =

    intended recipients identified above. If you are not the intended recipient=

     of this communication, you are hereby notified that any use, dissemination=

    , distribution, downloading, or copying of this communication is strictly p=

    rohibited. If you have received this communication in error, please immedia=

    tely notify us by e-mail or by telephone at xxx-xxx-xxxx and delete the com=

    munication and destroy all copies. Thank you for your cooperation.=0A=0A***=

    ******************************************************************* =0A****=

    ********************************************************** =0A=0A=0A=0A=0A-=

    Monday, October 21, 2013 2:53 PM
  • put yahoo.com in remote domains ,   *.yahoo.com  and let me know if you still face this issue.

    Monday, October 21, 2013 3:05 PM
  • Thank you for your replay.  Where would the option be for remote domains?  Is that somewhere on the Exchange server?
    Monday, October 21, 2013 3:38 PM
  • in organization settings under hub transport look for remote domains. put *.yahoo.com

    Monday, October 21, 2013 3:40 PM
  • Whether it happens to all, or only some, e-mail the source is still the same -- an empty line in the wrong place.

    You can use Pipeline Tracing to see what's in the message as it arrives at a particular transport server (it's set using the set-transportserver cmdlet).

    --- Rich Matheisen MCSE&I, Exchange MVP

    Monday, October 21, 2013 10:15 PM
  • Unfortunatly, we are still on Exchange 2003 so the pipeline tracing is not built in.  Thanks for the responses though. 
    Monday, October 21, 2013 10:42 PM
  • This will work for 2003:


    --- Rich Matheisen MCSE&I, Exchange MVP

    Tuesday, October 22, 2013 2:54 AM