Step 4 — Setting up Fetchmail
The Fetchmail Panel
Fetchmail is useful for people who have many other POP or IMAP servers that they read mail from. Fetchmail can be set up to check these other POP or IMAP servers periodically and download all that mail, consolidating them into one single mailbox on the local server.
To set up Fetchmail, go to the Fetchmail tab, click the + button to add a POP or IMAP server to fetch mail from, enter the server name, choose the protocol, e.g., POP3 or IMAP, enter your user ID and password at this server, and your user name on your local server.
Leave the Keep column as NO to fetch all messages from the server and delete them after downloading.
If you set Keep to YES, then they're left on the server, but Fetchmail attempts to figure out which messages are new and tries to download only the new ones. If this doesn't work well, leave Keep as NO.
Leave SSL to NO, unless your ISP requires the connection to be over SSL.
If you know that the ISP server is a POP3 server, it helps to set the protocol explicitly to POP3 rather than to leave it as AUTO.
The default polling interval is one minute and the default time-out is 45 seconds. Set to 0 for no timeout, though this is not recommended.
The Via field is optional. It can be made to contain the DNS name of the ISP POP or IMAP server. If set, this will override the Server Name field. Now why would you want to do that? You may have several accounts polling the same ISP mail server. If you enter the ISP server name into the Via field rather than the Server Name field, you can use the Server Name field merely as a label, a descriptive name for each account set-up. The Via field is optional. It's for people whose existing Fetchmail setup already uses a Via parameter. You can choose to ignore it if you want.
Leave the Node and Aka fields empty, unless you want to set up Fetchmail to work in multi-drop mode whereby mail from one single mailbox at the ISP server is split by Fetchmail into multiple mailboxes at the local server.
Fetchmail in Multi-Drop Mode
Typically, multi-drop mode works this way. The ISP provides you with an account or node on the server, say node.isp.net. Your web server is at www.node.isp.net and you can get mail delivered to firstname.lastname@example.org, email@example.com, etc... When you need to read those mail, you log in to the ISP server as user name "node" and give your password. But user1 and user2's mail are all in the same mailbox.
What you want to do is to get Fetchmail to do the logging on for you, and download all those mail, but split them into individual mailboxes that you have created on your own server for user1 and user2, etc.
Then your users will log onto your local server and read their mail (coming down from isp.net) as if these had been sent to the local server all along.
Fetchmail in multi-drop mode needs a couple of hints to help it on its way.
First, you will need the node name. In Fetchmail parlance, this would be the localdomains parameter. In our example, this will be "node.demon.nl", i.e., the right hand side of the @ sign in the email addresses you've been given by the ISP.
Then you may need to enter the other names that the ISP POP or IMAP server is known by, also known as the aka paramter. You can find this out by doing a "dig +short MX pop.isp.net" in the Terminal, where pop.isp.net is replaced by the POP or IMAP server you need Fetchmail to download the mail from. By giving more information about what likely names the ISP mail server may be known by, it can help Fetchmail figure out, from the mail headers, where each message should be delivered to on the local server.
Then you enter the localdomains and aka parameters into MailServe's Server Options field, as shown above.
To start Fetchmail, make sure its check box is on and click on the Restart Mail Server button the top right-hand corner of the panel. Make sure that the Fetchmail status light turns green. If not, check the Fetchmail log in the Mail Log panel for clues as to what could have gone wrong.
The serial number & download link will be displayed in the browser after payment, and will also be sent via email.
Also, I’m still updating the MailServe for Monterey documentation.
MailServe for Monterey
Please provide the email address you used to purchase the product, together with its serial no:
This is a Universal "fat binary”, with both ARM and Intel “slices”.
This is a Universal "fat binary”, which will install HomeBrew and Letsencrypt Certbot in /opt/homebrew-cutedge in either ARM or Intel versions.