mail delivered to folder .....slight problem

[ehabshoubaki]

I know that fastmail has the cool capability that if an email is sent to "folder @ some_alias_of_yours" the email will end up in the specified folder .

well , I got an email recently that went to the rigth folder but later (a couple of minutes) another copy was delivered to the inbox . the inbox copy had let's say SUBJECT in the subject field and the copy in the folder had FW:SUBJECT .....

it's a small problem , but why did it happen ?

take care

Can you post the X-Delivered-To header from both emails?

Do you have any explicit rules that may have overridden the subdomain addressing feature?

[ehabshoubaki]

header of email in Inbox
*****************************************
Return-Path: REMOVED
Received: from frontend3.messagingengine.com (frontend3.internal [10.202.2.152])
by www.fastmail.fm (Cyrus v2.3-prealpha) with LMTPA;
Thu, 15 Jul 2004 12:02:30 -0400
X-Sieve: CMU Sieve 2.2
X-Spam-score: 0.0
X-Spam-hits: BAYES_00, HTML_50_60, HTML_MESSAGE, NO_RDNS2
X-Resolved-to: ehabshoubaki+ebab [at] fastmail.fm
X-Delivered-to: ebab [at] etutor.ftml.net
X-Mail-from: REMOVED
Received: from usaflcms09.usa-spaceops.ksc.nasa.gov (usaflcms09.ksc.nasa.gov [163.206.102.153])
by smtp.us.messagingengine.com (Postfix) with ESMTP id 9730A54298C
for <ebab [at] etutor.ftml.net>; Thu, 15 Jul 2004 12:02:28 -0400 (EDT)
Received: from USAFLCMS05.usa-spaceops.ksc.nasa.gov ([163.206.102.6]) by usaflcms09.usa-spaceops.ksc.nasa.gov with Microsoft SMTPSVC(5.0.2195.5329);
Thu, 15 Jul 2004 12:02:27 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C46A85.1FE02778"
Subject: Electrical engineering
Date: Thu, 15 Jul 2004 12:02:27 -0400
Message-ID: <B2765506C3331C4581ED6B2777D1D95336E0E7@usaflcms05.usa-spaceops.ksc.nasa.gov>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Electrical engineering
Thread-Index: AcRqhR/qe4HgmtPKTsyYMdPRjL8KKg==
From: "Seling, George F" <REMOVED>
To: <ebab[at]etutor.ftml.net>
X-OriginalArrivalTime: 15 Jul 2004 16:02:27.0529 (UTC) FILETIME=[201EA390:01C46A85]
********************************************************

Header of email in folder (in correct place)
**********************************************************

Return-Path: <REMOVED>
Received: from frontend3.messagingengine.com (frontend3.internal [10.202.2.152])
by www.fastmail.fm (Cyrus v2.3-prealpha) with LMTPA;
Thu, 15 Jul 2004 12:03:38 -0400
X-Sieve: CMU Sieve 2.2
X-Spam-score: 0.0
X-Spam-hits: BAYES_00, HTML_50_60, HTML_MESSAGE, NO_RDNS2
X-Resolved-to: ehabshoubaki+ehab[at]fastmail.fm
X-Delivered-to: ehab[at]etutor.ftml.net
X-Mail-from: REMOVED
Received: from usaflcms09.usa-spaceops.ksc.nasa.gov (usaflcms09.ksc.nasa.gov [163.206.102.153])
by smtp.us.messagingengine.com (Postfix) with ESMTP id 9BCF2542E14
for <ehab[at]etutor.ftml.net>; Thu, 15 Jul 2004 12:03:34 -0400 (EDT)
Received: from USAFLCMS05.usa-spaceops.ksc.nasa.gov ([163.206.102.6]) by usaflcms09.usa-spaceops.ksc.nasa.gov with Microsoft SMTPSVC(5.0.2195.5329);
Thu, 15 Jul 2004 12:03:34 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C46A85.47F0EBE4"
Subject: FW: Electrical engineering
Date: Thu, 15 Jul 2004 12:03:34 -0400
Message-ID: <B2765506C3331C4581ED6B2777D1D95336E0E8@usaflcms05.usa-spaceops.ksc.nasa.gov>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Electrical engineering
Thread-Index: AcRqhR/qe4HgmtPKTsyYMdPRjL8KKgAAAduw
From: "Seling, George F" <REMOVED>
To: <ehab[at]etutor.ftml.net>
X-OriginalArrivalTime: 15 Jul 2004 16:03:34.0733 (UTC) FILETIME=[482D27D0:01C46A85]
**********************************************************

I don't have any explicit rules.

take care.

The headers are identical, except for the Thread-Index, date and message ID.

You do not have any rules, so this is not a fileinto+keep problem.

The emails were sent a minute after each other (successive Message-ID's ), so it's unlikely (though possible) that it's a temporary error at FM.

I assume you didn't move them, and you didn't have any client-side rules to do this, either.

Is this the first time? Has this happened only once? If not, is there a pattern?

[ehabshoubaki]

nothing on the client side....

this happened only once ....... I've tried test sending but couldn't duplicate the problem ... probably a transient fluke.

take care