Advanced users: Changes to mail headers

Jeremy Howard · 29th October 2003, 09:12 AM

People using advanced filtering may need to change their filters based on changes soon to occur to FastMail.FM headers. If you're not a major email geek, you should probably just skip this thread...

The changes will occur in the next couple of days. The first thing you'll notice is that there is one less Received header. The missing header is the one for the content filter injecting back into Postfix:

Code:

Received: from smtp.us2.messagingengine.com (localhost [127.0.0.1])
        by localhost.localdomain (Postfix) with ESMTP
        id E380436A1E0; Mon, 27 Oct 2003 06:38:37 -0500 (EST)

The X-Delivered-to header will now be added even if there are multiple local recipients.

The X-Attached header will now appear multiple times, once for each attachment.

The X-Sasl-enc header will now appear correctly in the Sent Items folder, rather than the non-encoded version previously shown if sent through the web interface. The X-Sasl-enc now includes the contents of X-Epoch as well, with a space character between, so X-Epoch will no longer be added.

These changes make things more consistent and robust, so if you use any of these features in your Sieve scripts, things should work better!

mcowger · 29th October 2003, 09:25 AM

Holy cow!

Its this level of information and data that makes me more than happy to pay $40/yr for this service.

bitequator · 29th October 2003, 11:20 AM

Hallelujah! I can see the next FM newsletter will be just as choke-full of new feature announcements

EDIT: What are all the attachment types that FM automatically rejects from SMTP and POP-Links (.pif, .scr, etc)?

I take it for POP-Links X-Resolved-to is still "username" and no X-Delivered-to? But I'm confused, where does X-Mail-from get its value from, from Return-Path?

hunter · 29th October 2003, 11:20 AM

well indeed its good news... now I can filter my spam mail better (I think). I've made some changes to my sieve.. just going to do some test on spam.. and the best way is to wait for real spam.

but I don't think I would want to pay for 40$/yr.. converted to my currency, current price for full is already quite high.

but I'm satisfied with the features and advanced nature of them.

bitequator · 29th October 2003, 11:32 AM

I'm gonna try to update some old threads @ these issues so old thread participants might be made aware (what the heck I have time)...

Jeremy Howard · 29th October 2003, 11:55 AM

Quote:

Originally posted by bitequator
EDIT: What are all the attachment types that FM automatically rejects from SMTP and POP-Links (.pif, .scr, etc)?

.pif, .scr, and executables with double-extensions (eg .txt.exe)

ady · 29th October 2003, 12:46 PM

Quote:

Originally posted by hunter
but I don't think I would want to pay for 40$/yr.. converted to my currency, current price for full is already quite high. but I'm satisfied with the features and advanced nature of them.

It was at first. But then it paid off. Believe me!

hunter · 31st October 2003, 04:20 PM

Quote:

Originally posted by Jeremy Howard
The X-Delivered-to header will now be added even if there are multiple local recipients.

Just small reminder..
fastmail faq should be updated, shouldn't it ?

bitequator · 31st October 2003, 04:25 PM

Including adding the other headers that aren't already in that FAQ list

Jeremy Howard · 31st October 2003, 04:31 PM

Quote:

Originally posted by hunter
Just small reminder..
fastmail faq should be updated, shouldn't it ?

Thanks, fixed now. Let me know if I've missed anything.

hadaso · 3rd November 2003, 06:39 AM

Quote:

Originally posted by Jeremy Howard
Thanks, fixed now. Let me know if I've missed anything.

"Received:", "Return-Path:", "X-Sieve:", "X-Spam-hits:". And then there are all those standard headers added when sending from the web interface, and those added when sending from a client...

Jeremy Howard · 3rd November 2003, 08:05 AM

Received, X-Sieve, and Return-path are not FastMail.FM-specific. I've added X-Spam-hits now.

David · 3rd November 2003, 08:54 AM

Quote:

Originally posted by Jeremy Howard

The X-Sasl-enc header will now appear correctly in the Sent Items folder, rather than the non-encoded version previously shown if sent through the web interface. The X-Sasl-enc now includes the contents of X-Epoch as well, with a space character between, so X-Epoch will no longer be added.

Jeremy, If the X-Epoch header is to be a thing of the past, does this mean that we will no longer be told stories, about the Unix geeks of the late sixties:

http://www.emaildiscussions.com/...170#post108170

