Hey Jason,
I had a quick look at your notes and had few lines of "gnarf cringe -
why?". I will try to go over them:
- Ubuntu for Win10 - uhm, ok, although I guess it's possible to run
James on a virtualized Ubuntu on top of a Win10 - a desktop OS isn't the
best choice for a server - so either running a Linux native or at least
use a Windows Server as host OS
- sudo reboot - why you keep rebooting the entire system just for a few
configs and such? this shouldn't be needed at all
- sudo in general - you keep doin much as root - all can be done as
normal user - only start up of james require root as the ports used by
james are below 1024 - wich are the so called "well known ports" wich
require administrative privileges - even on Windows - you should change
to just set up a normal user from the start and do all in that lower
priv context
- extract of lib jar - this bothered me since you first wrote it here on
the list: why you want to extract a lib jar? If you want to build
something against it you just have to add it to the classpath at compile
time - no need for extracting
- manual download of java runtime - also not needed on most Linux
distributions as almost any of thier package managers are able to just
install different versions aside from mostly java is installed by
default at os install
- mysql and mysql-connector: although should still be useable most
distributions switched to MariaDB due to Oracle (wich bought Sun wich
bought MySQL) changed lincese so re-distributing MySQL by Linux isn't as
easy as before - so most switched to MariaDB as its license complies to
re-distribute it within the repos - I once had a week long heavy trouble
cause an update completely crashed my james database - had hard time to
recover it
- ant - yes, it's always better to use a build system nowdays - but just
to compile a single class most java devs would just do it on command
line - your notes are written like ant would required
- use of third party to generate keypair - first rule of security: never
rely on others to generate keys - always do it by yourself - why: cause
you can't be sure that the third party is trustworthy / stores the
private key - this chapter should be complete reworked to generate the
key and signatures on the command line instead of using external services
Overall its maybe a personal note on how you did it - but it's not
really useable as "general tutorial", wich is covered on apache itself.
You only combined a few things like setting up SPF and adding DKIM to a
normal James setup.
Matt
Am 17.07.2019 um 11:21 schrieb Jason Tjankilisan:
Hiya Matt,
Here is the Github link to the tutorial I created :
https://github.com/JasonTjankilisan/James-3.3.0-setup_tutorial
Firstly I apologize if there;s any wrong word or bad English. I hope the
tutorial were clear enough even for those who just learned about James, as I
try to make the information as general as it can be. any Comment/Critique are
welcome !
Thank you for the help and response.
Sincerely, Jason.
Sent from Mail for Windows 10
From: cryptearth
Sent: Tuesday, July 16, 2019 2:55 PM
To: server-user@james.apache.org
Subject: Re: Applying JDKIM and SPF to the Mailets
Hey Jason,
I don't know about Google Drive and maybe files get unavailable after
some time. If you already have a GitHub account I would recommend you to
maybe set up a new repo and publish it this way. This would ensure a
general availability and also space for additional resources like
examples. Also, the issue and merge functions would allow others to
point out issues and possible fixes. About the format: text, html and
PDF are good formats, where text and html offer easy editable where PDF
would require re-exporting one from what ever source format.
Looking forward to read it.
Matt
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
