Domain Search

[bellzerr]

I like to save domain searches but it takes a LONG time for the domain list to appear in the search builder, and it appears to have even domains that come in as JUNK mail. Does anyone know how I can "clean up" my domain list?

[schemers]

You can't clean it up, since it is built dynamically form the list of domains in your account.

I'm not sure if there is already an exsting bug filed against how slow the domain list UI is or not, but if you file one and vote on it we'll look at it. It shouldn't be that hard to build a paging interface into it.

As for saving them, if you already know the domain you are interested in you can just type the following in the search bar:

from:(@domain.com)

If you click the To/CC box as well, it would look like:

(from:(@domain.com) OR to:(@domain.com) OR cc:(@domain.com))

[bellzerr]

Most helpful - thanks!

[bbarnett]

Sorry to bring up an old subject, but I've searched and this is the most relevant thread I've found so far.

We're evaluating Zimbra right now, and are indeed impressed with the document search options, and the power of advanced searches.

However, we are having problems with the the domain search.

1) it is quite slow. My first user converted over has about 6 gigs of email, and opening the 'domain search' takes 10 to 20 seconds, and always results in the browser stating that 'a script appears to be hung, should I terminate it'. I'm not sure if 5.0 improves the queries or the database indexing, but 4.5 seems a bit slow. Any ideas?

2) I'm not sure about other Zimbra users, but we have lots of domains that are prefixed by things such as 'us' or 'jp'. For example, 'bob@us.company.com" and "joe@jp.othercompany.com". As you can probably imagine, it is hard for end users to know that "othercompany.com" is prefixed by "jp" or "us". It makes it hard to find the domain name in the domain search box, especially when you consider that the domain search list is quite lengthy.. hence the problems with #1.

The problem with #1 is that users are simply not going to be able to know about, or use, from:@domain.com... meaning we're stuck with the script warning popping up. The issue with #2 is that I can't type from:@*domain.com either.. and even if I could, it would be "confusing" to users unless it was provided as a fancy box where they could type *company.com.

Does 5.0 resolve any of these issues? Does anyone have any suggestions for a way to resolve them, other than educating users (which is the impossible ).

Thanks

[bbarnett]

I'm running into this same problem when users are composing a message.

Most users are not aware that emails to (for example) ibm.com are actually @us.ibm.com. They enter 'ibm.com', yet nothing appears. They become confused.

Worse, even if the confusion is lifted.. that is, even if I inform them that us.ibm.com is what they want to search under, it does not help. There are representitives under all *.ibm.com domains, and there are other domains that are the same way.

The whole point of the address book is that users are not able to keep track of 1000 records, the names, and such for all contacts. Some users have no idea what the name is, just that "we need to email those ibm people!".

Once names start popping up, they are able to recall who to email to. So...

Is there any way to have an extended domain search, so that blah.domain.com is searchable by typing 'domain'.?

[bbarnett]

Hmm.

Have it hit upon a touchy topic or something along that line??