Connectivity Issues…

Thursday, 2. January 2014 20:59

West coast Zimbra servers are unreachable right now..  we are aware and working to correct the problem…

Hang tight…

**UPDATE:  All better… upstream routing issue… lasted about 5 min…

Category:Uncategorized | Comment (0)

Zimbra Upgrades 8.0.6

Friday, 20. December 2013 23:09

Look here for the status of the upgrades as we move through them this weekend.

Please refer to the announcement e-mail sent earlier in the week for details.


Friday

UPDATE 11:10 PM EST: Upgrades started on zim5 and zim6

UPDATE 12:40 AM EST: zim5 and zim6 all good!

Saturday

UPDATE 1:00 AM EST: Upgrades started on zim7

UPDATE 2:55 AM EST: zim7 all good!

UPDATE 9:55 AM EST: Upgrades started on zim4

UPDATE 10:50 AM EST: zim4 all good!

Sunday

UPDATE 5:35 AM EST: Upgrades started on  zim3 (Late start, backup ran long)

UPDATE 8:05 AM EST : zim3 all good! (damn… missed our window…)

UPDATE 11:10 PM EST: Upgrades started on zim2

Monday

UPDATE 1:30 AM EST: zim2 all good!

All upgrades for all servers complete!

 

 

 

Category:Uncategorized | Comment (0)

Druva Server Down for Upgrade

Wednesday, 4. September 2013 18:16

The Druva server will be down for a bit as we back it up and upgrade it.  So if you have a scheduled backup happening, your client will complain, but will pick up once the server is back online…

All clients have a good 9/4/13 backup.

Category:Uncategorized | Comment (0)

Zimbra (Zim2) Maintenance this weekend.

Friday, 23. August 2013 8:28

This Zimbra e-mail system will be unavailable from approximately 11PM EST till 1AM EST this Saturday night into Sunday morning (8/24 – 8/25) for a significant upgrade.

We are doubling the memory and disk space of the machine as well as upgrading from Zimbra 7 to Zimbra 8.  Both changes will bring significant performance and feature enhancements.
Please check back here for progress updates during the upgrade and you can check here to see the up/down status (Zim2) of the server.

**Update: Not starting process to earlier in the morning, backup running longer than we expected… look for server down time 3am-5am.

 

Category:Uncategorized | Comment (0)

Increase Zimbra Attachment/Upload size

Tuesday, 18. June 2013 8:58

Ok.. love Zimbra, but sometimes finding answers to simple questions can be a bit daunting since there are so many “systems” working together…

So the question: increase the attachment size from default of 10m to 40m, lots of people with different answers… the simple:

$ zmprov modifyConfig zimbraMtaMaxMessageSize 41943040
$ postfix reload

from what looks like the “official” doc here didn’t work for me…

zimbra@zimbra:~$ postconf message_size_limit
message_size_limit = 41943040

Reported the right size, but still could not upload larger attachments.

So, I’m not sure if all these commands are necessary, but did the following and everything worked on two 8.0.3 severs:

zimbra@zimbra:~$ zmprov ms `zmhostname` zimbraFileUploadMaxSize 41943040
zimbra@zimbra:~$ zmprov ms `zmhostname` zimbraMailContentMaxSize 41943040
zimbra@zimbra:~$ zmprov mcf zimbraMtaMaxMessageSize 41943040
zimbra@zimbra:~$ postfix reload
postfix-script: refreshing the Postfix mail system
zimbra@zimbra:~$ postconf message_size_limit
message_size_limit = 41943040

Category:Zimbra | Comments (1)

Zimbra2 down for Maintence

Saturday, 8. June 2013 23:10

Z2 will be down from approx 11:30pm EST til 1:00am EST tonight for some maintenance….

Thanks for your patience…

 

Category:Zimbra | Comment (0)

web1 outage…

Monday, 3. June 2013 15:17

web1 suffered from a runaway process that rendered several web sites very unresponsive today from approx 3:25PM EST to 3:50PM EST….

We apologize for any inconvenience…

As a sidebar, the restart we had to issue to gain control back from the node ruined a string of 783 days of uptime for that node… oh well…

Please contact me with any questions….

Category:XEN, Zimbra | Comment (0)

