Hi Sarah and others,

        Well, if you don't have this mail forwarding problem then there must be 
a way to fix it.  Anyone out there have a suggestion for me?

Eric Caron 
On May 16, 2014, at 11:28 PM, Sarah k Alawami <[email protected]> wrote:

> Yep. looks like you are having  the same issue my friend had. as for me when 
> I forward a message All I get is begin forded message. How odd.
> 
> On May 16, 2014, at 6:51 PM, Eric Caron <[email protected]> wrote:
> 
>> 
>> 
>> Begin forwarded message:
>> 
>>> From: Zachary Kline <[email protected]>
>>> Subject: Re: Mail forwarding, Can we avoid the unneeded info?
>>> Date: May 16, 2014 5:17:56 PM EDT
>>> To: OS X & iOS Accessibility <[email protected]>
>>> Reply-To: OS X & iOS Accessibility <[email protected]>
>>> Return-Path: <[email protected]>
>>> Delivered-To: [email protected]
>>> Delivered-To: [email protected]
>>> Received: from localhost (localhost [127.0.0.1]) by mail.tft-bbs.co.uk 
>>> (Postfix) with ESMTP id 79BF220A97EB; Fri, 16 May 2014 22:18:16 +0100 (BST)
>>> Received: from mail.tft-bbs.co.uk ([127.0.0.1]) by localhost 
>>> (mail.tft-bbs.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 
>>> JvafPgi542wp; Fri, 16 May 2014 22:18:13 +0100 (BST)
>>> Received: from mail.tft-bbs.co.uk (localhost [127.0.0.1]) by 
>>> mail.tft-bbs.co.uk (Postfix) with ESMTP id EA9BD20A97D1; Fri, 16 May 2014 
>>> 22:18:12 +0100 (BST)
>>> Received: from localhost (localhost [127.0.0.1]) by mail.tft-bbs.co.uk 
>>> (Postfix) with ESMTP id 96B9720A97AC for <[email protected]>; 
>>> Fri, 16 May 2014 22:18:09 +0100 (BST)
>>> Received: from mail.tft-bbs.co.uk ([127.0.0.1]) by localhost 
>>> (mail.tft-bbs.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 
>>> maLaLSrYyu9X for <[email protected]>; Fri, 16 May 2014 22:18:04 
>>> +0100 (BST)
>>> Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com 
>>> [66.111.4.26]) by mail.tft-bbs.co.uk (Postfix) with ESMTPS id 35B6A20A97A0 
>>> for <[email protected]>; Fri, 16 May 2014 22:18:03 +0100 (BST)
>>> Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) 
>>> by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id AC10220E6F for 
>>> <[email protected]>; Fri, 16 May 2014 17:17:58 -0400 (EDT)
>>> Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); 
>>> Fri, 16 May 2014 17:17:58 -0400
>>> Received: from 10-196-36-78.wireless.oregonstate.edu (unknown 
>>> [128.193.8.40]) by mail.messagingengine.com (Postfix) with ESMTPA id 
>>> 4B042C007B0 for <[email protected]>; Fri, 16 May 2014 17:17:58 
>>> -0400 (EDT)
>>> X-Virus-Scanned: amavisd-new at mail.tft-bbs.co.uk
>>> X-Virus-Scanned: amavisd-new at mail.tft-bbs.co.uk
>>> X-Original-To: [email protected]
>>> Dkim-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=speedpost.net; h= 
>>> content-type:mime-version:subject:from:in-reply-to:date 
>>> :content-transfer-encoding:message-id:references:to; s=mesmtp; 
>>> bh=lWckgYxD2Q6Owxzbt36raB9BwLY=; b=XVqbSSt6MQRRNYGKBQIWOB5nbT20 
>>> SXZDXFNYQS3NdXEM1dltuWiU/RJLhGqadjrFUUvqt01smQrL1q0Th/s3UMEWMuJk 
>>> HXSip/mSfpnDKNqZu6gAEJdfJv1SUeHf98Vx85Lnqt0ee1fkgupzFhSqOnlWMr3w 
>>> 6cB9zQNtRsuyV3M=
>>> Dkim-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; 
>>> h=content-type:mime-version:subject:from 
>>> :in-reply-to:date:content-transfer-encoding:message-id :references:to; 
>>> s=smtpout; bh=lWckgYxD2Q6Owxzbt36raB9BwLY=; b=NI 
>>> y4Bi4Iu6iU2vxP3Z9gwNjrIcqVZ/ntp0ns3wftiL5lwX7DbkhYGloTV6Gagow70R 
>>> qSj0iibb52YOe3sAszVxyY7OCNHVOJ6u0pPIpL/0G0sZntQdrfQNCK+sr2Ad1mjC 
>>> 4cGZ+ueGfiqwAulXfBFKuPM6Rhxtq2LDGfVnY51JQ=
>>> X-Sasl-Enc: Z1MTcNKEvH5gdAh2rbEC9sk7SHuVwJc1T0Xlxz/oqMg1 1400275078
>>> Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
>>> In-Reply-To: <[email protected]>
>>> Message-Id: <[email protected]>
>>> References: <[email protected]> 
>>> <[email protected]> 
>>> <[email protected]>
>>> X-Mailer: Apple Mail (2.1878.2)
>>> X-Beenthere: [email protected]
>>> X-Mailman-Version: 2.1.14
>>> Precedence: list
>>> List-Id: OS X & iOS Accessibility <mac-access.mac-access.net>
>>> List-Unsubscribe: <http://mail.tft-bbs.co.uk/mailman/options/mac-access>, 
>>> <mailto:[email protected]?subject=unsubscribe>
>>> List-Archive: <http://mail.tft-bbs.co.uk/pipermail/mac-access>
>>> List-Post: <mailto:[email protected]>
>>> List-Help: <mailto:[email protected]?subject=help>
>>> List-Subscribe: <http://mail.tft-bbs.co.uk/mailman/listinfo/mac-access>, 
>>> <mailto:[email protected]?subject=subscribe>
>>> Content-Type: text/plain; charset="windows-1252"
>>> Content-Transfer-Encoding: quoted-printable
>>> Errors-To: [email protected]
>>> Sender: [email protected]
>>> Hi Zach, above is all the chatter that appears when I forward a message.  
>>> I'd love to get rid of this as it makes reading forwarded mail very 
>>> difficult for me and for my recipients.  I'm amazed that this is the 
>>> default behavior for Apple Mail.
>> 
>> Eric Caron 
>> 
>> On May 16, 2014, at 5:17 PM, Zachary Kline <[email protected]> wrote:
>> 
>>> Eric,
>>> Can you clarify about which headers you’re seeing? Is it message ID, return 
>>> path, and so forth?
>>> You need to forward a new message for the command I gave you to work.
>>> Best,
>>> Zack.
>>> On May 16, 2014, at 2:13 PM, Eric Caron <[email protected]> wrote:
>>> 
>>>> Hi Zach,
>>>> 
>>>>    I tried command, shift, h, and there was no change.  I do hear VO say 
>>>> Default Headers.
>>>> 
>>>> Any tips on how I can adjust the default headers or another way to get rid 
>>>> of all the forwarding prefix chatter.
>>>> 
>>>> Eric Caron  
>>>> On May 16, 2014, at 4:34 PM, Zachary Kline <[email protected]> wrote:
>>>> 
>>>>> Eric,
>>>>> The problem is that you have told Mail to show all headers by default. If 
>>>>> you hit cmd-shift-h, you will switch to just seeing the basic ones.
>>>>> Best,
>>>>> Zack.
>>>>> On May 16, 2014, at 1:29 PM, Eric Caron <[email protected]> wrote:
>>>>> 
>>>>>> Hi listers,
>>>>>> 
>>>>>>  When I forward a message in mail it always has a long series of 
>>>>>> information about the message that I must get through before I can 
>>>>>> actually read the message.  Is there any setting or other way to keep 
>>>>>> mail from putting all this chatter at the top of a forwarded message? 
>>>>>> 
>>>>>> I'm using Mountain Lion.
>>>>>> 
>>>>>> Eric Caron 
>>>>>> 
>>>>>> 
>>>>>> <--- Mac Access At Mac Access Dot Net --->
>>>>>> 
>>>>>> To reply to this post, please address your message to 
>>>>>> [email protected]
>>>>>> 
>>>>>> You can find an archive of all messages posted    to the Mac-Access 
>>>>>> forum at either the list's own dedicated web archive:
>>>>>> <http://mail.tft-bbs.co.uk/pipermail/mac-access/index.html>
>>>>>> or at the public Mail Archive:
>>>>>> <http://www.mail-archive.com/[email protected]/>.
>>>>>> Subscribe to the list's RSS feed from:
>>>>>> <http://www.mail-archive.com/[email protected]/maillist.xml>
>>>>>> 
>>>>>> As the Mac Access Dot Net administrators, we do our very best to ensure 
>>>>>> that the Mac-Access E-Mal list remains malware, spyware, Trojan, virus 
>>>>>> and worm-free.  However, this should in no way replace your own security 
>>>>>> strategy.  We assume neither liability nor responsibility should 
>>>>>> something unpredictable happen.
>>>>>> 
>>>>>> Please remember to update your membership preferences periodically by 
>>>>>> visiting the list website at:
>>>>>> <http://mail.tft-bbs.co.uk/mailman/listinfo/mac-access/options/>
>>>>>> 
>>>>> 
>>>>> <--- Mac Access At Mac Access Dot Net --->
>>>>> 
>>>>> To reply to this post, please address your message to 
>>>>> [email protected]
>>>>> 
>>>>> You can find an archive of all messages posted    to the Mac-Access forum 
>>>>> at either the list's own dedicated web archive:
>>>>> <http://mail.tft-bbs.co.uk/pipermail/mac-access/index.html>
>>>>> or at the public Mail Archive:
>>>>> <http://www.mail-archive.com/[email protected]/>.
>>>>> Subscribe to the list's RSS feed from:
>>>>> <http://www.mail-archive.com/[email protected]/maillist.xml>
>>>>> 
>>>>> As the Mac Access Dot Net administrators, we do our very best to ensure 
>>>>> that the Mac-Access E-Mal list remains malware, spyware, Trojan, virus 
>>>>> and worm-free.  However, this should in no way replace your own security 
>>>>> strategy.  We assume neither liability nor responsibility should 
>>>>> something unpredictable happen.
>>>>> 
>>>>> Please remember to update your membership preferences periodically by 
>>>>> visiting the list website at:
>>>>> <http://mail.tft-bbs.co.uk/mailman/listinfo/mac-access/options/>
>>>>> 
>>>> 
>>>> <--- Mac Access At Mac Access Dot Net --->
>>>> 
>>>> To reply to this post, please address your message to 
>>>> [email protected]
>>>> 
>>>> You can find an archive of all messages posted    to the Mac-Access forum 
>>>> at either the list's own dedicated web archive:
>>>> <http://mail.tft-bbs.co.uk/pipermail/mac-access/index.html>
>>>> or at the public Mail Archive:
>>>> <http://www.mail-archive.com/[email protected]/>.
>>>> Subscribe to the list's RSS feed from:
>>>> <http://www.mail-archive.com/[email protected]/maillist.xml>
>>>> 
>>>> As the Mac Access Dot Net administrators, we do our very best to ensure 
>>>> that the Mac-Access E-Mal list remains malware, spyware, Trojan, virus and 
>>>> worm-free.  However, this should in no way replace your own security 
>>>> strategy.  We assume neither liability nor responsibility should something 
>>>> unpredictable happen.
>>>> 
>>>> Please remember to update your membership preferences periodically by 
>>>> visiting the list website at:
>>>> <http://mail.tft-bbs.co.uk/mailman/listinfo/mac-access/options/>
>>>> 
>>> 
>>> <--- Mac Access At Mac Access Dot Net --->
>>> 
>>> To reply to this post, please address your message to 
>>> [email protected]
>>> 
>>> You can find an archive of all messages posted    to the Mac-Access forum 
>>> at either the list's own dedicated web archive:
>>> <http://mail.tft-bbs.co.uk/pipermail/mac-access/index.html>
>>> or at the public Mail Archive:
>>> <http://www.mail-archive.com/[email protected]/>.
>>> Subscribe to the list's RSS feed from:
>>> <http://www.mail-archive.com/[email protected]/maillist.xml>
>>> 
>>> As the Mac Access Dot Net administrators, we do our very best to ensure 
>>> that the Mac-Access E-Mal list remains malware, spyware, Trojan, virus and 
>>> worm-free.  However, this should in no way replace your own security 
>>> strategy.  We assume neither liability nor responsibility should something 
>>> unpredictable happen.
>>> 
>>> Please remember to update your membership preferences periodically by 
>>> visiting the list website at:
>>> <http://mail.tft-bbs.co.uk/mailman/listinfo/mac-access/options/>
>>> 
>> 
>> <--- Mac Access At Mac Access Dot Net --->
>> 
>> To reply to this post, please address your message to 
>> [email protected]
>> 
>> You can find an archive of all messages posted    to the Mac-Access forum at 
>> either the list's own dedicated web archive:
>> <http://mail.tft-bbs.co.uk/pipermail/mac-access/index.html>
>> or at the public Mail Archive:
>> <http://www.mail-archive.com/[email protected]/>.
>> Subscribe to the list's RSS feed from:
>> <http://www.mail-archive.com/[email protected]/maillist.xml>
>> 
>> As the Mac Access Dot Net administrators, we do our very best to ensure that 
>> the Mac-Access E-Mal list remains malware, spyware, Trojan, virus and 
>> worm-free.  However, this should in no way replace your own security 
>> strategy.  We assume neither liability nor responsibility should something 
>> unpredictable happen.
>> 
>> Please remember to update your membership preferences periodically by 
>> visiting the list website at:
>> <http://mail.tft-bbs.co.uk/mailman/listinfo/mac-access/options/>
>> 
> 
> <--- Mac Access At Mac Access Dot Net --->
> 
> To reply to this post, please address your message to 
> [email protected]
> 
> You can find an archive of all messages posted    to the Mac-Access forum at 
> either the list's own dedicated web archive:
> <http://mail.tft-bbs.co.uk/pipermail/mac-access/index.html>
> or at the public Mail Archive:
> <http://www.mail-archive.com/[email protected]/>.
> Subscribe to the list's RSS feed from:
> <http://www.mail-archive.com/[email protected]/maillist.xml>
> 
> As the Mac Access Dot Net administrators, we do our very best to ensure that 
> the Mac-Access E-Mal list remains malware, spyware, Trojan, virus and 
> worm-free.  However, this should in no way replace your own security 
> strategy.  We assume neither liability nor responsibility should something 
> unpredictable happen.
> 
> Please remember to update your membership preferences periodically by 
> visiting the list website at:
> <http://mail.tft-bbs.co.uk/mailman/listinfo/mac-access/options/>
> 

<--- Mac Access At Mac Access Dot Net --->

To reply to this post, please address your message to [email protected]

You can find an archive of all messages posted    to the Mac-Access forum at 
either the list's own dedicated web archive:
<http://mail.tft-bbs.co.uk/pipermail/mac-access/index.html>
or at the public Mail Archive:
<http://www.mail-archive.com/[email protected]/>.
Subscribe to the list's RSS feed from:
<http://www.mail-archive.com/[email protected]/maillist.xml>

As the Mac Access Dot Net administrators, we do our very best to ensure that 
the Mac-Access E-Mal list remains malware, spyware, Trojan, virus and 
worm-free.  However, this should in no way replace your own security strategy.  
We assume neither liability nor responsibility should something unpredictable 
happen.

Please remember to update your membership preferences periodically by visiting 
the list website at:
<http://mail.tft-bbs.co.uk/mailman/listinfo/mac-access/options/>

Reply via email to