Re: [Dovecot] pop3 rate limit
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 28.12.2013 14:05, schrieb Christian Rößner: Hi, we have customers with Exchange servers that are polling for new mail every minute with dozens of pop3 accounts. I am looking for a mechanism to rate limit this per user. So what I am looking for is a way to block users from polling, if a user asks for new mail more than every 5 minutes (for example). Is this possible? Can this be achieved within Dovecot or does it need external scripting? (I thought about fail2ban, but also want IPv6 support) Hi Christian, i have about 1000 pop3 logins per minute, with little tuning dovecot has no problem with it but however you may use iptables recent, but for sure its not optimal cause of nat and/or grep login timestamps syslog and echo in deny list http://wiki2.dovecot.org/Authentication/RestrictAccess perhaps fail2ban can be configured to do equal actions Thanks in advance -Christian Rößner -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein Best Regards MfG Robert Schetterer - -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJSwSjZAAoJEP8jBObu0LlE1n0IALpzRi2k7QaDkILMthMcRZwz K7ukF0EVZmtGUt8uFJiEW1hWyyWRM3F5/KCwK7d39mTA+fEo54GhoAzrQrJkomnO z+N3qWUj8MbKNx6vNbMH6b6qpSPKIPr913Al2vhxQ4Mp2EYI/630Xu1GuVVCzWyI cUURYWFwNBNwExzzphYgKS8V1MU6EBt1g/ElaYY0uVwH0m3f8kxmLNbaswuQ5pga dczxDtcIzMCsK/bxoSot8SKpSmNOkLEexBM5rb8UWKmHXFym1vTdHQHf/gYsAuv2 7ePsUcG3JCQO5pfi6q6psFDFTodXNttS89Np+0tdwVLqoSZ3DA3rdpknjnQALXQ= =cYCD -END PGP SIGNATURE-
Re: [Dovecot] LMTP with virtual and system users
Hi Adrian,
Am 26.12.2013 12:20, schrieb Adrian Zaugg:
You can use exim to prepare the address as you wish: only the user name
for pam users and the full address for virtual users.
Configure a new router to strip the domain part for pam users:
local_pam_users:
debug_print = R: strip domain for local pam users
driver = redirect
check_local_user
domains = @ : localhost : ${primary_hostname}
data = ${local_part}
redirect_router = local_user
I'm not 100% sure of the domains condition; it should restrict the
router to your domain(s) where your pam users receive their email. The
redirect_router designates the router which routes your local deliveries
to your lmtp transport. Place the new router to run just before your
local_user router.
Since your config works for your virtual users, you don't need to do
anything in addition.
I had tried this once already. I have used your snipplet and attached
the debug output from exim. Sadly it didn't work, because the mtp
process got the foll email again and not just the username.
thanks
Philipp
--
---
DI Mag. Philipp Kolmann mail: kolm...@zid.tuwien.ac.at
Technische Universitaet Wien web: www.zid.tuwien.ac.at
Zentraler Informatikdienst (ZID) tel: +43(1)58801-42011
Wiedner Hauptstr. 8-10, A-1040 WienDVR: 0005886
---
17788 local_pam_users router
17788 local_part=pkolmann domain=lukas.rudolfina.at
17788 checking domains
17788 lukas.rudolfina.at in @ : localhost : lukas.rudolfina.at? yes (matched
@)
17788 checking for local user
17788 seeking password data for user pkolmann: using cached result
17788 getpwnam() succeeded uid=1002 gid=1002
17788 R: strip domain for local pam users
17788 calling local_pam_users router
17788 rda_interpret (string): ${local_part}
17788 expanded: pkolmann
17788 file is not a filter file
17788 parse_forward_list: pkolmann
17788 extract item: pkolmann
17788 local_pam_users router generated pkolm...@lukas.rudolfina.at
17788 errors_to=NULL transport=NULL
17788 uid=unset gid=unset home=NULL
17788 routed by local_pam_users router
17788 envelope to: pkolm...@lukas.rudolfina.at
17788 transport: none
17788 locking /var/spool/exim4/db/retry.lockfile
17788 locked /var/spool/exim4/db/retry.lockfile
17788 EXIM_DBOPEN(/var/spool/exim4/db/retry)
17788 returned from EXIM_DBOPEN
17788 opened hints database /var/spool/exim4/db/retry: flags=O_RDONLY
17788
17788 Considering: pkolm...@lukas.rudolfina.at
17788 unique = \0\pkolm...@lukas.rudolfina.at
17788 dbfn_read: key=R:lukas.rudolfina.at
17788 dbfn_read: key=R:pkolm...@lukas.rudolfina.at
17788 dbfn_read: key=R:pkolm...@lukas.rudolfina.at:phil...@kolmann.at
17788 no domain retry record
17788 no address retry record
17788 pkolm...@lukas.rudolfina.at: queued for routing
17788
17788 routing pkolm...@lukas.rudolfina.at
17788 local_user router
17788 local_part=pkolmann domain=lukas.rudolfina.at
17788 checking domains
17788 search_open: mysql NULL
17788 cached open
17788 search_find: file=NULL
17788 key=SELECT domain FROM domain WHERE domain='lukas.rudolfina.at';
partial=-1 affix=NULL starflags=0
17788 LRU list:
17788 :/etc/aliases
17788 End
17788 internal_search_find: file=NULL
17788 type=mysql key=SELECT domain FROM domain WHERE
domain='lukas.rudolfina.at';
17788 cached data used for lookup of SELECT domain FROM domain WHERE
domain='lukas.rudolfina.at';
17788 lookup failed
17788 lukas.rudolfina.at in @:localhost:? yes (matched @)
17788 lukas.rudolfina.at in +local_domains? yes (matched +local_domains)
17788 checking local_parts
17788 pkolmann in ! root? yes (end of list)
17788 checking for local user
17788 seeking password data for user pkolmann: using cached result
17788 getpwnam() succeeded uid=1002 gid=1002
17788 R: local_user for pkolm...@lukas.rudolfina.at
17788 calling local_user router
17788 local_user router called for pkolm...@lukas.rudolfina.at
17788 domain = lukas.rudolfina.at
17788 set transport dovecot_lmtp
17788 queued for dovecot_lmtp transport: local_part = pkolmann
17788 domain = lukas.rudolfina.at
17788 errors_to=NULL
17788 domain_data=NULL localpart_data=NULL
17788 routed by local_user router
17788 envelope to: pkolm...@lukas.rudolfina.at
17788 transport: dovecot_lmtp
17788
17788 After routing:
17788 Local deliveries:
17788 pkolm...@lukas.rudolfina.at
17788 Remote deliveries:
17788 Failed addresses:
17788 Deferred addresses:
17788 search_tidyup called
17788 close MYSQL connection: localhost/exim/exim
17788 Local deliveries
17788 pkolm...@lukas.rudolfina.at
17788 locking /var/spool/exim4/db/retry.lockfile
17788 locked /var/spool/exim4/db/retry.lockfile
17788 EXIM_DBOPEN(/var/spool/exim4/db/retry)
17788 returned from EXIM_DBOPEN
Re: [Dovecot] pop3 rate limit
michael skrev den 2013-12-30 02:35: www.policyd.org You'll need to use v2.1 to get IPV6 support. incorrect, policyd v1 still supports ipv6 greylistning, but it cant be used as a ipv6 server from postfix is another problem same holds water with sqlgrey
Re: [Dovecot] pop3 rate limit
Patrick Ben Koetter skrev den 2013-12-30 08:36: policyd can rate limit dovecot POP3 users? sure :) i just think dovecot does it better last resort would be ip6table/iptable
Re: [Dovecot] pop3 rate limit
On 2013-12-30 22:53, Benny Pedersen wrote: michael skrev den 2013-12-30 02:35: www.policyd.org You'll need to use v2.1 to get IPV6 support. incorrect, policyd v1 still supports ipv6 greylistning, but it cant be used as a ipv6 server from postfix is another problem same holds water with sqlgrey v2.0 is supposed to support IPV6 but it is buggy (in my experience unusable). This is why I recommended v2.1 ewven though it is still in development.
Re: [Dovecot] dsync-local crashes due to assertion failures
On 08-12-2013 16:26:15 +0100, Fabian Groffen wrote: I have two servers that share nothing, running dovecot version 2.2.9. The first server hosts the original mail base, which I want to sync using dovecot to the second server. With some trial and error I managed to get synchronisation running using tcp sockets. Now for some accounts I see dsync-local crashing on the server that has the original mail base (which is still the only of the two that receives new mail). The log shows: Dec 8 03:13:14 zeus dovecot: dsync-local(someuser): Panic: file mail-index-tr ansaction-export.c: line 203 (log_append_ext_hdr_update): assertion failed: (u32 .offset + u32.size = ext_hdr_size) Turns out I didn't remove all index files. After I did (dovecot.index + dovecot.list.index) the assertion has gone away. Interesting side-note: after removal of the indices, some of my mailboxes showed new emails from long ago, that I hadn't seen previously. Now, from the first look and sizes, synchronisation seems to have succeeded after a night. -- Fabian Groffen Gentoo on a different level signature.asc Description: Digital signature
[Dovecot] dovecot 2.2.10 - imap: Error: Can't load plugin imap_stats_plugin:
dovecot 2.2.10 is raising this error on my installation.
Dec 30 13:57:59 imap: Error: Can't load plugin imap_stats_plugin: Plugin
stats must be loaded also (you must set: mail_plugins=$mail_plugins
stats)
Dec 30 13:57:59 imap: Fatal: Couldn't load required plugins
This error occurs at logging phase.
The dovecot configuration looks correct to me, here below an excerpt of
it:
...
...
mail_plugins=$mail_plugins stats
protocol imap {
mail_plugins = $mail_plugins imap_stats
}
plugin {
# how often to session statistics
stats_refresh = 30 secs
# track per-IMAP command statistics
stats_track_cmds = yes
}
...
...
I was already using this configuration but only now I am getting this
error.
From STRACE I see that the stat plugin is correctly localed .
Is anybody else getting this error? or am I missing something?
Here below an except of the strace message.
[pid 17112] open(/usr/local/lib/dovecot/lib95_imap_stats_plugin.so,
O_RDONLY) = 14
[pid 17112] read(14,
\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0`\t\0\0004\0\0\0...,
512) = 512
[pid 17112] fstat64(14, {st_mode=S_IFREG|0755, st_size=53122, ...}) = 0
[pid 17112] mmap2(NULL, 8908, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_DENYWRITE, 14, 0) = 0xf7609000
[pid 17112] mmap2(0xf760b000, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 14, 0x1) = 0xf760b000
[pid 17112] close(14) = 0
[pid 17112] open(/usr/local/lib/dovecot/lib90_stats_plugin.so,
O_RDONLY) = 14
[pid 17112] read(14,
\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0@\24\0\0004\0\0\0...,
512) = 512
[pid 17112] fstat64(14, {st_mode=S_IFREG|0755, st_size=100054, ...}) = 0
[pid 17112] mmap2(NULL, 20320, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_DENYWRITE, 14, 0) = 0xf7604000
[pid 17112] mmap2(0xf7608000, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 14, 0x3) = 0xf7608000
[pid 17112] close(14) = 0
[pid 17112] write(2, \1\01017112 prefix=imap: \n, 22) = 22
[pid 17112] write(2, \1\00417112 Can't load plugin imap_s..., 127) =
127
[pid 17112] munmap(0xf7609000, 8908)= 0
[pid 17112] munmap(0xf7604000, 20320) = 0
[pid 17112] write(2, \1\00517112 Couldn't load required p..., 39) = 39
[pid 17112] exit_group(89) = ?
Process 17112 detached
Re: [Dovecot] dovecot 2.2.10 - imap: Error: Can't load plugin imap_stats_plugin:
Am 30.12.2013 14:29, schrieb giova...@neweden.uk.to:
dovecot 2.2.10 is raising this error on my installation.
Dec 30 13:57:59 imap: Error: Can't load plugin imap_stats_plugin: Plugin
stats must be loaded also (you must set:
mail_plugins=$mail_plugins stats)
Dec 30 13:57:59 imap: Fatal: Couldn't load required plugins
This error occurs at logging phase.
The dovecot configuration looks correct to me, here below an excerpt of it:
how do you come to that conclusion by quoting the error above?
you must set: mail_plugins=$mail_plugins stats and have
stats *not* configured - notice the word *also* above
mail_plugins=$mail_plugins stats
protocol imap {
mail_plugins = $mail_plugins imap_stats
}
plugin {
# how often to session statistics
stats_refresh = 30 secs
# track per-IMAP command statistics
stats_track_cmds = yes
}
signature.asc
Description: OpenPGP digital signature
Re: [Dovecot] dovecot 2.2.10 - imap: Error: Can't load plugin imap_stats_plugin:
Am 30.12.2013 14:33, schrieb Reindl Harald:
Am 30.12.2013 14:29, schrieb giova...@neweden.uk.to:
dovecot 2.2.10 is raising this error on my installation.
Dec 30 13:57:59 imap: Error: Can't load plugin imap_stats_plugin: Plugin
stats must be loaded also (you must set:
mail_plugins=$mail_plugins stats)
Dec 30 13:57:59 imap: Fatal: Couldn't load required plugins
This error occurs at logging phase.
The dovecot configuration looks correct to me, here below an excerpt of it:
how do you come to that conclusion by quoting the error above?
you must set: mail_plugins=$mail_plugins stats and have
stats *not* configured - notice the word *also* above
mail_plugins=$mail_plugins stats
protocol imap {
mail_plugins = $mail_plugins imap_stats
}
plugin {
# how often to session statistics
stats_refresh = 30 secs
# track per-IMAP command statistics
stats_track_cmds = yes
}
sorry - indeed i missed the first line and faced only mail_plugins
in the imap section :-(
signature.asc
Description: OpenPGP digital signature
Re: [Dovecot] tests with metadata module
On Sunday 29 December 2013 11:52:23 Mihai Badici wrote: On Thursday 26 December 2013 12:23:18 you wrote: --Repost after subscription as list member --- I made some tests with metadata support in dovecot 2.2.10. Previously I had dovecot 2.2.4 with external metadata plugin who work well. I use dovecot with roundcube and roundcube plugins from kolab project . First, the feature activation was tricky and rather undocumented. I spent about half hour googling, after that I set: imap_metadata = yes and mail_attribute_dict = file:%h/shared_metadata It worked after I changed here : file:%s/shared_metadata I made some investigation and I found Roundcube perform a GETMETADATA * (/private/vendor/kolab/folder-type) to list all special folders. In cmd-getmetadata.c there is a if (line 455) who is intended, I think, to avoid the use of wildcards in mailbox name, but at the end the result is an attempt to open a NULL mailbox name who produce the crash. When I remove this condition and recompile dovecot, there are no crashes. It's not clear for me if GETMETADATA * is still legal (there is a reference to rfc 5464 in the code) ; but in both cases there is a bug in the code.
Re: [Dovecot] tests with metadata module
On 12/30/2013 03:25 PM, Mihai Badici wrote: I made some investigation and I found Roundcube perform a GETMETADATA * (/private/vendor/kolab/folder-type) to list all special folders. This is indeed not specified in RFC5464, but it was in ANNOTATEMORE extension draft. This is very handy and it is supported by Cyrus. Timo fixed this in http://hg.dovecot.org/dovecot-2.2/rev/0c3071ebe44b one day before 2.2.10 release. Didn't it make to the release? -- Aleksander 'A.L.E.C' Machniak LAN Management System Developer [http://lms.org.pl] Roundcube Webmail Developer [http://roundcube.net] --- PGP: 19359DC1 @@ GG: 2275252 @@ WWW: http://alec.pl
Re: [Dovecot] pop3 rate limit
Hello Benny, Monday, December 30, 2013, 9:57:13 AM, you wrote: Patrick Ben Koetter skrev den 2013-12-30 08:36: policyd can rate limit dovecot POP3 users? sure :) i just think dovecot does it better last resort would be ip6table/iptable We're talking Dovecot, not Postfix. Policyd AFAIK is ran as a policy from within Postfix. That would be over SMTP and not POP3. If there is some config within Dovecot to allow usage of policys written for Postfix, please point that out. Searching the policyd.org site for terms like 'POP3' or 'Dovecot' yield no results. -- Best regards, Duanemailto:duih...@gmail.com
Re: [Dovecot] tests with metadata module
Zitat von A.L.E.C a...@alec.pl: Timo fixed this in http://hg.dovecot.org/dovecot-2.2/rev/0c3071ebe44b one day before 2.2.10 release. Didn't it make to the release? yes
Re: [Dovecot] tests with metadata module
On Monday 30 December 2013 16:48:58 A.L.E.C wrote: On 12/30/2013 03:25 PM, Mihai Badici wrote: I made some investigation and I found Roundcube perform a GETMETADATA * (/private/vendor/kolab/folder-type) to list all special folders. This is indeed not specified in RFC5464, but it was in ANNOTATEMORE extension draft. This is very handy and it is supported by Cyrus. Timo fixed this in http://hg.dovecot.org/dovecot-2.2/rev/0c3071ebe44b one day before 2.2.10 release. Didn't it make to the release? I will check further. Dovecot crashes only in some particular conditions but it looks like is related with this * . There are values for mail_location and mail_attribute_dictwho crash dovecot. With: mail_location = maildir:~/MAILDIR and mail_attribute_dict= file:%u/shared_metadata dovecot works well. So I think the fix is applied but there is a side effect remaining. -- Mihai Bădici http://mihai.badici.ro
Re: [Dovecot] pop3 rate limit
Hi, policyd can rate limit dovecot POP3 users? sure :) i just think dovecot does it better last resort would be ip6table/iptable We're talking Dovecot, not Postfix. Policyd AFAIK is ran as a policy from within Postfix. That would be over SMTP and not POP3. If there is some config within Dovecot to allow usage of policys written for Postfix, please point that out. Searching the policyd.org site for terms like 'POP3' or 'Dovecot' yield no results. That’s what I thought ;-) In fact I would have to write an external policy service that really counts user/time. But as Robert said, there seems not to be a bigger problem with lots of connections, so I do not try to find a solution here anymore :-) Thanks everybody -Christian Rößner -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [Dovecot] pop3 rate limit
Duane Hill skrev den 2013-12-30 16:59: Searching the policyd.org site for terms like 'POP3' or 'Dovecot' yield no results. yes if its undokumented, then its unsupported, if dovecot anvil / dovecot pop3 cant do it then it could be added, if pop3 is a problem why not change to imap ?, where idle is supported else its more or less just possible to use iptable recent to limit it
Re: [Dovecot] pop3 rate limit
Christian Rößner skrev den 2013-12-30 17:28: That’s what I thought ;-) In fact I would have to write an external policy service that really counts user/time. But as Robert said, there seems not to be a bigger problem with lots of connections, so I do not try to find a solution here anymore :-) think of rsyslog, that update dovecot sql table pop3 enable disable ? :=) sorry just thinking loudly now, so close to new years eye
[Dovecot] Warning: fscking index file /.../dovecot.index
We have often found the below error in VPS servers using OpenVZ, and some cases using OpenStack, in neither case is used for storage or sharing ISCSI or NFS Client can not receive messages via POP3 or IMAP In /var/log/maillog the message below is seen Oct 31 15:28:26 vps dovecot: pop3(u...@domain.com): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0 [0x2b3718e07400] - /usr/lib64/dovecot/libdovecot.so.0 [0x2b3718e07456] - /usr/lib64/dovecot/libdovecot.so.0 [0x2b3718e06df3] - /usr/lib64/dovecot/libdovecot-storage.so.0 [0x2b3718b6566b] - /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_sync_commit+0x89) [0x2b3718b5ced9] - /usr/lib64/dovecot/libdovecot-storage.so.0 [0x2b3718aeae4d] - /usr/lib64/dovecot/libdovecot-storage.so.0 [0x2b3718aea357] - /usr/lib64/dovecot/libdovecot-storage.so.0 [0x2b3718aea698] - /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_storage_sync_init+0xbb) [0x2b3718aea83b] - /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x31) [0x2b3718b15e31] - /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync+0x27) [0x2b3718b18537] - dovecot/pop3(client_create+0x332) [0x405702] - dovecot/pop3 [0x40414b] - dovecot/pop3 [0x404708] - /usr/lib64/dovecot/libdovecot.so.0 [0x2b3718dc9a52] - /usr/lib Both POP3 as IMAP Oct 31 15:24:42 vps dovecot: imap(u...@domain.com): Warning: fscking index file /home/user/mail/domain.com/user/dovecot.index Oct 31 15:28:26 vps dovecot: pop3(u...@domain.com): Warning: fscking index file /home/user/mail/domain.com/user/dovecot.index Today I do to solve this the procedure below - Access the directory mailbox - Remove files dovecot.index * - Run the command doveadm index-u $ user @ $ domain-q INBOX The question is for what reason this only occurs with VPS servers, I do not find this error on any single physical server to virtual and dovecot settings are the same. att Alex Vitola
Re: [Dovecot] pop3 rate limit
Am 30.12.2013 17:30, schrieb Benny Pedersen: Duane Hill skrev den 2013-12-30 16:59: Searching the policyd.org site for terms like 'POP3' or 'Dovecot' yield no results. yes if its undokumented, then its unsupported so what you are talking about? if dovecot anvil / dovecot pop3 cant do it then it could be added if it could cook it would not by a mobile-phone or what? if pop3 is a problem why not change to imap ?, where idle is supported why not stop talking about things you do not understand? read the OP again - the topic is fetch email with exchange-connector else its more or less just possible to use iptable recent to limit it yes, but that was not the question signature.asc Description: OpenPGP digital signature
[Dovecot] How to add dovecot plugin?
I'm running dovecot version 2.0.9 under CentOS-6.5 .
I want to add the following plugin:
require fileinto;
if header :contains X-Spam-Flag YES {
fileinto Spam;
}
Could some kind soul tell me where exactly I should place this script
(eg anywhere in /etc/dovecot/dovecot.conf
or anywhere in /etc/dovecot/conf.d/90-plugin.conf),
and do I need to take any other action?
Actually, the folder I should like spam to go to is
~/Maildir/.Spam/cur/ - should I modify the above script?
If these queries are anwered clearly in some dovecot documentation,
please point me to that.
--
Timothy Murphy
e-mail: gayleard /at/ eircom.net
School of Mathematics, Trinity College, Dublin 2, Ireland
Re: [Dovecot] How to add dovecot plugin?
Am 31.12.2013 00:44, schrieb Timothy Murphy:
I'm running dovecot version 2.0.9 under CentOS-6.5 .
I want to add the following plugin:
require fileinto;
if header :contains X-Spam-Flag YES {
fileinto Spam;
}
Could some kind soul tell me where exactly I should place this script
(eg anywhere in /etc/dovecot/dovecot.conf
or anywhere in /etc/dovecot/conf.d/90-plugin.conf),
and do I need to take any other action?
Actually, the folder I should like spam to go to is
~/Maildir/.Spam/cur/ - should I modify the above script?
If these queries are anwered clearly in some dovecot documentation,
please point me to that
this is a *sieve script* not a plugin itself
http://wiki2.dovecot.org/Pigeonhole/Sieve
signature.asc
Description: OpenPGP digital signature
