Search found 80 matches
- Mon Jul 24, 2006 12:49 am
- Forum: Administrators
- Topic: Junk/Not junk feature from CLI
- Replies: 5
- Views: 818
Junk/Not junk feature from CLI
Dkarp, should I add this requirement to the bug you mentioded? It is quite general one as I have seen.
- Fri Jul 21, 2006 4:56 am
- Forum: Administrators
- Topic: Junk/Not junk feature from CLI
- Replies: 5
- Views: 818
Junk/Not junk feature from CLI
Is there a way to move certain message (based on message ID) from Junk to Inbox or back using CLI? If not, would you see it as useful/possible?
- Thu Jul 13, 2006 2:23 am
- Forum: Administrators
- Topic: mystery solved: unclean shutdown causes redo.log to be owned by root:root
- Replies: 29
- Views: 5629
mystery solved: unclean shutdown causes redo.log to be owned by root:root
I do not know if this is the right place for comments, but please read this. I have noticed several times that files in opt/zimbra/amavisd/.spamassassin/ directory have incorrect permissions, in fact the same you mentioned (owned by root/root, read only). This happens quite randomly, let's say once ...
- Wed Jun 28, 2006 5:35 am
- Forum: Users
- Topic: Global address book
- Replies: 5
- Views: 900
Global address book
Those future GAL features - will they work from Zimbra UI only, or from Outlook too? I mean something like a auto "null search" and display of the whole list when user clicks "To" button. I know this is mostly LDAP issue, but what if?
- Mon Jun 26, 2006 2:40 am
- Forum: Administrators
- Topic: Filtering user access per account
- Replies: 7
- Views: 1755
Filtering user access per account
"Enforce strong password" feature would be good, Zimbra is missing that. But I would still prefer solution that would allow mailbox access from defined IPs/subnets only. Also could be part of CoS. For some kind of automated attacks trying to guess name/password sombination, strong password...
- Fri Jun 23, 2006 10:45 am
- Forum: Administrators
- Topic: Filtering user access per account
- Replies: 7
- Views: 1755
Filtering user access per account
Scotty, 1. Majority of our users (Group1) does not need e-mail access from outside world at all. 2. Another part (Group 2) is travelling a lot around the world and they need access from ANY location, so there is no need for any kind of IP filtering at any level. Just free access from everywhere, no ...
- Fri Jun 23, 2006 2:52 am
- Forum: Administrators
- Topic: Filtering user access per account
- Replies: 7
- Views: 1755
Filtering user access per account
Thank for your responses. In fact we are already using VPN and it is satisfying. VPN use is quite restrictive here (only from authorized computers + smartcards) and I just wanted to loosen mail access a little bit. Filtering by country is no option for us as our commercial staff is travelling really...
- Thu Jun 22, 2006 5:56 am
- Forum: Administrators
- Topic: Filtering user access per account
- Replies: 7
- Views: 1755
Filtering user access per account
It is maybe too much I'm asking for but anyway I'll try it. Is there a way to filter users' access to their mailboxes based on account and IP adress? For example: user1 can access his mailbox from local subnets only user2 can access his mailbox from local subnets and/or another specified public IP u...
- Fri Jun 16, 2006 6:39 am
- Forum: Administrators
- Topic: Bad Planning
- Replies: 5
- Views: 967
Bad Planning
There may be a workaround I think. Try to set helo/ehlo in postfix conf. Then your zimbra will helo with the name you set. Of course there will be original name in message headers, but for your purpose it may be sufficient. In /opt/zimbra/postfix/conf/main.cf add this line: smtp_helo_name = whatever...
- Tue Jun 13, 2006 5:11 am
- Forum: Administrators
- Topic: Whitelisting
- Replies: 9
- Views: 1822
Whitelisting
Techdude: 1. Try to delist your mailserver from these blacklists. Every blacklist should have procedure for that, so use Google to find respective web pages and folllow their rules. If you have secured your SMTP, you may have success. But from posted headers it seems to me that it is not your server...