I still had such a TP-Link router in my vaults which once contributed usage metrics to the SamKnows EU project. Since I don’t want to operate it any longer, I thought of changing the router firmware to either the original TL-WR1043ND or a DD-WRT firmware.
This link provides a great walkthrough how to get it done:
Unfortunately it turned out that my MacBook doesn’t have telnet available anymore, after the upgrade to MacOS Catalina. Thus I had to install it first and chose to compile telnet from source for the MacOS Catalina:
If I were just to install DD-WRT from the original firmware of the TL-WR1043ND V1.8 I would probably go after this description:
Everything went smoothly, now after updating I can reach the TP-Link router via web interface and first should enter a new root password for security.
Scrollout F1 is my major defence against all incoming spam waves. Using it for quite some time now, easily hosted at Hetzner, I have tweaked around some of the settings. Here I will document the change I needed to make to send email from my Mac OS infrastructure outgoing through the Scrollout F1 appliance.
Unfortunately, after updating the Scrollout Appliance once again (by entering
I ran into the following error when trying to send email:
I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can delete your own text from the attached returned message.
The mail system
<email@example.com>: host my.mailserver [10.20.30.40] said: 530-5.7.0 Must issue a STARTTLS command first 530 5.7.0 For assistance, see Admin or contact +49351XXXXXXX. Please provide the following information in your problem report: Time: (Mar 09 22:24:08), Client: (192.168.30.40), Server: (my.mailserver). (in reply to MAIL FROM command) Reporting-MTA: dns; my.mailhost X-Postfix-Queue-ID: AFDDA182DF3F0 X-Postfix-Sender: rfc822; me@myaddress Arrival-Date: Sat, 9 Mar 2019 22:24:07 +0100 (CET)
The solution was a bit quirky, but I at least found out, that this problem can be resolved by changing a setting in main.cf of postfix. The line
would have to be changed into
Once I changed it, the sending out of email did work again. Until, I used the Scrollout F1 frontend to change some settings. Then I was back at the start because postfix was running with TLS security level ENCRYPT again. So I thought that somewhere in F1 the defaults must be buried, and voilá, I found the following:
Since I moved my Promise Pegasus storage to the new Mac (which still runs High Sierra), I had to find a way to use Time Machine from my old MacMini. The old one still runs El Capitan. I read about the new File Sharing feature and created a folder which was shared and had under „Advanced Options“ the „Share as a Time Machine backup destination“ turned on. Still, I couldn’t select this target folder on my old MacMini.
After reading the discussion at apple.com, I thought I should enable AFP too, which I had disabled before. Then it looked like this:
As the Apple Discussions article described, you should connect to the Backup folder via AFP. But Finder (Command+K) wouldn’t allow me to do so. So I found out that I didn’t have AFP enabled at all, you have to select it in the major window for File Sharing as you can see in the following screen shot:
Thus I went to „Options“ and enabled both SMB and AFP to allow my old MacMini with MacOS El Capitan to use the TimeMachine feature from MacOS HighSierra (or Mojave in the near future).
After enabling AFP, I was able to connect to the shared folder and afterwards select the folder from the newer MacOS to backup my older MacOS based MacMini.
Today I set up my system with Mac OS High Sierra and again encountered issues while using my Kyocera printer to scan to a folder on my Mac.
The initial steps were to enable file sharing via SMB (without encryption!) and then set up the Kyocera as discussed in several blogs.
Finally when it was working, I noticed that it would save everything under the username I have chosen, but all other users were not able to open the scanned files. So, that was the typical user – group – rights issue in a SMB connection. What solved my issue was posted on a website and reads:
Firstly enable ACL permissions for SMB shares with the following command.
I had shared this family calendar and forgotten about it … until I used it again to enter several appointments. Unfortunately, one family member thought that was a mistake and they had to be deleted. Which let me scratch my head, how I could restore those calendar entries either on Mac OS or in iOS.
First, I remembered that the calendar affected was an iCloud calendar. Second, Google delivered the following KB article upon searching:
And yes! This worked flawlessly. I was able to fetch a backup from just after midnight (12:35 AM, at first got afraid that no backup was available, until I checked that 12:35 AM is right after midnight, here in Germany we would say 0:35 hrs … ) and restore the calendar content. That worked and I had all my appointments back. Easy, wasn’t it?
PS: If your lost entries were not from an iCloud calendar, then you might try this solution:
So I am still running Mac OS El Capitan Server Edition on my Mac Mini. Recently, the Spam that comes through, has increased again and I wondered if there is any mechanism to implement AntiSpam in Mac OS X.
The Apple Knowledge Base only gives this article:
which is not exactly what I wanted.
Looking further, I came across these links, which proved helpful at the end:
When running spamtrainer now right away, it complains:
Either there is no mailbox called No GUID found for user: junkmail in the mailpartition or it has never been fed with mail.
Either there is no mailbox called No GUID found for user: notjunkmail in the mailpartition or it has never been fed with mail.
So I go an create those users. Starting the Server.app plus adding the needed network accounts „junkmail“ and „notjunkmail“. Further I edit access so that these accounts only have access to the Mail service. Now I add these accounts to Mail so that I have access to them.
Now, finally, when I run
it does what it should.
Using the install option I can also have it run as plist item.
>> /usr/local/sbin/spamtrainer -i
Checking if there is a startup item for 'learn_junk_mail' or 'spamtrainer'
There IS a plist for sa_learn.pl
... and it is ENABLED
If you want to use 'spamtrainer' it is RECOMMENDED that this be disabled
Would you like me to disable it for you (yes/no)
'learn_junk_mail and/or sa_learn.pl' item has been disabled'
You can ignore 'No such process' error messages
There IS NO plist for spamtrainer
if you want to use 'spamtrainer' it is recommended that this be added
Would you like me to enable it for you (yes/no)
What time would you like spamtrainer to run (24-hour format)?
Please enter the hour (1)
Please enter the minutes (0)
Would you like SPAM/HAM messages to be deleted after the learn process? (n)
Would you like to log bayes stats into /var/log/spamtrainer.log? (n)
If you would you like to have spamtrainer mail you a report after it runs, then please enter an e-mail address. Enter for no (n)
Enter name of mail store with SPAM/HAM mailboxes? Enter for default (default)
Enter name of mailbox with SPAM? Enter for default (junkmail)
Enter name of mailbox with HAM? Enter for default (notjunkmail)
A plist with the following parameters for 'spamtrainer' has been prepared
/usr/local/sbin/spamtrainer -m firstname.lastname@example.org -d -l
It will run each day at 05:00:00
Would you like to add and enable it? (yes/no)
The following launchd plist item for 'spamtrainer' has been enabled'
/usr/local/sbin/spamtrainer -m email@example.com -d -l
It will run each day at 05:00:00
That is all for installation, now let me see if it does what it should!
For my iPhone I just love Readdle’s App called Spark. On MacOS I am still clinging to Apple Mail. Since all my Mail is stored on my Mac Mini MacOS server, I also work with server based folders. Here I noted a discrepancy between Apple Mail and Spark, because both programs use different presets for saving mail on the server. Fortunately I came across this websavers article, how to get both to work together smoothly.
Apple Mail defaults to a sent mailbox/folder named „Sent Messages“. If the option to „Store sent messages on the server“ is active it will create a folder called „Sent Messages“ on the server and use that folder to save copies of sent messages. This conflicts with many other applications with use the folder „Sent“ instead.
As I am not yet on Sierra, the second part of the article did it for me:
Select the „Sent“ folder on the server (in the folders pane on the left) by clicking on it once. It should *not* be at the top of the page next to Inbox/Drafts/Junk/etc, nor should it be under „Local Folders“ or „On My Mac“. It will be found under a heading indicating that it’s a server-side folder. For example, my heading says „Websavers“ as it’s my Websavers email account.
If you do not see a server-side heading in the folder list or if you do and there is no Sent folder there then you must create a new folder by choosing the Mailbox menu, then „New Mailbox“. For the Location field, you must select the correct account to create it under, then set the name to „Sent“.
Chose Mailbox from the system menu at the top of the screen
Choose „Use this Mailbox as“ > and then choose „Sent Mailbox“.
Ok, if you would like to go from there – no problem. But if you would like to install this license on another Mac it gets a bit difficult to acquire the installation kit.
I thought I would download it from the regular Kaspersky website, but unfortunately – the Parallels license key doesn’t work with the regular download package.
I contacted Parallels about it and got a confirmation for this behaviour:
The parallels code can only be used with a Parallels versions of Kaspersky, it cannot be registered with a trial version. The Parallels version of Kaspersky can only be downloaded from Parallels‘ servers. There is no external download source.
An error reading „Cannot Connect Using SSL“ on my iPhone caused me some extra grey hair: The symptoms I observed since mid of December were:
iOS Mail came up with a SSL error when trying to negotiate SSL/TLS through the IMAP service on my MacOS server. Adding a new mailbox was not possible, Apple Mail always suggested to turn of SSL (which I didn’t want to do for good reason).
My Squirrelmail webbased email reader suddenly couldn’t connect to the IMAP mailbox anymore. The error observed was: „Error connecting to IMAP server: <server_name>. 0„
First I thought that there was a problem with the MacOS Server, but when I switched to a self signed certificate – things worked OK again (only with the hint that I use an untrusted cert of course).
After some more googling around for the symptoms I observed, I came across this article Lists of available trusted root certificates in iOS (in German). It clearly mentions, that from December 2016 onward, the certificates of StartCom (which were available also cost free) are not recognized anymore. Now, my MacOS Server did not throw any error in the Server Manager, but the services didn’t work as expected anymore.
echo 'fsockopen("tls://yourmailserver.domain",993,$errno,$errmsg,15);'|php -a
I used it to check the connection to my mailserver, and look and behold, I got to see the PHP error that I had a certificate issue!
So I decided to order a RapidSSL certificate to replace the StartCom certificate. Said and done, set it all up, and voilá – all services are running smoothly again.
While the Server App correctly changes certs for all services including the postfix Mail service, I have configured TLS manually in the postfix main.cf as this was a requirement for my outbound mail forwarder. These configuration statements I always have to change manually when updating the certificate. Now there is at the end of the file: