Documentation

This category contains articles relating to setup and configuration of our different products and services.

New Remote Email Forward Policy

February 6, 2024 – Beginning today, we will be ending the ability to do “remote forwards” on email accounts.   A remote forward is setup to take an email address which is local to our servers and forward it to another service.   For example, if we forwarded support@internetpro.net (which is located on our servers) to someone@yahoo.com, that would be a “remote forward”.    The problem with this is that when Yahoo! sees the email, they think it is being sent by our servers.  So, if a spammer sends an email to support@internetpro.net and we forward it to Yahoo!, then Yahoo! thinks we are spamming them.

This month, Google has put much more strict policies in place dealing with spam and as a result, emails coming through our systems are being rejected or flagged as spam by Google’s servers.   This is due to the number of remote forwards we have in place, and so we’ve had to make the decision to stop these forwards and institute a policy of not allowing them in the future.

Since Google has implemented this, the rest of the industry who haven’t already done so will quickly line up to do so as well.

Some more information about remote forwards follows for the technically curious:

Why remote forwards are bad

With the anti-spam protections in place in all modern mail servers, forwarding emails to remote servers or addresses is not recommended. The whole industry is moving away from remote forwards. As Best Practices for email server operators, remote forwarding should be disabled due to the potentially system-wide negative effects they could cause, such as backscatter and IP reputation issues.

Backscatter can stem from the remote addresses being no longer valid,  servers not being authorized to send emails for the sender’s domain, or emails being rejected by remote servers due to anti-spam policies in place at the remote site.

As more backscatter events accumulate, they will not only cause higher system load and resource usage, but will also have a negative effect on the IP reputation of the sending servers. A poor IP reputation will cause system-wide delivery issues affecting accounts on those servers. For example, if our server’s IPs are blocked or rate-limited by Yahoo! or Gmail servers, all accounts will experience delivery issues when sending emails to Yahoo! and Gmail addresses. (This is happening now. See:  https://www.netsolinc.com/gmail-blocking-email/)

Aside from the backscatter and IP reputation issues, having remote forwarding available provides a way for bad actors secretly forwarding a compromised account’s emails to a remote address without the account/mailbox owner’s knowledge. For example, if third-party site’s account verification or password-reset emails are being forwarded to a remote address, the bad actor could gain access to the compromised user’s other online accounts.

 

2024-02-06T17:30:54-06:00February 6, 2024|Documentation, FAQ, News and Updates|Comments Off on New Remote Email Forward Policy

Gmail Requiring SPF Records

We are getting more and more support requests from people having trouble sending email to Gmail and Google hosted domains.   This is currently almost always the result of an email domain not having an SPF record.  That is a fairly technical sentence, so click the link for detailed information on SPF.   The simplified version is that an SPF record specifies what servers are allowed to send email for your email address.   It was designed to help combat spam.  If you don’t have one of those records, Google is now rejecting the email with an error message similar to the one below:

–BEGIN

host gmail-smtp-in.l.google.com[74.125.195.26] said:
   550-5.7.26 The MAIL FROM domain [<your domain>] has an SPF record
   with 550-5.7.26 a hard fail policy (-all) but it fails to pass SPF checks
   with the 550-5.7.26 ip: [17.57.156.17]. To best protect our users from spam
   and 550-5.7.26 phishing, the message has been blocked. Please visit
   550-5.7.26  https://support.google.com/mail/answer/81126#authentication for
   more 550 5.7.26 information.

 

–END

In the past, Google would just send the offending message to the Spam folder, but now if the SPF record is missing or fails (as the one above), the message will be rejected.

This can also be caused by “forwards”.  For instance, if you have an email address hosted with us, but choose to forward incoming email to a personal Gmail account, you will most likely lose some email as a result of this policy.   Senders trying to reach you will receive a failure notice, but there is no way to “fix” this except to check your email in the account rather than forwarding it to another external email address.

 

2022-09-20T11:01:02-05:00September 20, 2022|Documentation, News and Updates|Comments Off on Gmail Requiring SPF Records

New Mail Server Feature!

October 20, 2015 – We’re very happy to announce the addition of a new mail server feature – Server Side Mail Rules.   This is a feature we actually had on our old mail system and we have been missing it since then, so it is great to have it back!   This feature is most useful to customers who are using Webmail or IMAP for their email.  The interface is available in the Tuxedo webmail.  Access it by choosing the Settings icon on the left and then choosing “Delivery Filters” in the section above the icons.   The interface is very similar to what you would find in most email client programs, but if you need assistance, please feel free to call us at 256-547-6817 or email support@internetpro.net.

To use these filters, you don’t have to remain in the Tuxedo interface.  Once  you have saved your rule, it will remain active all the time, so the filter will still be functioning when accessing your email through your email client like Thunderbird, Outlook, or your mobile device as long as it is using the IMAP protocol.

 

2015-10-20T23:29:50-05:00October 20, 2015|Documentation, News and Updates|Comments Off on New Mail Server Feature!

Web Form Authentication

Why won’t the form on my website send email?

 

Beginning January 1, 2015, Network Solutions, Inc. requires SMTP authentication for all form on websites.   This it to prevent spammers from exploiting web forms (like contact forms, applications, and such) to send out unsolicited email.  By using SMTP authentication, we are able to limit the number of emails a form can generate, and if one becomes exploited, we are able to stop just that form and not block an entire web server.

Most (if not all) modern email libraries support SMTP authentication.  For example, in WordPress, we recommend the “WP Mail SMTP” plugin.   Other Content Management Systems will have similar plugins and even standalone form handlers should support this protocol.  If you are a web designer and are having trouble finding a suitable library for delivering email, please contact us at support@internetpro.net.

We recommend that the web developer create an account which can be used for authentication such as webform@yourdomain.com.    This can be created using our web interface if we host the email for your domain.   If we do not host your email, please contact us, and we will be glad to create a free account to use for your web form.

Settings for the email library:

Use SMTP-Auth
Authentication type:  Plain or Login
Security:   TLS
SMTP server:    smtp.internetpro.net
Port:  587
Username:  entire email address (in our example, webform@yourdomain.com)
Password:  Your configured password (minimum 5 characters with 1 number and 1 letter)

 

2016-12-29T16:55:02-06:00December 17, 2014|Documentation, FAQ|Comments Off on Web Form Authentication

Whitelisting Emails in Mail Settings

This documentation only applies if you are using the Normal with Quarantine template for spam filtering.  If you are using other templates, your spam messages will not be quarantined in the spam folder.
To add quarantined senders to your whitelist follow these steps (the numbers on the arrow correspond to the step number):

  1. Click on Spam Management – it will expand as shown in the screenshot below after you click it.
  2. Click Quarantined Mail
  3. Put a check mark next to the message(s) which are legitimate mail  you want to receive
  4. Click the “Deliver selected messages normally” button.   The sender of the email(s) will be added to your personal whitelist, so that sender’s email will never be quarantined or blocked as spam again!

Mail-Settings

2014-12-11T20:29:17-06:00December 11, 2014|Documentation|Comments Off on Whitelisting Emails in Mail Settings

Signatures in Tuxedo Webmail

When using webmail, you may want to have a signature automatically append to your messages.  These are the instructions for accessing/managing signatures in the Tuxedo Webmail,

 

To access your signature and set or change it follow these steps as shown in the screenshot below:
	1 - click on Settings on the bottom left
	2 - click on Identities at the top center of the screen.
	3 - click on your email address on the top left
Signature1



To set when your signature is used, follow these steps as shown in the screenshot below:
	1 - click on Settings on the bottom left
	2 - click on Composing Messages
	3 - set when you want your signature to be used

Signature2
2014-12-11T17:33:35-06:00December 11, 2014|Documentation|Comments Off on Signatures in Tuxedo Webmail

Whitelisting Emails in Webmail Lite

This documentation only applies if you are using the Normal with Quarantine template for spam filtering.  If you are using other templates, your spam messages will not be quarantined in the spam folder.
To add quarantined senders to your whitelist in Webmail Lite follow these steps:

1) First, click the spam folder to show a list of messages which have been quarantined as spam.