sshfs “read: Connection reset by peer” issue

Monday, 8. April 2013 12:21

Ok.. juts going to post this since I just wasted 2 hours of my time with this, part of which was reviewing countless post of how to fix this issue, none of which either pertained to my situation or worked….

So…

You got a box you ssh with keys to every day no issue…  and you are like, “Hey, I’d like create a mount to make it easier to work on that box”, you use sshfs with the same credentials/keys and you simply get:

read: Connection reset by peer

Ok, you turn on debugging and the like.. no clues..  and proceed to waste 2 hours goggling like I did….

This is what was doing it for me.. relative vs. absolute paths to key and mount point… either missed it in the man page or whatever…

Where as this did not work:

sshfs <user>@<host>:. ./pick/ADR -o IdentityFile=.ssh/<key> 
-o ServerAliveInterval=60 -o Port=2322 

This does:

sshfs <user>@<host>:. /home/<user>/pick/ADR -o IdentityFile=/home/<user>/.ssh/<key> 
-o ServerAliveInterval=60 -o Port=2322

(both examples moved to 2 lines to fit better.. there obviously is no linefeed mid command…)

I’m sure there is a good reason why this user space tool requires an absolute path… but…

Hope this helps…

Category:Linux | Comment (0)

Easter Zimbra Upgrades

Saturday, 30. March 2013 17:59

Several of our Zimbra servers will be getting software and/or hardware upgrades this weekend…

Downtime should not be longer then :30 and will not interrupt incoming mail,  just your ability to “get” it…

Thanx for your patience and we hope you enjoy the upgrades!

Category:Zimbra | Comment (0)

Zimbra Searching

Friday, 8. February 2013 10:47

We receive alot of complaints about the search capability of the Zimbra web client, but the truth is, is that it is an extremely powerful tool, if you are willing to make a small investment in learning the query language.

Most of what can be done with the query language can be done under the “Advanced” button next to the search box, but it can be slow to build a query with the  GUI…

So.. look below and learn a few “verbs” and that blank search box can become very powerful friend

All of this can be viewed here.

Query language description

This advanced topic describes in detail the search grammar used for Zimbra ‘s Search feature. Some type of query is always applied to produce the view that you see in the interface.

Search Language Structure

Simple searches can be done by just entering a word into the search field. Bare words (words without a search operator) are interpreted to search in the ‘content:’ operator — this matches any text in the message.

More advanced searches can be done by specifying a search operator. A search operator is a special keyword followed by a colon, followed by some other parameter specific to that operator. For example:

  • in: inbox the operator is “in” and the parameter is ” inbox” – this returns messages which are in the folder named ” inbox”
  • from:someone the operator is “from” and the parameter is “someone” – this returns messages which have the word “someone” in their email address

You can prefix any keyword with the word “not” to specify items that do not have that criterion, for example not in: inbox. Search is not case sensitive, meaning that “in:inbox” is the same as “in:Inbox”. The minus sign (-) is a synonym for NOT So: not in:inbox is the same as -in:inbox

In most cases, it is not necessary to include punctuation-type characters in your search string, as these are ignored by the search code. There are certain times where this is not true (for example, searching for a time ’9:30′ in a message) and in those cases you should enclose the search parameter in quotation marks. For example: subject:”9:30″ will return messages which have the string 9:30 in the subject.

Allowable characters in the search parameter:

  • The following characters cannot be anywhere in a search parameter unless it is enclosed by quotes: ~ ‘ ! # $ % ^ & * ( ) _ ? / { }[ ] ; :
  • The following characters are allowed in a search parameter as long as they are not the first character: – + < >

Note: Special characters, such as trademark symbols that are part of a word, are removed when the word is indexed for search. They are ignored in a search. For example, a search for Zimbra™ finds all references to Zimbra, including those without the trademark symbol.

Multiple Search Terms

If multiple search terms are entered (separated by spaces), they are ” ANDed” together by default. in:inbox tim means “return me messages which are in the inbox AND which have the word tim in them”. For searches using multiple criteria, you can either find items that match one of the specified criteria or all of them. You can perform both types of searches using the Advanced search builder.

