$ grep -c ^Return-path ~/mail/saved/2019
1159
$ grep -c ^Return-path ~/mail/saved/2019
1159-- https://www.greenend.org.uk/rjk/
Oh dear. I wonder who added that?
-- Socialism is the philosophy of failure, the creed of ignorance and the gospel of envy. Its inherent virtue is the equal sharing of misery. Winston Churchill
Exim. It?s following the spec:
-- https://www.greenend.org.uk/rjk/
And what a bloody good job MS' code minions have done. Runs like the clappers, stays running and the best bit of all, runs on Linux. So you can now run the engine on any old small cloud instance and use all the sexy tools (SSMS et al) on Windows. No need for (relatively) expensive Windows hosting any more.
Like everything DB, get the schema right, get the queries right, get the indexes right and it's a really, really solid system.
Mine runs fine in a 2GB mem, 2 core Xeon, 15GB SSD cheap VPS with 5500 active users (not simultaneously!) with access controlled by a load balanced set of four RESTful API servers, three have API in C#/.NET Core on Linux and one runs Node.js + FreeTDS on Linux. A beautiful marriage of cross platform, cross-ideology that just works.
On Fri, 20 Mar 2020 10:42:51 -0000 (UTC), Martin Gregorie declaimed the following:
M$ Access is a GUI front-end (query and report writer) to the JET database engine. JET being a "file-server" database (every application was directly opening/managing the database file itself). Access later grew an extension allowing one to use it as a GUI front-end for SQL Server/MSDE databases (at the time, this was the difference between an MDB and ADP [Access Data Project]).
-- Wulfraed Dennis Lee Bieber AF6VN wlfraed@ix.netcom.com http://wlfraed.microdiversity.freeddns.org/
The fact that you can reply to it only occurs because your MUA displayed it in such a way that you can reply to it. It can be plain wrong: how many times have you seen a sender displayed by your MUA as:
From [Close Friend ]
You haven't? Then one of the following applies (a) your MUA isn't configured to show the address after the display-name (b) your MUA can't/won't show the from address, so ditch it and get a better one (c) you haven't been watching out for spam
envelope sender is NOT the From: header and nothing says that there has to be a From: header or that irs content has to be the same as the envelope-from content
Same goes for the Return-address: and Reply-To: addresses though, because they are automatically set from the sender's account name and server domain, they are more likely to be correct.
-- Martin | martin at Gregorie | gregorie dot org
I never said it was.
The mail From sequence in smtp has nothing to do with the From: header
They are not,. Reply-to: is set by the senders MUA itself
Return-address: is a new feature that is set to the envelope from.
-- "Corbyn talks about equality, justice, opportunity, health care, peace, community, compassion, investment, security, housing...." "What kind of person is not interested in those things?" "Jeremy Corbyn?"
You're already in a state of regex sin. There are far too many exceptions to the rules with respect to an email address. The "+" is a sendmail construct, and has been replicated in postfix and possibly (likely?) present in other MTAs.
The domain portion is much smaller match space, but the username portion permits all characters ***if they're properly escaped***.
This is a thorny problem, and has been with us ever since someone put a webform asking for an email address on the web, and thought sanity checking the address was a good idea. In theory, a great idea, but in practice it will drive you to drink.
-- Consulting Minister for Consultants, DNRC I can please only one person per day. Today is not your day. Tomorrow isn't looking good, either. I am BOFH. Resistance is futile. Your network will be assimilated.
FSVO "good"
100% agree.
There's a little operator called "gmail" that supports it. I use it for testing things that need a unique email address, eg signups to a web site, by sticking a timestamp in: username+ snipped-for-privacy@gmail.com. The format is then easy for me to select on the backend and delete things later.
I think the original use the + was the Andrew system at CMU back in late
1980s early 1990s. It was certainly quickly implemented in sendmail's famously obfuscated cf language, but I don't know that CMU was using sendmail to do that.(But note: Last-modified: (2 Jun 98 14:32:39) )
Elijah
------ gmail wasn't around in 1998
OK, added it to my regex - can't do any harm with the way I'm using the regex.
-- Martin | martin at Gregorie | gregorie dot org
It may have originated in sendmail, but it's firmly enshrined in the standards - which originated way before MS, Google and even AOL started to bastardise the standard and create their own 'standard'. Start with RFC822
published in 1982 and work forwards to it's replacements/updates.
(which isn't easy reading, but you need to note that it specifies characters that can't be used rather than ones that can, so +, {}, ~ and whatever else you want are valid characters in an email address - see section 3.3 and look for 'atom')
Or drive the poor user (ie us) to throw their drink including bottle down the throats of the people who didn't even know standards existed let alone use them
-Gordon
ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.