OZLAN Technical Services

How can I change my WebMail Password?

Login at: https://www.knzhosting.com/webmail
From this location you will be able to:
  • Change Password
  • Setup 'Auto Responders'
  • Configure Mail Client
  • Email Filtering
  • Email Trace

You will also be able to Enable/Disable the automatic loading of your chosen WebMail Interface.

What is the Maximum Number of Emails Per Hour I can send?

Users accounts on our system are allowed to send a Maximum of 100 Emails Per Hour. If you have a legitimate reason for sending more than this limit, please contact support or submit a Ticket and we will happily raise the limit for you.

Which WebMail system should I use?

KNZ Hosting offer 3 different flavors of WebMail

Login at: https://www.knzhosting.com/webmail
horde: Best for old cellular devices, phones, wap capable etc.
**roundcube: Best for desktop operating systems.
SquirrelMail: Best for Tablets/Mobile devices and desktop systems (has the most features including: calendar, todo lists, notes, filtering).
**recommended, also good for tablets

Best Practices for Organizations Sending to McAfee SaaS Email Protection Customers

Any organization sending email should follow standard best practices to prevent their organization’s domain(s) from being blocked or blacklisted.

Even though there may be a valid business relationship with a sender, the McAfee SaaS Email Protection service will block (or quarantine depending upon service settings) any mail that scores as “probable spam” unless that sender’s domain or e-mail address is on one of the available Sender Allow Lists within the service – either domain or user-level.

In some cases email from an otherwise trusted sender may be blocked with a variation of a 554 error or quarantined.

If a sender receives a 554 error on a message that is being sent directly to a McAfee SaaS customer (not a reply or a forwarded message), it is probable that the sending domain or IP address has been “fingerprinted” based on recent sending habits.

Many times, upon investigation, it is found that someone from the sending domain has sent a recent email that met one or more of the following criteria that increased the spam score in our spam detection system.

- A percentage of messages were sent to invalid recipients generating a large number of NDRs. Typically when this is seen, it is taken as a possible directory harvest attack and the spam score elevates accordingly

- Messages sent were received by “honeypots”. Honeypots – or spam traps – are trusted servers around the world set up with dummy e-mail addresses that sit and wait for mail to hit. Mail hitting these servers is automatically classified as spam because the accounts tied to these servers have not been advertised or requested mail. Any mail sent is deemed unsolicited and therefore spam. Again, this is common with directory harvest attacks and the spam score of messages sent from that domain will be elevated accordingly

- Messages that were sent from the sending domain may have been reported by the recipient to their ISP as potential spam. These complaints are reported through various sources and aggregated in the spam score of all inbound messages through the SaaS Email Protection service and may affect the score enough to have the mail either quarantined or blocked. This typically will come about if the sender is not using opt-out links and/or not honoring opt-out links in certain types of messages being sent from their domain

Best-Practices for Senders

While there are no guarantees that any email message will be delivered, an organization can minimize the risk of having their outbound mail blocked by following a few simple guidelines. Among the steps an organization can take include:

- Maintain mailing lists and eliminate any and all invalid email addresses that exist
- Purchase mailing lists only from reputable organizations and do not use lists that may have been purchased more than 90 days prior to any mailing
- Include instructions for recipients to opt-out of future mailings
- Honor any opt-out requests from recipients
- Use third-party mass-mailers (Constant Contact, etc.) to send mass mailings as needed
- Activate and review outbound server logs periodically to ensure there are no unknown mass mailings being sent and that there is not an abnormal number of NDRs being generated

Possible Actions for SaaS Email Protection Customers

Customers using the McAfee SaaS Email Protection service can take any or all of the following steps to work around an issue should it arise:

- Attempt to add the sending domain to the domain-level sender allow list
- Report the issue to their SaaS Email Protection support provider and have the following information available:
o Email address of the sender
o Email address of the intended recipient
o Date of message (within past 7 days)
o Subject of message (not necessary but useful)
o Full bounce message if available

As a last resort, customers can ask the sender to attempt to resend their message WITHOUT their signature block. Many times, the messages are flagged or “fingerprinted” based on a static piece of information to identify messages coming from a sending domain. The most static piece of any messages domain-wide tends to be the signature block. Combining this as a TEMPORARY recommendation while the situation is being investigated further can sometimes allow critical messages to come through while the scoring is being investigated and potentially challenged.

NOTE: the above information is only for straight communication from sender to recipient and does NOT include scenarios relating to replies to existing messages inbound to a SaaS Email Protection customer or messages that were forwarded. These situations need to be investigated fully to identify where the problem may lie (recipient, sender, prior senders in the case of forwarded messages).

Gmail Mail Fetcher