For all search panes other than the Basic search, the rules are:

  • Searching for messages that match any of the specified criteria is called an ‘OR’ search, because if the message contains either X or Y, then it is considered a match. For Advanced search panes with multiple check boxes, making multiple selections within a single pane creates an ‘OR ‘search for those items.
  • Searching for messages that contain both X and Y is called an ‘AND’ search, because the message must meet all the specified criteria in order to be considered a match. For Advanced server panes with check boxes, opening multiple instances of the same pane and making different check box selections in each one causes the criteria to be specified as an ‘AND’ search.

Only “OR” appears in a query. If you selected as an option to show the search query in the Search bar as you make selections in the Advanced search, the Search text box updates to show the resulting query. With the ‘AND’ type of search, the word ‘AND’ does not appear.

Tip: Using parenthesis with AND and OR. Words within parentheses are considered as a unit. For example from: (john thomas) is equivalent to from:john AND from: thomas. If you use OR in the parenthesis,from:(john or smith), the search is for results from:john OR from: thomas.

Using * as a wildcard in Search

The asterisk (*) can be used as a wildcard at the end of a word in a search to find content that contains words that have similar spellings.

Use the asterisk * as a wildcard. For example, the search string do* returns items such as dodogdoor, etc.

Note: A double-byte asterisk sign in a search query is not considered a wildcard character and is ignored when the search runs.

Keyword Descriptions and Examples

content:

Specifies text that the message must contain. For example, content:bananas finds all items containing the word “bananas”.

from:

Specifies a sender name or email address that is in the From header. This can be text, as in “John Smith III”, an email address such as ” joe@acme.com”, or a domain such as ” zimbra.com”.

to:

Same as from: except that it specifies one of the people to whom the email was addressed in the To: header.

cc:

Same as from: except that it specifies a recipient in the Cc: header of the message.

subject:

Specifies text that must appear in the subject header of the message. An example might be subject:new vacation policy.

in:

Specifies a folder. For example, in:sent would show all items in your Sent folder.

has:

Specifies an attribute that the message must have. The types of object you can specify are “attachment”, “phone”, or ” url”. For example, has:attachment would find all messages which contain one or more attachments of any type.

filename:

Specifies an attachment file name. For example, filename: query.txt would find messages with a file attachment named ” query.txt”.

type:

Specifies a search within attachments of a specified type. The types of attachment you can specify are “text”, “word”, “excel”, and ” pdf”. For example, type:word “hello” finds messages with attachments that are Microsoft Word documents and searches within those attachments for the word “hello”.

attachment:

Specifies any item with a certain type of attachment. For example, attachment:word would find all messages with a Word file attachment.

Note:  If you did not find an attachment that was written in a non-western language, see Search Issues with Non-Western Language Attachments.

is:

Searches for messages with a certain status. Allowable values are “unread”, “read”, “flagged”, ” unflagged”, “sent”, “draft”, “received”, “replied”, ” unreplied”, “forwarded”, unforwarded”, “anywhere”, “remote” (in a shared folder), “local”, “sent”. For example, is: unread will find all unread messages.

date:

Use this keyword to specify a date, using the format that is default for your browser’s locale (for US English the format is mm/ dd/ yyyy). For example, date:2/1/2010 would find messages dated February 1, 2010. The greater than (>) or less than (<) symbols can be used instead of after or before. >= and <= are also allowed.

after:

Specifies mail sent after a certain date. For example, after:2/1/2010 specify mail sent after February 1, 2010.

before:

Same as after: except specifies mail sent before the specified date.

size:

Specifies messages whose total size, including attachments, is a specified number of bytes, kilobytes, or megabytes  For example, size:12 kb would find messages that are exactly 12K in size. The greater than (>) or less than (<) symbols can be used instead of bigger or smaller.

larger:

Similar to size: except specifies greater than the specified size.

smaller:

Similar to size: except specifies smaller than the specified size.

solo:

Finds email messages that do not have a reply to them yet.

tag:

Finds messages which have been tagged with a specified tag. For example, tag:amber will find message that have a tag called “amber” applied.

priority:

Finds messages, tasks or calendar items based on “high” “low” priority. For example, priority:high will find items with a priority setting of high..

Category:Zimbra | Comment (0)