Xan wrote: ↑Thu Mar 14, 2024 9:48 pm
yankees60 wrote: ↑Thu Mar 14, 2024 9:29 am
Tyler wrote: ↑Wed Mar 06, 2024 2:28 pm
yankees60 wrote: ↑Wed Mar 06, 2024 11:15 am
Yet another example of how the Value Stock Geek consistently sends an email with an email date about 2 weeks prior to it actually being sent.
I was in the email box yesterday and it had nothing left in it about 24 hours ago. The email was not there. Today it is with a 2/21/24 date.
My educated guess is that it’s related to the fact that VSG makes his podcasts available to subscribers 2 weeks before he makes them public.
The "educated guess" wins the prize!
He responded quickly to my email to him yesterday:
"The podcasts are released behind a paywall for two weeks, then they go wide. So if you're a paying subscriber, you get early access to the episode on substack. Then, they get emailed out to the free audience 2 weeks later.
Question I still have is I'd always thought that my Eudora email showed the date that I received the email, not the date that they were sent. Also, how does it have a February 28 date if it is not sent until March 13?
It's actually not terribly easy for a mail client to operate on the date a message was received. The message stored on-disk in your mailbox probably doesn't have a "date received" header, whereas every message has a "date" header which is set by the sender side usually at the time of sending.
Picture physical mail: each letter you receive is (presumably) dated, but in order to sort your mail in the order it was received, you have to put it in a stack which is never modified (not really an option for mail clients since they aren't in control of what's happening on the server) or attempt to use postmarks to guess when each was received. Most of the time the guesses will be right because most email is received shortly after being sent.
In this case, the message is being composed and then sent 2 weeks later. I think it's weird that the message doesn't have a header giving the date it was sent rather than the date the message was composed. If I were advising this guy it's something I would insist on fixing.
Thanks for the explanation.
My ancient email program -- Eudora -- does (in part) provide me with this information:
X-Mailgun-Tag: post
X-Mailgun-Track-Clicks: false
Message-Id: <
20240228090035.3.3f5c348a985cf3f4@mg2.substack.com>
Date: Wed, 28 Feb 2024 09:00:35 +0000
Feedback-ID: post-141196316:cat-post:pub-263142:substack
sender: Value Stock Geek from Security Analysis <
valuestockgeek@substack.com>
References: <
post-141196316@substack.com>
In-Reply-To: <
post-141196316@substack.com>
Reply-To: Value Stock Geek from Security Analysis
<reply+2c2brw&3ifd&&
8e8edd7f25d7108cf84073dd1e4597f611e645c1328a45f2b04cf9a14549e630@mg1.substack.com>
List-Owner: <mailto:
valuestockgeek@substack.com>
List-URL: <
https://www.securityanalysis.org/>
List-Archive: <
https://www.securityanalysis.org/archive>
List-Unsubscribe: <
https://www.securityanalysis.org/action ... pires=365d>
List-Unsubscribe-Post: List-Unsubscribe=One-Click
List-Id: <valuestockgeek.substack.com>
List-Post: <
https://www.securityanalysis.org/p/phil ... -macro-and>
X-Mailgun-Variables: {"category": "post", "email_generated_at": "1710316902981", "is_freemail":
"true", "post_audience": "everyone", "post_id": "141196316", "post_type":
"podcast", "pub_community_enabled": "true", "publication_id": "263142",
"subdomain": "valuestockgeek", "user_id": "163849"}
X-CMAE-Envelope:
Delivery-date: Wed, 13 Mar 2024 04:02:28 -0400