legitimate-webmail

 

2)  Click the legitimate email to view it.   Above the body of the email, you will see an “Allow Sender” button as in the screenshot below.  Click that button.

legitimate-webmail2

 

That’s it!   The email will automatically be moved from the spam folder and back to your Inbox.  The sender of the email will be added to your personal whitelist, so that sender’s email will never be quarantined or blocked as spam again!

 

2014-12-11T19:56:51-06:00December 11, 2014|Documentation|Comments Off on Whitelisting Emails in Webmail Lite

Whitelisting Emails in Tuxedo

This documentation only applies if you are using the Normal with Quarantine template for spam filtering.  If you are using other templates, your spam messages will not be quarantined in the spam folder.
To add quarantined senders to your whitelist using the Tuxedo webmail, follow these steps:

1) First, click the spam folder to show a list of messages which have been quarantined as spam.

legitimate

 

 

2)  Click the legitimate email to view it.   Above the body of the email, you will see an “Allow Sender” tab as in the screenshot below.  Click that link.

legitimate2

 

That’s it!   The email will automatically be moved from the spam folder and back to your Inbox.  The sender of the email will be added to your personal whitelist, so that sender’s email will never be quarantined or blocked as spam again!

2014-12-11T19:57:41-06:00December 11, 2014|Documentation|Comments Off on Whitelisting Emails in Tuxedo

New Email System

We are bringing the new email system online around 11:00am CST on 12/9/2014.   We are bringing it online during the day instead of during a maintenance window so that we can better troubleshoot issues while people are using their email instead of possibly missing messages in the middle of the night when people aren’t using the system.    Also, we’ll have a full staff available to address any problems which may arise.

Fundamental Change in Dealing with SPAM

