Re: [Dovecot] Virusscanning
On Sun, Apr 11, 2010 at 08:06:34PM +0200, Andreas Schulze wrote: Hello list, I use currently a non-dovecot pop3 proxy which has the ability to scan all passing mails for viruses. And I like dovecot. p3scan? I have to combine both. One (and the only) idea is to call a virusscanner a shellscript, installed as PostLoginScript. What do you want: 1. Scan mails with newest database near fetch (IMAP command)? I'm not sure, but I've seen something about that looking into latetst p3scan features. It seems like it supports IMAP and can act as proxy beetween MUA and specified IMAP/POP3 server. I haven't tried it. 2. Just get mails from pop3 server and check it for viruses during delievery to dovecot mail storage? It seems to be work for some MTA filter. 3. You want to mirror remote IMAP store locally and check mails in local copy for viruses (and maybe do some spam checks)? Why not give a try to imapsync and some script around? I'm not finished my own yet... WBR Dmitri Ivanov
Re: [Dovecot] Forcibly emptying a POP3 mailbox
On Wed, Feb 03, 2010 at 06:41:34PM +0200, R??zvan Sandu wrote: Please provide a suggestion for the following situation: - I am running a stock POP3 dovecot server, on Fedora 12 (dovecot version 1.2.9) .. .. However, there are users that check the infamous ???Leave a copy on the server??? checkbox (or equivalent) in their mail clients, eventually adding ???Delete messages after X days???. Since I have no direct administrative control on the clients, I absolutely need a way to forbid the above behaviour at server level, in order to enforce the policy. The server's HDD is meant to store received messages from reception to the first access only. Well-well-well. I don't know the situation with dovecot POP3 server, but look on RFC 2449 and especially expire extension. I think there is other question and it is right one: Can dovecot pop3 server deal with pop3 extensions (supports capa command) and can it deal with expire extension and how to use it? Sorry that not much help... WBR Dmitri Ivanov
Re: [Dovecot] Forcibly emptying a POP3 mailbox
On Fri, Feb 05, 2010 at 08:25:01PM +0200, Timo Sirainen wrote: On Fri, 2010-02-05 at 19:37 +0300, Dmitri V. Ivanov wrote: Well-well-well. I don't know the situation with dovecot POP3 server, but look on RFC 2449 and especially expire extension. I think there is other question and it is right one: Can dovecot pop3 server deal with pop3 extensions (supports capa command) and can it deal with expire extension and how to use it? I haven't looked at the expire extension, but my guess is that about zero clients support it, so it's not really relevant if Dovecot supports it or not. Curious... Cyrus pop3d supports it for some reason, qpopper allows adding it into responce of capa pop3 command. Some old pine releases was crashed with it... But seem's you are right. There is no support with thunderbird for end-user. So this way to declare expiration policy isn't usefull... Sorry... WBR Dmitri Ivanov
Re: [Dovecot] Spam filtering
On Tue, Dec 15, 2009 at 02:20:23PM +0800, Patrick Nagel wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Dmitri, On 2009-12-15 04:54, Dmitri V. Ivanov wrote: On Mon, Dec 14, 2009 at 09:30:54PM +0100, Marcus Rueckert wrote: Is there a way do something like that with deliver? why not do it on MTA level? those already have the hooks for it normally. no need to reinvent the wheel imho. Sometimes it's virtual users using dovecot userdb or something like. MTA isn't aware of it (all it uses for virtual user is mailbox presence). But each virtual user have own wordlist for bogofilter. deliver would set some environment variables like $HOME to desirable values for such virtual user and then we have good place to call filter pointing it to virtual user home directory. Indeed, that would be more straight-forward than what's currently needed (from an administrator's point of view, at least). We have postfix configured to pipe to-be-delivered mails into a shell script that takes ${recipient} (the recipient's e-mail address) as first argument (here is the relevant part from master.cf): spamcheck unix- n n - - pipe flags=DRhu user=maildeliver:maildeliver argv=/usr/local/libexec/spamcheck_and_deliver ${recipient} The script then pipes the mail through `/usr/bin/spamc -u 'left part of e-mail address'` (which lets spamassassin's spamd do the checking and insertion of headers, and thanks to the -u parameter for each user a separate bayes_journal, bayes_seen and bayes_toks file is being used). That output then gets finally piped into `deliver -d 'e-mail address'`, which files the mails into the inbox/spam/unsure mailbox, according to a global sieve script that checks the headers previously inserted by spamd. My private bogofilter setup is simpler, since it's just for me, but you could do it similarly, by specifying the user's bogofilter wordlist directory (-d ...) in the shell script (I think). No holywar!!! I just tried to ask: is there plugin to replace maildrop with deliver for my setup. I just thinking that plugin to call bogofilter before sieve isn't to bad idea, but there may be a stones under water (I don't know it fairly). I dont like to use shell there (procmail too, because maildrop would set all needed environment variables from it's userdb and it's easy to write script to fill maildrop userdb up from dovecot passwd-like file). And there is an option to call deliver without '-d user' as far as I understand ($HOME is set to desired value). Note: with debian etch situation wasn't so clear bacause maildrop was compiled to use courier authdaemon, and so construction got extra unnessessery parts. WBR Dmitri Ivanov
Re: [Dovecot] Spam filtering
On Mon, Dec 14, 2009 at 09:30:54PM +0100, Marcus Rueckert wrote: Is there a way do something like that with deliver? why not do it on MTA level? those already have the hooks for it normally. no need to reinvent the wheel imho. Sometimes it's virtual users using dovecot userdb or something like. MTA isn't aware of it (all it uses for virtual user is mailbox presence). But each virtual user have own wordlist for bogofilter. deliver would set some environment variables like $HOME to desirable values for such virtual user and then we have good place to call filter pointing it to virtual user home directory. WBR Dmitri Ivanov
Re: [Dovecot] dovecot howto?
On Wed, Dec 10, 2008 at 06:08:31PM +0100, Olaf Zaplinski wrote: I have maildrop between dovecot and postfix but doesn't matter: postfix main.cf: # -- delivery options # local_recipient_maps = So not use users from /etc/passwd and virtual_mailbox_domains = list of my domains or database with it mydestination = virtual_alias_maps = btree:/etc/postfix/virtual alias_maps = btree:/etc/postfix/aliases alias_database = btree:/etc/postfix/aliases I think last two lines not for virtual, but for system users, so use virtual_alias_maps instead # mailbox_command = /usr/lib/dovecot/deliver mailbox_transport = dovecot virtual_transport = dovecot As far as I understand postfix also need to know users/mailboxes. So there must be: virtual_mailbox_maps = type:database with database key equal to mailbox name and value with something (virtual from postfix distribution wants path to mailbox/maildir). mailbox name is u...@domain. WBR Dmitri Ivanov
Re: [Dovecot] PLAIN password scheme question
On Fri, Nov 21, 2008 at 10:20:08PM +0200, Timo Sirainen wrote: I just never remembered to announce it anywhere. Added now to http://wiki.dovecot.org/Authentication/PasswordSchemes Thanks a lot. And I beg Your pardon for distraction. WBR Dmitri Ivanov
Re: [Dovecot] PLAIN password scheme question
On Thu, Nov 13, 2008 at 08:16:17PM +0200, Timo Sirainen wrote: v1.1+ supports {plain.b64} or {plain.hex}. As far as I can see (well - grep is used) You are implemented something (I don't untderstand code jet - just from comments within src/auth/password-scheme.c). It seems like to look for .hex,.b64 and .base64, But I'm wrong to find anything about it from wiki or NEWS. Where I'm wrong? WBR Dmitri Ivanov
[Dovecot] PLAIN password scheme question
Hi, ppls There is some problem with using passwd-like file and plaintext passwords within it. Let's assume we have users speaking russian. They think and remember their passwords also within russian words (they just not change keyboard layout before entering their passwords). So if the user has password like :jgf (meaning ass in russian) and passwords are stored into passwd-like file within {PLAIN} scheme what will happen? = user:{PLAIN}:jgf:1234:1234: = Isn't it a reason to implement something like {HEX} and why? WBR Dmitri Ivanov
Re: [Dovecot] Moving mail between folders
On Thu, Nov 13, 2008 at 07:59:32PM +0200, Ilo Lorusso wrote: Ive just installed Dovecot and postfix and Ive created a whole bunch of folders and started moving my mail around. Ive noticed that it copies the mail to the folder I wish to move the mail to and leave the original message waiting to be purged in the original folder IMAP protocol doesn't have move command. It has copy. So your client need (if I'mnot wrong): 1. copy message to destination mailbox (within COPY command) 2. store \Deleted flag to a message (within STORE command) It will not really delete message (but Your client often will not show it at folder anymore). One will be deleted within EXPUNGE command or when You will leave imap folder (with CLOSE command). Have a look into RFC 3501. Some peoples says It's terrible one tough. WBR Dmitri Ivanov