To set up Mail Fetcher:
  1. Click Settings at the top of any Gmail page, and open the Accounts and Import tab. (For Google Apps domains, open the Accounts tab.)
  2. In the Check mail using POP3 section, click Add POP3 email account.
  3. Enter the full email address of the account you'd like to access, then click Next Step. Gmail will populate sample settings, but we recommend checking with your other provider to learn the correct server name and port. Enter your Password.
  4. Decide whether to:
  • Leave a copy of retrieved messages on the server
  • Always use a secure connection (SSL) when retrieving mail
  • Label incoming messages
  • Archive incoming messages
  1. Click Add Account.
  2. Once your account has been added successfully, you'll have the option of setting it as a custom From address. This allows you to compose messages in Gmail, but have them appear to be sent from your other email account. Click Yes to set up a custom From address.

How to change AOL Password

  1. Sign in to AOL with existing password
  2. Options (right hand top of screen)
  3. Click "My account"
  4. Click "Password change" (towards bottom of screen).
  5. Answer security question
  6. Choose new password (You will have to enter new password twice)
  7. Click "Save" (If accepted will say "Thank you, your password was changed")
  8. Go back to AOL and sign in with your Username (email address) and NEW password.

NOTE: You will have to sign out on ALL computers you check mail from (phone, laptops, tablets, work computers, etc)

How to disable the Windows Live mail sign in Window

To disable the sign in window, open Windows Live Mail and go to: The Windows Live Mail drop-down menu icon
(top left above 'Email Message' icon).
Select 'Options', then click on 'Mail' from the selection offered.
In the mail 'Options' property pages, select the 'Connection' tab and click 'Stop Signing in' from the 'Connecting to Windows Live Services' section.
Click 'stop signing in' to any warning messages. Click 'OK' to exit the 'Options' Property pages

IMAP Mail Settings for AT&T Mail

Incoming Server: imap.mail.att.net
Incoming Port: 993
SSL: Yes
Outgoing Server: smtp.mail.att.net
Outgoing Port: 465
SSL: Yes

** The username will be your full AT&T email address.

Moving emails from one IMAP server to another

  • Both of your servers must support the IMAP email protocol. All KNZ Hosting email hosting packages can connect using IMAP.
  • The password for the email account you are trying to migrate.
  • An IMAP capable local email client. Most email clients like Outlook, Apple Mail, and Thunderbird support IMAP mail accounts.
  1. Create the same email account on your new server that you had on your old server. Use the same spelling and capitalization.
  2. Give the new email account the same password that you used on your old server. You can change the password after the migration process is done, if desired.
  3. In your local email client, create two new email accounts.
  • These will both be for the same email address.
  • They will both use the same password.
  • They must both be configured to connect using IMAP.
  • The incoming server (or IMAP server) will be different for each account. You should use your access domain for your new server, and your access domain or IP address for your old server, rather than your domain name, whenever possible. This will avoid any possible DNS conflicts.
  1. With both accounts online, open up the inbox for the account that connects to your old server. Drag and drop messages from this inbox to the inbox on your new server.

That's it! If you have a lot of emails, give the accounts a few minutes to finish syncing up. Once they're done, your old emails will be in your mailbox on the new server.

Sender receives bounce message "554 Denied"

When sending an email to a McAfee SaaS Email Protection client, the sender is receiving the bounce back message “554 Denied.”
The error message “554 Denied” is most commonly caused by McAfee SaaS Email Protection Clients having rejected the message as spam. This is either due to the content of the message or the reputation of the sending IP address.
Example Error:
host domain.com.inbound15.mxlogic.net[] said: 554 Denied (Mode:normal) (in reply to end of DATA command)
For McAfee SaaS Customers, please do one or more of the following:

  1. Place the sending domain on the User or Domain-Level allow list in the Control Console. For instructions on how to do this, please consult with the Systems Administrator of your email system.
  2. Send a copy of the message to SaaS_falsepositives@mcafeesubmissions.com. If the message was blocked, the sender can obtain a copy from their Sent Items folder. Messages to this address are not filtered for spam, and all submissions are accepted.
  3. Copy full Message Audit Details showing the 554 Denied response from the Control Console and supply this in an email with a subject of “False Positive” to SaaS_falsepositives@mcafeesubmissions.com
  4. Open a service request with McAfee SaaS Technical Support so we may investigate the cause of this issue and possibly reset the filter that is causing messages to be denied.

For senders who are not McAfee SaaS Email Protection customers, please do one or more of the following:

  1. Contact the intended recipient and ask them to add the sending address or domain to their allow list
  2. Contact the intended recipient and ask them to open a service request with McAfee SaaS Technical Support so that the message can be reviewed as a false positive
  3. Send a copy of the message with the original headers to SaaS_falsepositives@mcafeesubmissions.com.Messages to this address are not filtered for spam, and all submissions are accepted.

See also the related article titled Best Practices for Organizations Sending to McAfee SaaS Email Protection Customers for additional information.