The new system brings with it a fundamental change to the way we deal with spam.   In the past, we have tagged messages our system thought were spam with *****SPAM***** in the subject line.   The idea was to leave filtering of the spam to the end user.   However, as global spam volume has increased, people are wanting to just not see spam at all.  Also, devices such as phones and tablets have become more prevalent and those devices generally don’t have good filtering capabilities built in.   So, the new system will concentrate on just keeping spam out of your inbox completely.   Spam messages will now be rejected back to sender by default.

What This Means to You

You will now be able to maintain your own “whitelist” (list of email addresses whose email you always receive) and “blacklist” (list of email addresses you always block).  Using these lists, you will be able to “tweak” your Inbox so that you receive very little spam.   We are also providing templates which will allow you to be more or less aggressive in your spam blocking – more aggressive if you want a cleaner Inbox and less aggressive if you want to insure nothing is ever missed by accident.   You can also set up a “quarantine” which is like a server-side junk folder to hold email which our server thinks might be spam.   However, we recommend you only use this quarantine to perfect your rules so you no longer even have to check that folder.   Messages which are quarantined will automatically be removed by the server after 14 days.

Known Issues with Migration

We’ve been working hard to make the migration as seamless as possible and to minimize downtime.  However, with any large change like this, there will be some issues.  Some of those issues we know about and some will be unforeseen.  Issues we do know about are:

  1. Webmail-based address books aren’t going to automatically transfer over.  If you have a large address book stored in the webmail, please drop us a line at support@internetpro.net and we will move it for you.   Please let us know if the address book is stored in the webmail located at https://webmail.internetpro.net or the one at https://mail.internetpro.net (Legacy).
  2. There will be an increase in spam email when the server first comes online.   We have relaxed our spam rules so that we can address any delivery issues which may arise from the new server.  We will be tightening those rules again as soon as we are sure everything is running smoothly.   Please bear with us during this transition as it will be worth the trouble!

 

We will be continuing to post more updates and documentation as we get closer to the Go Live time, so please keep checking our website.

 

2014-12-08T18:07:25-06:00December 8, 2014|Documentation, Internet, News and Updates|Comments Off on New Email System

NetSol Cloud Desktop Client Updated

The desktop sync client for NetSol Cloud has been updated.  If you already had the latest client, you probably already know this as the client would have alerted you to the available update.  The update mechanism in this new version is improved and will do future updates automatically (depending on OS version).   See below for more details and for information on other changes:

  • [Feature] Provide information about the current connection’s encryption and SSL certificate chain in the account dialog
  • Handle Windows LNK files correctly  (these are shortcut icons)
  • Detect remove and renames in read only shared and restore removed files there
  • Preserve permissions of local files
  • Apply network limit changes to active sync run
  • Several bugfixes

 

For the autoupdater in the new version, see below for descriptions of the feature as pertaining to your operating system:

Windows

ownCloud client will check for updates and download the update if one is available. You can view the status under Settings -> General -> Updates. If an update is available and has been successfully downloaded, ownCloud Client will start a silent update prior to its next launch and then start itself. If the silent update fails, the client offers a manual download.

The user needs to be able to attain administrative privileges to successfully perform the update.

Mac OS X

If a new update is available, ownCloud client will ask the user to update to the latest version using a pop-up dialog. This is the default for Mac OS X applications which use the Sparkle framework.

Linux

Since distributions provide their own update tool, ownCloud Client on Linux will not perform any updates on its own. It will, however, check for the latest version and passively notify the user (Settings -> General -> Updates) if an update is available.

Preventing Auto Updates

In controlled environment such as companies or universities, the auto-update mechanism might not be desired as it interferes with controlled deployment tools and policies. In this case, it is possible to disable the auto-updater entirely:

Windows

There are two alternative approaches:

  1. In HKEY_LOCAL_MACHINE\Software\ownCloud\ownCloud, add a key skipUpdateCheck (of type DWORD) with the value 1 to the machine. This key can be manually overrideen by the same value in HKEY_CURRENT_USER.
  2. In HKEY_LOCAL_MACHINE\Software\Policies\ownCloud\ownCloud, add a key skipUpdateCheck (of type DWORD) with the value 1 to the machine. Setting the value here cannot be overridden by the user and is the preferred way to control the updater behavior via Group Policies.

Mac OS X

You can disable the update check via a system-wide .plist file located at /Library/Preferences/com.owncloud.desktopclient.plist. Add a new root level item of type bool and the name skipUpdateCheck and set it to true. You can also just copy the file owncloud.app/Contents/Resources/deny_autoupdate_com.owncloud.desktopclient.plist` to /Library/Preferences/com.owncloud.desktopclient.plist.

Linux

Since there is no updating functionality, there is no need to remove the check. If you want to disable the check nontheless, open a file called /etc/ownCloud/ownCloud.conf and add the following content:

[General]
skipUpdateCheck=true
2014-03-27T16:42:19-05:00February 14, 2014|Documentation, NetSol Cloud, News and Updates|Comments Off on NetSol Cloud Desktop Client Updated
Go to Top