Hi all,
This little tutorial explains you how to run your own email
infrastructure for family and friends, without paying a dime.
No email privacy provider accounts required.
No own Domain required.
No VPS required.
No postfix set-up required.
No pop3,IMAP required.
Requirements:
The received email looks like this:
Received: from localhost (kubernetes.docker.internal. [127.0.0.1])
by iria (SMTPDump) with SMTP
for <castor@fswlpxkp6xdrwrcu3dmby4lwv4z22bep32s3f3ffrua3x4bmvdyhg2ad.onion>; Sun, 18 May 2025 21:32:18 +0200 (CEST)
From: pollux@fswlpxkp6xdrwrcu3dmby4lwv4z22bep32s3f3ffrua3x4bmvdyhg2ad.onion To: castor@fswlpxkp6xdrwrcu3dmby4lwv4z22bep32s3f3ffrua3x4bmvdyhg2ad.onion Subject: äöüÄÖÜߤ
Message-ID: <myj85zmjpi.1747596734@jcdui.nd>
Date: Sun, 18 May 2025 19:32:14 +0000
As you see, no MIME headers for international characters are needed.
Stefan Claas wrote:
Hi all,
This little tutorial explains you how to run your own email
infrastructure for family and friends, without paying a dime.
No email privacy provider accounts required.
No own Domain required.
No VPS required.
No postfix set-up required.
No pop3,IMAP required.
Requirements:
OmniMix.
The received email looks like this:
Received: from localhost (kubernetes.docker.internal. [127.0.0.1])
by iria (SMTPDump) with SMTP
for <castor@fswlpxkp6xdrwrcu3dmby4lwv4z22bep32s3f3ffrua3x4bmvdyhg2ad.onion>; Sun, 18 May 2025 21:32:18 +0200 (CEST)
From: pollux@fswlpxkp6xdrwrcu3dmby4lwv4z22bep32s3f3ffrua3x4bmvdyhg2ad.onion To: castor@fswlpxkp6xdrwrcu3dmby4lwv4z22bep32s3f3ffrua3x4bmvdyhg2ad.onion Subject: äöüÄÖÜ߀
Message-ID: <myj85zmjpi.1747596734@jcdui.nd>
Date: Sun, 18 May 2025 19:32:14 +0000
As you see, no MIME headers for international characters are needed.
There are multi-byte character sets out there, you laughing stock.
And beyond that it's inherently foolish to rely on the recipient
using your default charset.
BTW, MID <20250414.023758.60358c31@msgid.frell.theremailer.net>
explains in a few steps how it's really done the easy way within a
few minutes and without depriving you of your favourite standard
SMTP/POP3 mail client capable of handling your region's character
set(s).
Or you set up a nym account with it, which means state-of-the-art
protection even against worst imaginable adversaries.
Anonymous wrote:
Stefan Claas wrote:
Hi all,
This little tutorial explains you how to run your own email
infrastructure for family and friends, without paying a dime.
No email privacy provider accounts required.
No own Domain required.
No VPS required.
No postfix set-up required.
No pop3,IMAP required.
Requirements:
OmniMix.
Oh please, only a handful of Windows users are using Omnimix.
Anonymous wrote:
Stefan Claas wrote:
Hi all,
This little tutorial explains you how to run your own email infrastructure for family and friends, without paying a dime.
No email privacy provider accounts required.
No own Domain required.
No VPS required.
No postfix set-up required.
No pop3,IMAP required.
Requirements:
OmniMix.
Oh please, only a handful of Windows users are using Omnimix.
This tutorial is aimed for the mainstream.
In article <3a1849664742667932eaa48b9f82cc04aeee48eb@i2pn2.org>
Stefan Claas <stefan@mailchuck.com> wrote:
Anonymous wrote:
Stefan Claas wrote:
Hi all,
This little tutorial explains you how to run your own email infrastructure for family and friends, without paying a dime.
No email privacy provider accounts required.
No own Domain required.
No VPS required.
No postfix set-up required.
No pop3,IMAP required.
Requirements:
OmniMix.
Oh please, only a handful of Windows users are using Omnimix.
This tutorial is aimed for the mainstream.
[snip]
Stefan, ignore the trolls/distractors. They do nothing for the remailer community.
You, sir, do what you can, and it's greatly appreciated
Have fun with your Omnimix rig and third-party servers involved.
Stefan Claas <stefan@mailchuck.com> wrote:
Have fun with your Omnimix rig and third-party servers involved.
With 3rd party you mean the tor circuit or what?
Anonymous User wrote:
Stefan Claas <stefan@mailchuck.com> wrote:
Have fun with your Omnimix rig and third-party servers involved.
With 3rd party you mean the tor circuit or what?
The involved smtp/pop3/IMAP servers or the nym server.
Stefan Claas <stefan@mailchuck.com> wrote:
Anonymous User wrote:
Stefan Claas <stefan@mailchuck.com> wrote:
Have fun with your Omnimix rig and third-party servers involved.
With 3rd party you mean the tor circuit or what?
The involved smtp/pop3/IMAP servers or the nym server.
There are no exteral mail servers involved, as the Omnimix package already includes a Hamster SMTP/POP3/NNTP server, primarily used to hold a local alt.anonymous.messages repository for nym reply extraction. It's an easy task to activate that Hamster's mail servers from within the GUI and
connect its SMTP part with a hidden service of the also present Tor subsystem.
You see, what you present here is old news for an Omnimix user.
Stefan Claas wrote:
As you see, no MIME headers for international characters are needed.
There are multi-byte character sets out there, you laughing stock.
And beyond that it's inherently foolish to rely on the recipient
using your default charset.
In article <20250519.032550.a4e89a88@yamn.paranoici.org>
Anonymous <nobody@yamn.paranoici.org> wrote:
Stefan Claas wrote:
As you see, no MIME headers for international characters are needed.
That kind of MIME-free magic is beyond a Taiwanese who's used to use a
Big5 character set, and me. So it looks as if generations of Internet programmers were wrong thinking MIME encoding is of any importance.
Or does Class once again demonstrate his own incompetence in dealing
with MIME encoding by idealizing homebrew ASCII-only crippleware?
There are multi-byte character sets out there, you laughing stock.
And beyond that it's inherently foolish to rely on the recipient
using your default charset.
And you need MIME encoding to attach files to mail messages.
There are multi-byte character sets out there, you laughing stock.
And beyond that it's inherently foolish to rely on the recipient
using your default charset.
And you need MIME encoding to attach files to mail messages.
Anonymous User wrote:
Stefan Claas <stefan@mailchuck.com> wrote:
Anonymous User wrote:
Stefan Claas <stefan@mailchuck.com> wrote:
Have fun with your Omnimix rig and third-party servers involved.
With 3rd party you mean the tor circuit or what?
The involved smtp/pop3/IMAP servers or the nym server.
There are no exteral mail servers involved, as the Omnimix package already >> includes a Hamster SMTP/POP3/NNTP server, primarily used to hold a local
alt.anonymous.messages repository for nym reply extraction. It's an easy
task to activate that Hamster's mail servers from within the GUI and
connect its SMTP part with a hidden service of the also present Tor
subsystem.
You see, what you present here is old news for an Omnimix user.
And how about the publicity involved smtp servers in a chain,
or the recipient's mail server, when you write messages?
Fritz Wuehler wrote:
There are multi-byte character sets out there, you laughing stock.
And beyond that it's inherently foolish to rely on the recipient
using your default charset.
And you need MIME encoding to attach files to mail messages.
For beginners, use base64+ from me, without any MIME 1.0 headers.
https://github.com/Ch1ffr3punk/base64-plus
Fritz Wuehler wrote:
There are multi-byte character sets out there, you laughing stock.
And beyond that it's inherently foolish to rely on the recipient
using your default charset.
And you need MIME encoding to attach files to mail messages.
For beginners, use base64+ from me, without any MIME 1.0 headers.
https://github.com/Ch1ffr3punk/base64-plus
Regards
Stefan
Anonymous User wrote:
Stefan Claas <stefan@mailchuck.com> wrote:
Anonymous User wrote:
Stefan Claas <stefan@mailchuck.com> wrote:
Have fun with your Omnimix rig and third-party servers involved.
With 3rd party you mean the tor circuit or what?
The involved smtp/pop3/IMAP servers or the nym server.
There are no exteral mail servers involved, as the Omnimix package already >> includes a Hamster SMTP/POP3/NNTP server, primarily used to hold a local
alt.anonymous.messages repository for nym reply extraction. It's an easy
task to activate that Hamster's mail servers from within the GUI and
connect its SMTP part with a hidden service of the also present Tor
subsystem.
You see, what you present here is old news for an Omnimix user.
And how about the publicity involved smtp servers in a chain,
or the recipient's mail server, when you write messages?
As you see, no MIME headers for international characters are needed.set-up >your own email
Hello World! :-)Step 6. That's all. :-) You now have successfully
service, which is online as long as you do not power-off yourPC.
This way you can be reached, once you come home fromschool/work.
Stefan Claas <stefan@mailchuck.com> wrote:
Fritz Wuehler wrote:
There are multi-byte character sets out there, you laughing stock.
And beyond that it's inherently foolish to rely on the recipient
using your default charset.
And you need MIME encoding to attach files to mail messages.
For beginners, use base64+ from me, without any MIME 1.0 headers.
https://github.com/Ch1ffr3punk/base64-plus
Take your meds, Stefen!
Fritz Wuehler wrote:
In article <20250519.032550.a4e89a88@yamn.paranoici.org>
Anonymous <nobody@yamn.paranoici.org> wrote:
Stefan Claas wrote:
As you see, no MIME headers for international characters are needed.
That kind of MIME-free magic is beyond a Taiwanese who's used to use a
Big5 character set, and me. So it looks as if generations of Internet
programmers were wrong thinking MIME encoding is of any importance.
Or does Class once again demonstrate his own incompetence in dealing
with MIME encoding by idealizing homebrew ASCII-only crippleware?
Do us all a favor and test it by yourself.
In article <329a2004cb27756fe709e2cf8e882762c5b5ccf1@i2pn2.org>
Stefan Claas <stefan@mailchuck.com> wrote:
Fritz Wuehler wrote:
In article <20250519.032550.a4e89a88@yamn.paranoici.org>
Anonymous <nobody@yamn.paranoici.org> wrote:
Stefan Claas wrote:
As you see, no MIME headers for international characters are needed.
That kind of MIME-free magic is beyond a Taiwanese who's used to use a Big5 character set, and me. So it looks as if generations of Internet programmers were wrong thinking MIME encoding is of any importance.
Or does Class once again demonstrate his own incompetence in dealing
with MIME encoding by idealizing homebrew ASCII-only crippleware?
Do us all a favor and test it by yourself.
No. As we're not only interested in your success, but even more in the reason why it works you'd better do us all a favour and explain how the recipient of a two byte message knows that those aren't two ASCII
characters but instead it's one of the more that 13 thousand Chinese characters from the 2-byte Big5 character table. Please enlighten us!
In article <5a30bad7e6175153eceedee9b25f02a8bb56cc01@i2pn2.org>
Stefan Claas wrote:
Fritz Wuehler wrote:
There are multi-byte character sets out there, you laughing stock.
And beyond that it's inherently foolish to rely on the recipient
using your default charset.
And you need MIME encoding to attach files to mail messages.
For beginners, use base64+ from me, without any MIME 1.0 headers.
https://github.com/Ch1ffr3punk/base64-plus
Regards
Stefan
So your message header contains a MIME-Version line
without any further MIME entries!? Very smart! LOL!
On 19 May 2025, Fritz Wuehler <fritz@spamexpire-202505.rodent.frell.theremailer.net> posted some news:20250520.010943.799d277b@msgid.frell.theremailer.net:
In article <5a30bad7e6175153eceedee9b25f02a8bb56cc01@i2pn2.org>
Stefan Claas wrote:
Fritz Wuehler wrote:
There are multi-byte character sets out there, you laughing stock.
And beyond that it's inherently foolish to rely on the recipient
using your default charset.
And you need MIME encoding to attach files to mail messages.
For beginners, use base64+ from me, without any MIME 1.0 headers.
https://github.com/Ch1ffr3punk/base64-plus
Regards
Stefan
So your message header contains a MIME-Version line
without any further MIME entries!? Very smart! LOL!
It's just extra lines. Who needs that?
Fritz Wuehler wrote:
In article <329a2004cb27756fe709e2cf8e882762c5b5ccf1@i2pn2.org>UTF-8 is the default for modern protocols (HTTP, JSON, etc.).
Stefan Claas <stefan@mailchuck.com> wrote:
Fritz Wuehler wrote:
In article <20250519.032550.a4e89a88@yamn.paranoici.org>
Anonymous <nobody@yamn.paranoici.org> wrote:
Stefan Claas wrote:That kind of MIME-free magic is beyond a Taiwanese who's used to use a >> > > Big5 character set, and me. So it looks as if generations of Internet >> > > programmers were wrong thinking MIME encoding is of any importance.
As you see, no MIME headers for international characters are needed. >> > >
Or does Class once again demonstrate his own incompetence in dealing
with MIME encoding by idealizing homebrew ASCII-only crippleware?
Do us all a favor and test it by yourself.
No. As we're not only interested in your success, but even more in the
reason why it works you'd better do us all a favour and explain how the
recipient of a two byte message knows that those aren't two ASCII
characters but instead it's one of the more that 13 thousand Chinese
characters from the 2-byte Big5 character table. Please enlighten us!
Go assumes UTF-8 unless told otherwise (e.g., []byte ? string).
Big5 vs. UTF-8:
Big5 needs external context (e.g., "this is Big5") to avoid ambiguity
with ASCII.
UTF-8 embeds the context in the byte patterns.
Stefan Claas <stefan@mailchuck.com> wrote:
Fritz Wuehler wrote:
In article <329a2004cb27756fe709e2cf8e882762c5b5ccf1@i2pn2.org>
Stefan Claas <stefan@mailchuck.com> wrote:
Fritz Wuehler wrote:
In article <20250519.032550.a4e89a88@yamn.paranoici.org>
Anonymous <nobody@yamn.paranoici.org> wrote:
Stefan Claas wrote:
As you see, no MIME headers for international characters are needed.
That kind of MIME-free magic is beyond a Taiwanese who's used to use a
Big5 character set, and me. So it looks as if generations of Internet
programmers were wrong thinking MIME encoding is of any importance.
Or does Class once again demonstrate his own incompetence in dealing with MIME encoding by idealizing homebrew ASCII-only crippleware?
Do us all a favor and test it by yourself.
No. As we're not only interested in your success, but even more in the reason why it works you'd better do us all a favour and explain how the recipient of a two byte message knows that those aren't two ASCII characters but instead it's one of the more that 13 thousand Chinese characters from the 2-byte Big5 character table. Please enlighten us!
UTF-8 is the default for modern protocols (HTTP, JSON, etc.).
Go assumes UTF-8 unless told otherwise (e.g., []byte ? string).
Big5 vs. UTF-8:
Big5 needs external context (e.g., "this is Big5") to avoid ambiguity
with ASCII.
UTF-8 embeds the context in the byte patterns.
In your initial posting you wrote:
| This little tutorial explains you how to run your own email
| infrastructure for family and friends, without paying a dime.
But to take UTF-8 encoding for granted is far from email standards. To
make it short you set up your own communication infrastructure following
your self-knitted rules, which is ok. But please don't call the result *email* which it definitely isn't as it severely violates RFCs!
anon <noreply@dirge.harmsk.com> wrote:
On 19 May 2025, Fritz Wuehler <fritz@spamexpire-202505.rodent.frell.theremailer.net> posted some news:20250520.010943.799d277b@msgid.frell.theremailer.net:
In article <5a30bad7e6175153eceedee9b25f02a8bb56cc01@i2pn2.org>
Stefan Claas wrote:
Fritz Wuehler wrote:
There are multi-byte character sets out there, you laughing stock. And beyond that it's inherently foolish to rely on the recipient using your default charset.
And you need MIME encoding to attach files to mail messages.
For beginners, use base64+ from me, without any MIME 1.0 headers.
https://github.com/Ch1ffr3punk/base64-plus
Regards
Stefan
So your message header contains a MIME-Version line
without any further MIME entries!? Very smart! LOL!
It's just extra lines. Who needs that?
This group more and more becomes a joke, a monkey house where standards
no longer play any role. We have to get rid of these stoned buffoons.
You don't seem to know the word innovation, right?
Stefan Claas <stefan@mailchuck.com> wrote:
You don't seem to know the word innovation, right?
We still fail to find something innovative in your work. Where is it?
Btw, to disregard standards isn't innovative, it's just plain stupid.
It uses the smtp protocol and RFCs can be replaced with newer onces.
Nomen Nescio wrote:
anon <noreply@dirge.harmsk.com> wrote:
On 19 May 2025, Fritz Wuehler <fritz@spamexpire-202505.rodent.frell.theremailer.net> posted some news:20250520.010943.799d277b@msgid.frell.theremailer.net:
In article <5a30bad7e6175153eceedee9b25f02a8bb56cc01@i2pn2.org>
Stefan Claas wrote:
Fritz Wuehler wrote:
There are multi-byte character sets out there, you laughing stock. >> > > > > > And beyond that it's inherently foolish to rely on the recipient >> > > > > > using your default charset.
And you need MIME encoding to attach files to mail messages.
For beginners, use base64+ from me, without any MIME 1.0 headers.
https://github.com/Ch1ffr3punk/base64-plus
Regards
Stefan
So your message header contains a MIME-Version line
without any further MIME entries!? Very smart! LOL!
It's just extra lines. Who needs that?
This group more and more becomes a joke, a monkey house where standards
no longer play any role. We have to get rid of these stoned buffoons.
A monkey house, because of replies, such as yours.
You don't seem to know the word innovation, right?
Stefan Claas <stefan@mailchuck.com> wrote:
You don't seem to know the word innovation, right?
We still fail to find something innovative in your work. Where is it?
Btw, to disregard standards isn't innovative, it's just plain stupid.
Stefan Claas wrote:
It uses the smtp protocol and RFCs can be replaced with newer onces.
Then do it. But as long as they are the official standard we have to
abide by them. Otherwise there'll be chaos, which means a breakdown. Or
are dysfunctional anonymizing systems what you're really aiming at?
Fritz Wuehler wrote:
Stefan Claas wrote:
It uses the smtp protocol and RFCs can be replaced with newer onces.
Then do it. But as long as they are the official standard we have to
abide by them. Otherwise there'll be chaos, which means a breakdown. Or
are dysfunctional anonymizing systems what you're really aiming at?
What do you mean by dysfunctional anonymizing systems? Tor is used by
Omnimix users, for example, to hide, because their remailers can't
protect them properly.
As you see, no MIME headers for international characters are needed.
Hello World! :-)Step 6. That's all. :-) You now have successfullyset-up >your own email
service, which is online as long as you do not power-off yourPC.
This way you can be reached, once you come home fromschool/work.
I'm retired. You left me out. The above should read:
"This way you can be reached, once you come home from
school/work/beach."
| Sysop: | Gate Keeper |
|---|---|
| Location: | Shelby, NC |
| Users: | 940 |
| Nodes: | 20 (0 / 20) |
| Uptime: | 497125:40:47 |
| Calls: | 15,886 |
| Calls today: | 11 |
| Files: | 5,345 |
| D/L today: |
4 files (8,192P bytes) |
| Messages: | 680,309 |