Jeremy Howard · 3rd November 2003, 09:21 AM

Not at all: the epoch is still there - it's just in the X-Sasl-enc header now, concatenated by a space. Why? Mainly because of laziness - when we need to look up a user from the sasl-enc/epoch, we have to paste it into a form concatenated with a space - so now we save ourselves about two seconds a week by not having to copy and paste each bit separately...

Hey, laziness is one of the three great virtues...

bitequator · 3rd November 2003, 12:35 PM

What does this mean

Quote:

X-Spam: (deprecated)

http://encarta.msn.com/dictionary_/deprecate.html
http://www.m-w.com/cgi-bin/dictionary?deprecate

Are you just saying that you condemn/deplore/belittle/disparage spam?

29th October 2003, 09:12 AM	#1
Jeremy Howard Ultimate Contributor Join Date: Sep 2001 Location: Australia Posts: 11,499	Advanced users: Changes to mail headers People using advanced filtering may need to change their filters based on changes soon to occur to FastMail.FM headers. If you're not a major email geek, you should probably just skip this thread... The changes will occur in the next couple of days. The first thing you'll notice is that there is one less Received header. The missing header is the one for the content filter injecting back into Postfix: Code: Received: from smtp.us2.messagingengine.com (localhost [127.0.0.1]) by localhost.localdomain (Postfix) with ESMTP id E380436A1E0; Mon, 27 Oct 2003 06:38:37 -0500 (EST) The X-Delivered-to header will now be added even if there are multiple local recipients. The X-Attached header will now appear multiple times, once for each attachment. The X-Sasl-enc header will now appear correctly in the Sent Items folder, rather than the non-encoded version previously shown if sent through the web interface. The X-Sasl-enc now includes the contents of X-Epoch as well, with a space character between, so X-Epoch will no longer be added. These changes make things more consistent and robust, so if you use any of these features in your Sieve scripts, things should work better!

29th October 2003, 11:20 AM	#3
bitequator The "e" in e-mail Join Date: Apr 2003 Location: USA Posts: 2,978	Hallelujah! I can see the next FM newsletter will be just as choke-full of new feature announcements EDIT: What are all the attachment types that FM automatically rejects from SMTP and POP-Links (.pif, .scr, etc)? I take it for POP-Links X-Resolved-to is still "username" and no X-Delivered-to? But I'm confused, where does X-Mail-from get its value from, from Return-Path? Last edited by bitequator : 29th October 2003 at 11:52 AM.

29th October 2003, 09:25 AM	#2
mcowger Cornerstone of the Community Join Date: Sep 2002 Location: SF, CA Posts: 700	Holy cow! Its this level of information and data that makes me more than happy to pay $40/yr for this service.

29th October 2003, 11:20 AM	#4
hunter Essential Contributor Join Date: Dec 2002 Location: Indonesia Posts: 341	well indeed its good news... now I can filter my spam mail better (I think). I've made some changes to my sieve.. just going to do some test on spam.. and the best way is to wait for real spam. but I don't think I would want to pay for 40$/yr.. converted to my currency, current price for full is already quite high. but I'm satisfied with the features and advanced nature of them.

29th October 2003, 11:32 AM	#5
bitequator The "e" in e-mail Join Date: Apr 2003 Location: USA Posts: 2,978	I'm gonna try to update some old threads @ these issues so old thread participants might be made aware (what the heck I have time)...

31st October 2003, 04:25 PM	#9
bitequator The "e" in e-mail Join Date: Apr 2003 Location: USA Posts: 2,978	Including adding the other headers that aren't already in that FAQ list

3rd November 2003, 08:05 AM	#12
Jeremy Howard Ultimate Contributor Join Date: Sep 2001 Location: Australia Posts: 11,499	Received, X-Sieve, and Return-path are not FastMail.FM-specific. I've added X-Spam-hits now.

3rd November 2003, 09:21 AM	#14
Jeremy Howard Ultimate Contributor Join Date: Sep 2001 Location: Australia Posts: 11,499	Not at all: the epoch is still there - it's just in the X-Sasl-enc header now, concatenated by a space. Why? Mainly because of laziness - when we need to look up a user from the sasl-enc/epoch, we have to paste it into a form concatenated with a space - so now we save ourselves about two seconds a week by not having to copy and paste each bit separately... Hey, laziness is one of the three great virtues...