On 8/17/15, jimmy cho <jcho@xxxxxxxxxxxxxxxx> wrote: > Hi, > > Thank you for the reply, > > Yes squirrelmail account is sales@xxxxxxxxxxxx > <sales@xxxxxxxxxxxx> > > logged in as the user sales. the email is from the sender > 3FIQ@xxxxxxxxxx . The mail header is > > > Return-Path: <3FIQ@xxxxxxxxxx> > X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on cccxith.com > X-Spam-Level: > X-Spam-Status: No, score=0.0 required=6.0 tests=SPF_PASS,URIBL_BLOCKED > autolearn=unavailable autolearn_force=no version=3.4.0 > X-Original-To: sales@xxxxxxxxxxxx > Delivered-To: sales@xxxxxxxxxxxx > Received: from mail3.sa47.com (mail3.satc7.com []) > by cccxxith.com (Postfix) with ESMTP id C9E6C826C19C4 > for <sales@xxxxxxxxxxxx>; Thu, 13 Aug 2015 21:22:03 +0800 (SGT) > MIME-Version: 1.0 > Content-Type: multipart/mixed; > boundary="----_=_NextPart_001_01D0D5C9.5BDB8400" > Content-class: urn:content-classes:message > X-MimeOLE: Produced By Microsoft Exchange V6.5 > Subject: Tango: Final Outstanding > Date: Thu, 13 Aug 2015 13:10:16 -0000 > Message-ID: <5895F58F1CBCFB4B9798B816644E0A320285CBF8@xxxxxxxxxxxxxxxxxxx> > In-Reply-To: <5895F58F1CBCFB4B9798B816644E0A32020F408A@xxxxxxxxxxxxxxxxxxx> > X-MS-Has-Attach: yes > X-MS-TNEF-Correlator: > Thread-Topic: Tango: Final Outstanding > Thread-Index: AdDUC/C+4QueShRdQL+Ib7kuEwoRpg== > References: > <OF09125DEE.DEA5422C-ON48257B95.00122404-48257B95.00127049@xxxxxxxxxxxxx> > <000001ce7153$98f91cd0$caeb5670$@singnet.com.sg> > <25ea01ce7155$199977d0$4ccc6770$@ewliner.com> > <00ba01ce7157$81d7a590$8586f0b0$@ewliner.com> > <OFE1590139.822B0650-ON48257B97.004D946D-48257B97.004DD62B@xxxxxxxxxxxxx> > <003001ce73a0$55c41b00$014c5100$@ewliner.com> > <B1F64A67DE10644C8CBA4A63E0166F118BAED4D6@uk-site0-ex01> > <002401ce73e8$c70e67a0$552b36e0$@ewliner.com> > <OFF03F7889.17EE55DA-ON48257B9B.002036D2-48257B9B.0020541C@xxxxxxxxxxxxx> > <010001ce7622$85280080$8f780180$@ewliner.com> > <OF63A1FF93.30113491-ON48257B9B.00242657-48257B9B.00245664@xxxxxxxxxxxxx> > <011901ce77b3$255c2450$70146cf0$@ewliner.com> > <OF7B7C36CE.F2506CA5-ON48257B9D.002257A5-48257B9D.00228A16@xxxxxxxxxxxxx> > <5895F58F1CBCFB4B9798B816644E0A32020F408A@xxxxxxxxxxxxxxxxxxx> > From: <3FIQ@xxxxxxxxxx> > To: "Sales" <sales@xxxxxxxxxxxx> > Cc: "purchase tanker" <purtanker@xxxxxxxxxxxxx>, > <tanker-a@xxxxxxxxxxxxx>, > "Alk Rt" <alok.rawat@xxxxxxxxxxxxx>, > "Chine Kh" <chr@xxxxxxxxxxxxx> > Reply-To: <sales@xxxxxxxxxxxx> > > > Problem is when reply-all is selected, the sender > > 3FIQ@xxxxxxxxxx > > is not listed in the To: field Because there is a Reply-To in the original message. > only the cc addresses. The email was > sent and the sender never got the reply because the user did not spot the > missing 3FIQ@xxxxxxxxxx address. I agreed the email header is > defective because of the erroneous Reply-To: . But the From: field > entry 3FIQ@xxxxxxxxxx should be in the To: field in the reply email > compose page. According to who? Can you show the part of the RFC that requires this? I don't believe it's specifically defined, but I think the expectation is that a user will specify a Reply-To precisely because they do not want a reply to go to the From address. FWIW, Thunderbird behaves exactly the same. I think your other webmail client is the non-standard outlier. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php ------------------------------------------------------------------------------ ----- squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@xxxxxxxxxxxxxxxxxxxxx List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
