1. Make sure contacts / calendar entries on server are correct and up
to date – your phone will erase what it has for contacts / calendar
entries and repopulate it based on what the server has.
2. Go into the respective application (address book, calendar) and
select “options” from the program menu
3. Hold down shift key and type RSET (it is hidden so you will not see anything typed in). you may be asked a few times to
confirm, if your phone has multiple invalid sources – just keep
answering yes.
4. Exit and confirm the respective application no longer has duplicates

fail2ban is a service that continually scans your log files and bans IP addresses based on patterns you specify, such as logon failures. It then updates the firewall to block that IP address entirely. It works with anything that spits out a log file (SSH, apache, zimbra… etc..). Great for protecting against denial of service (DOS), as well as login failures for phpmyadmin, joomla, wordpress, webadmin (oft targeted web services)

It can also be expanded upon rather easily to enhance it’s use.  For example, you could centrally log addresses across multiple machines and when an IP hits the limit for failed logins (gathered from ALL your servers), have all servers block that IP address. Or, send an SNMP trap to your edge firewalls (we’re a cisco shop) to stop it from getting to your networks in the first place.

Another use would be to ban IP’s that have a high 404 count – such as script kiddies seeing if you have vulnerable software. I recommend you get an idea first of what “normal” is and to make sure you don’t accidentally ban legitimate users.

However, this is just a tool, and simply implementing this does NOT mean you can sleep soundly at night. Keep things up to date, have backups, keep an eye on your services as well as whats going on in your logs. Need some help with one of these? Just let us know

More info:

http://www.fail2ban.org – fail2ban website

http://www.debian-administration.org/articles/623 – how-to article on preventing DNS DDOS with fail2ban

Other resources:

http://www.tripwire.org – tripwire logs changes to files of specified directories (passwd file changed but you haven’t touched it? ruh-roh…)

http://www.nessus.org – security scanner, helps identify potential securities holes (packages tend to be more leaky than OS’s these days)

We are having an issue with BB syncing this morning… it appears as though some, but not all, of the BB accounts stopped synciing over the weekend… We are on it…

Thanx for your patience as we correct this issue….

Always a good free source if you think you have a virus.  Highlighted is their Housecall application.  Small app download that uses a smart scan technology.  Basically definitions sit in the cloud.  You can run a quick or full scan on an entire drive or select folders.  Also available is HijackThis application.  Great tool for the advanced tech.  Then there is RuBotted, CWShredder and RootkitBuster.  All great tools for any tech toolkit and the price is right.

You can flag a message that you write to have a return receipt message sent back to you when the recipient opens your message.  When you compose a message you select Return Read Receipt from the Options menu. The recipient can choose to return the read receipt or not.

Users set their Read Receipt Mail Preferences for messages that are flagged with a return receipt request. The following options can be set:

• Never send a read receipt. This is the default. When a message is received with a return read receipt request, the request is ignored. The recipient is not aware of the request.
• Always send a read receipt message. A return read receipt message is automatically sent when the message flagged for return read receipt is opened.
• Ask me.  Recipients are asked if they want to send the return receipt.

A return read receipt message is not sent if a recipient selects more than one message and right-clicks and selects Mark As Read.

• The return read receipt flag does not work for messages that are sent to users on systems other than Zimbra

A regression was introduced in 6.0.6 that prevented you from opening or composing e-mail in new browser window.  This also effected your ability to open an attachment of type .eml… which basically is an e-mail with another e-mail attached to it…

This issue has been corrected.  If you continue to have issues with a “new window”, please log out and log back into the web client to ensure the new code is loaded…

Thanx!

You can configure your mail options to be notified at another email address when you receive mail to your Zimbra mailbox.  This feature may be useful if you do not receive a lot of mail to your Zimbra account, but when you do receive mail, it’s important enough to require a timely response.

To set notification:

1. Click the Preferences tab.
2. Click the Mail folder.
3. In the Receiving Messages section, check Send a notification message to and enter the email address.
4. Click Save. The notification feature is enabled immediately.

Ahh… while you were all tucked in your bed we applied the next Zimbra upgrade  6.0.6.  This upgrade brings with it some great new features and bugs fixes…

Hightlights:

• You can now ADD words to your spell check (thank god, get alot of grief for this one…)
• The RSS folders, like the Zimbra Kiosk, should no longer double (Peter G. will be happy)
• The drag and drop Zimlet now works with Firefox 3.6
• Copy and paste now works when composing a message when using the Internet Explorer browser (This was another big one for one of our clients…)
• Sharing Briefcase folders publicly now works again
• Family mailboxes with child accounts now work in ZCS 6.0.x series.

The complete list of enhancements and fixes is available here.

You also notice this most references to Yahoo! have been removed.  Zimbra was owned by Yahoo! but was recently sold to VMWare so the Yahoo! branding has been removed…

Please let us know if you have any issues or questions….

Thanx!