Re: [Dovecot] mail spool filesystem

[Sven Hartge]

Adrian Ulrich  wrote:

>> I read that XFS is a good choice, but is not too reliable...

> Are you using Maildir or MBOX?

> In any case: XFS would be my last choice:

> XFS is nice if you are working with large files (> 2GB), but for
> E-Mail i'd stick with ext3 (or maybe even reiser3) as it works very
> well with small files.

I don't know, but my Courier server (Maildir++ format, 10k users, 12
million mails on server, some users with over 20k mails in one
directory/folder) runs _way_ smoother with XFS. I also tested ext4, but
this was no large gain over ext3 (with dir_index of course).

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re: [Dovecot] Duplicate Email with Dovecot Sieve

[Stephan Bosch]

On 8/17/2011 8:08 AM, Holden Hao wrote:

from: dovecot-deliver.log

deliver(user): Info: Loading modules from directory:
/usr/local/lib/dovecot/lda
deliver(user): Info: Module loaded:
/usr/local/lib/dovecot/lda/lib10_quota_plugin.so
deliver(user): Info: Module loaded:
/usr/local/lib/dovecot/lda/lib90_sieve_plugin.so
deliver(user): Info: Quota root: name= backend=maildir args=
deliver(user): Info: Namespace: type=private, prefix=INBOX., sep=.,
inbox=yes, hidden=no, list=1, subscriptions=yes
deliver(user): Info: maildir: data=/home/user/Maildir
deliver(user): Info: maildir++: root=/home/user/Maildir, index=, control=,
inbox=/home/user/Maildir
deliver(user): Info: sieve: using sieve path for user's script:
/home/user/.dovecot.sieve
deliver(user): Info: sieve: opening script /home/user/.dovecot.sieve
deliver(user): Info: sieve: executing compiled script
/home/user/.dovecot.sieve
deliver(user): Info: sieve: msgid=<
cajnnnymqpmeopfft3+_qhvxyxf3v-4bzv9ojjqgfrtcddnt...@mail.gmail.com>: stored
mail into mailbox 'Inbox.Test'


 Hmm, odd. The above log only shows one delivery. I would expect a 
duplicate entry there when Dovecot is causing this. You can enable 
mail_debug to see whether that shows more. Also, the user log 
(~/.dovecot.sieve.log) could contain other info. But, I don't expect 
much more from that.


Are you perhaps doing something interesting at MTA level?

Regards,

Stephan.

Re: [Dovecot] sender for Sieve vacation message

[Stephan Bosch]

On 8/17/2011 10:06 AM, Florian Effenberger wrote:

Hello,

2011/8/17 Florian Effenberger:


is it possible to define the sender for the Dovecot Sieve
implementation's vacation extension? It seems to be impossible to add,
e.g., a name, or choose a different sender address.

to be precisely: I am talking about the "From" header.


You can use the :from parameter, e.g.:

require "vacation";
vacation :from "flo...@gmail.com" "Not here at the moment!";

Read RFC5230 (http://tools.ietf.org/html/rfc5230) for more info.

Regards,

Stephan.

Re: [Dovecot] May Dovecot help in users education

[Noel Butler]

On Wed, 2011-08-17 at 16:05 +0200, Laurent CARON wrote:

> On 17/08/2011 16:00, Alexandre Chapellon wrote:
> > Is there any way to achieve this with dovecot? Does anybody have another
> > idea smoothly force used to switch to TLS?
> 
> Hi,
> 
> Maybe by sending them an email with a deadline for the end of clear text 
> auth support ?
> 


This is the best method, give them at least 30 days notice (preferably
90 days), the notices should include a link to a kb/support site showing
them how, not doing this will clog up your support lines for sure.

Send subsequent warning notices, with slightly stronger language each
time, at 21 days, 14 days and 7 days, 3 days and 1 day.
We did this when we cut out relaying for IP's and moved entirely to smtp
auth, so its much the same thing - getting them to change settings.

A safe guard though, if you tell them, say 1st October cut off, don't
actually cut off until a week or two after. 

Yes, you'll still find some have not done it, but that's the nature of
some people.


> If they don't amend their setup they'll be unable to retrieve their emails.
> 
> Should you want to go the "nicer" way, you could throttle bandwidth to 
> port 110/143 provided you use those for insecure connections.
> 


That's not the right thing to do, TLS uses those ports too, it's SSL
that does not, and it's pointless using other ports, you'll end up
creating more problems than what it's worth.




signature.asc
Description: This is a digitally signed message part

Re: [Dovecot] sender for Sieve vacation message

[Florian Effenberger]

Hello,

2011/8/17 Florian Effenberger :

> is it possible to define the sender for the Dovecot Sieve
> implementation's vacation extension? It seems to be impossible to add,
> e.g., a name, or choose a different sender address.

to be precisely: I am talking about the "From" header.

Florian

[Dovecot] sender for Sieve vacation message

[Florian Effenberger]

Hello,

is it possible to define the sender for the Dovecot Sieve
implementation's vacation extension? It seems to be impossible to add,
e.g., a name, or choose a different sender address.

Thanks,
Florian

[Dovecot] Duplicate Email with Dovecot Sieve

[Holden Hao]

I am trying to use Dovecot Sieve after upgrading Dovecot from 1.0.15 to
1.2.17.  I used the same config file from the old version but I added some
entries to make sieve work.  In my initial tests, sieve works and is able to
do the actions that I set it to do.  However, I get 2 copies of incoming
emails.  The inbox would always preserve a copy even if the sieve filter is
set to transfer emails to another folder or redirect it to another address.
 The logs do not seem to report any issues.  I don't know what causes the
problem and I would appreciate some pointers.

Here are some more details of my setup:

OS: Linux 2.6.24.2
Dovecot: 1.2.17
Dovecot Sieve:0.1.19
Manage Sieve:0.11.13
MTA: Qmail 1.03

dovecot -n

# 1.2.17: /usr/local/etc/dovecot.conf
# OS: Linux 2.6.24.2 i686 Debian lenny/sid
log_path: /var/log/dovecot.log
log_timestamp:
protocols: imap pop3 imaps pop3s managesieve
ssl_cert_file: /var/dir/etc/certificates/server.crt
ssl_key_file: /var/dir/etc/certificates/server.key
disable_plaintext_auth: no
login_dir: /usr/local/var/run/dovecot/login
login_executable(default): /usr/local/libexec/dovecot/imap-login
login_executable(imap): /usr/local/libexec/dovecot/imap-login
login_executable(pop3): /usr/local/libexec/dovecot/pop3-login
login_executable(managesieve): /usr/local/libexec/dovecot/managesieve-login
login_greeting: Welcome
login_process_size: 32
verbose_proctitle: yes
first_valid_uid: 1000
mail_location: maildir:~/Maildir
mail_debug: yes
mail_executable(default): /usr/local/libexec/dovecot/imap
mail_executable(imap): /usr/local/libexec/dovecot/imap
mail_executable(pop3): /usr/local/libexec/dovecot/pop3
mail_executable(managesieve): /usr/local/libexec/dovecot/managesieve
mail_plugins(default): quota imap_quota
mail_plugins(imap): quota imap_quota
mail_plugins(pop3): quota
mail_plugins(managesieve):
mail_plugin_dir(default): /usr/local/lib/dovecot/imap
mail_plugin_dir(imap): /usr/local/lib/dovecot/imap
mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3
mail_plugin_dir(managesieve): /usr/local/lib/dovecot/managesieve
imap_client_workarounds(default): outlook-idle
imap_client_workarounds(imap): outlook-idle
imap_client_workarounds(pop3):
imap_client_workarounds(managesieve):
pop3_uidl_format(default): %08Xu%08Xv
pop3_uidl_format(imap): %08Xu%08Xv
pop3_uidl_format(pop3): UID%u-%v
pop3_uidl_format(managesieve): %08Xu%08Xv
managesieve_logout_format(default): bytes=%i/%o
managesieve_logout_format(imap): bytes=%i/%o
managesieve_logout_format(pop3): bytes=%i/%o
managesieve_logout_format(managesieve): bytes ( in=%i : out=%o )
namespace:
  type: private
  separator: .
  prefix: INBOX.
  location: maildir:~/Maildir
  inbox: yes
  list: yes
  subscriptions: yes
lda:
  postmaster_address: postmas...@xx.org
  mail_plugin_dir: /usr/local/lib/dovecot/lda
  mail_plugins: quota sieve
  sendmail_path: /var/qmail/bin/sendmail
  log_path: /var/log/dovecot-deliver-errors.log
  info_log_path: /var/log/dovecot-deliver.log
auth default:
  verbose: yes
  passdb:
driver: checkpassword
args: /var/qmail/bin/auth_pop
  userdb:
driver: prefetch
plugin:
  quota: maildir
  sieve: ~/.dovecot.sieve
  sieve_dir: ~/sieve


from: dovecot-deliver.log

deliver(user): Info: Loading modules from directory:
/usr/local/lib/dovecot/lda
deliver(user): Info: Module loaded:
/usr/local/lib/dovecot/lda/lib10_quota_plugin.so
deliver(user): Info: Module loaded:
/usr/local/lib/dovecot/lda/lib90_sieve_plugin.so
deliver(user): Info: Quota root: name= backend=maildir args=
deliver(user): Info: Namespace: type=private, prefix=INBOX., sep=.,
inbox=yes, hidden=no, list=1, subscriptions=yes
deliver(user): Info: maildir: data=/home/user/Maildir
deliver(user): Info: maildir++: root=/home/user/Maildir, index=, control=,
inbox=/home/user/Maildir
deliver(user): Info: sieve: using sieve path for user's script:
/home/user/.dovecot.sieve
deliver(user): Info: sieve: opening script /home/user/.dovecot.sieve
deliver(user): Info: sieve: executing compiled script
/home/user/.dovecot.sieve
deliver(user): Info: sieve: msgid=<
cajnnnymqpmeopfft3+_qhvxyxf3v-4bzv9ojjqgfrtcddnt...@mail.gmail.com>: stored
mail into mailbox 'Inbox.Test'

Thanks in advance for your replies.


Holden

Re: [Dovecot] May Dovecot help in users education

[Alexandre Chapellon]

Le 17/08/2011 16:35, Eric Shubert a écrit :

On 08/17/2011 07:24 AM, Alexandre Chapellon wrote:



Le 17/08/2011 16:05, Laurent CARON a écrit :

On 17/08/2011 16:00, Alexandre Chapellon wrote:
Is there any way to achieve this with dovecot? Does anybody have 
another

idea smoothly force used to switch to TLS?


Hi,

Maybe by sending them an email with a deadline for the end of clear
text auth support ?

If they don't amend their setup they'll be unable to retrieve their
emails.

:)... already tried this in the past and it just don't work... 80% of
users never apply changes and prefer getting very angry and call the
support. Which is exactly what I want to avoid.


Should you want to go the "nicer" way, you could throttle bandwidth to
port 110/143 provided you use those for insecure connections.

This sounds better and I though tc could help going that way, but there
is nothing informative in going this way. I know what I ask for seems
crappy and probably is out of the scope of what dovecot is supposed to
do, but this would be temporary and I wanna make sure it is not possible
before digging somewhere else.

Thanks



I think I would write a script that would glean such accounts from the 
dovecot log, then send them a message every day instructing them how 
to turn on TLS in order to quit getting this message. A support line 
to call for help would be nice for those who have difficulty changing 
their configuration.



I didn't think about that It's quite basic but i like that.

Thanks

--

<>

Re: [Dovecot] mail spool filesystem

[Adrian Ulrich]

> I read that XFS is a good choice, but is not 
> too reliable...

Are you using Maildir or MBOX?

In any case: XFS would be my last choice:

XFS is nice if you are working with large files (> 2GB), but
for E-Mail i'd stick with ext3 (or maybe even reiser3)
as it works very well with small files.

If performance is a problem (iostat output?): Mount it with 'noatime'
or/and use a special device for the journal.


Regards,
 Adrian

Re: [Dovecot] May Dovecot help in users education

[Eric Shubert]

On 08/17/2011 07:24 AM, Alexandre Chapellon wrote:



Le 17/08/2011 16:05, Laurent CARON a écrit :

On 17/08/2011 16:00, Alexandre Chapellon wrote:

Is there any way to achieve this with dovecot? Does anybody have another
idea smoothly force used to switch to TLS?


Hi,

Maybe by sending them an email with a deadline for the end of clear
text auth support ?

If they don't amend their setup they'll be unable to retrieve their
emails.

:)... already tried this in the past and it just don't work... 80% of
users never apply changes and prefer getting very angry and call the
support. Which is exactly what I want to avoid.


Should you want to go the "nicer" way, you could throttle bandwidth to
port 110/143 provided you use those for insecure connections.

This sounds better and I though tc could help going that way, but there
is nothing informative in going this way. I know what I ask for seems
crappy and probably is out of the scope of what dovecot is supposed to
do, but this would be temporary and I wanna make sure it is not possible
before digging somewhere else.

Thanks



I think I would write a script that would glean such accounts from the 
dovecot log, then send them a message every day instructing them how to 
turn on TLS in order to quit getting this message. A support line to 
call for help would be nice for those who have difficulty changing their 
configuration.


--
-Eric 'shubes'

Re: [Dovecot] May Dovecot help in users education

[Alexandre Chapellon]

Le 17/08/2011 16:05, Laurent CARON a écrit :

On 17/08/2011 16:00, Alexandre Chapellon wrote:

Is there any way to achieve this with dovecot? Does anybody have another
idea smoothly force used to switch to TLS?


Hi,

Maybe by sending them an email with a deadline for the end of clear 
text auth support ?


If they don't amend their setup they'll be unable to retrieve their 
emails.
:)... already tried this in the past and it just don't work... 80% of 
users never apply changes and prefer getting very angry and call the 
support. Which is exactly what I want to avoid.


Should you want to go the "nicer" way, you could throttle bandwidth to 
port 110/143 provided you use those for insecure connections.
This sounds better and I though tc could help going that way, but there 
is nothing informative in going this way. I know what I ask for seems 
crappy and probably is out of the scope of what dovecot is supposed to 
do, but this would be temporary and I wanna make sure it is not possible 
before digging somewhere else.


Thanks

--

<>

Re: [Dovecot] mail spool filesystem

[Morten Stevens]

On Wed, 17 Aug 2011 10:23:24 -0300, Julio Cesar Covolato wrote:


 I´ll make a separate partition (raid 1) for the mail spool
(/var/spool/vmail) and want to now what type of filesystem to use on
it to increase performance. I read that XFS is a good choice, but is
not too reliable...


XFS is reliable.

I recommend ext4 or xfs. Both are very good reliable filesystems.

You should rather worry about the mailboxformat. The performance 
difference is much greater than xfs or ext4.


Best regards,

Morten

Re: [Dovecot] May Dovecot help in users education

[Laurent CARON]

On 17/08/2011 16:00, Alexandre Chapellon wrote:

Is there any way to achieve this with dovecot? Does anybody have another
idea smoothly force used to switch to TLS?


Hi,

Maybe by sending them an email with a deadline for the end of clear text 
auth support ?


If they don't amend their setup they'll be unable to retrieve their emails.

Should you want to go the "nicer" way, you could throttle bandwidth to 
port 110/143 provided you use those for insecure connections.

Re: [Dovecot] May Dovecot help in users education

[Alexandre Chapellon]

Hello,

I was wondering if dovecot could help me in my project to smoothly make 
all my users switch to TLS encrypted POP / IMAP sessions and forget 
about cleartext.
My first idea was to setup dovecot as a POP/IMAP  proxy for my mailhosts 
and ask dovecot to display a warning message or slowdown non TLS sessions.
Is there any way to achieve this with dovecot? Does anybody have another 
idea smoothly force used to switch to TLS?


Regards.

P.S: double posted because previous was HTML and I've seen some MUA 
fails to display it properly... sorry will only send raw text now.
<>

Re: [Dovecot] mail spool filesystem

[Johan Hendriks]

Julio Cesar Covolato schreef:

. I read that XFS is a good choice, but is not too reliable...



I did not know FreeBSD had XFS.

Well serieus now, be a little more specific.
Which OS and so on.

regards,
Johan Hendriks

Re: [Dovecot] mail spool filesystem

[Marcin Mirosław]

W dniu 17.08.2011 15:23, Julio Cesar Covolato pisze:

Hi!


Hello!


I read that XFS is a good choice, but is not
too reliable...


Why? Who wrote this? And when? In 2005 year? :)

[Dovecot] mail spool filesystem

[Julio Cesar Covolato]

Hi!

I´m about to migrate a system whith 5000 accounts whith (~ 500GB) from 
"postfix/courier-imap/maildrop/mysql" to a new hardware whith 
"postfix/dovecot/dovecot/mysql".


 I´ll make a separate partition (raid 1) for the mail spool 
(/var/spool/vmail) and want to now what type of filesystem to use on it 
to increase performance. I read that XFS is a good choice, but is not 
too reliable...


Any sugestions?

Thanks in advance,

--
-
_Julio Cesar Covolato
   0v0
  /(_)\  F: 55-11-3129-3366
   ^ ^   PSI INTERNET
-

Re: [Dovecot] Segmentation fault in dovecot director lmtp service

[Reinhard Vicinus]

On 17/08/11 14:12, Thierry de Montaudry wrote:

On 17 Aug 2011, at 13:42, Reinhard Vicinus wrote:


Hi,


the lmtp service of our dovecot director installation quits with a
segmentation fault if a lot of mails are simultaneously delivered.
For example if the postfix mailqueue is filled (for whatever reason)
and postqueue -f is run the lmtp service quits with a segmentation
fault:


Program terminated with signal 11, Segmentation fault.

#0  o_stream_cork (stream=0x0) at ostream.c:75

75  if (unlikely(stream->closed))

(gdb) backtrace

#0  o_stream_cork (stream=0x0) at ostream.c:75

#1  0x7fa6e6af45d9 in lmtp_client_send_more (client=0x2435870)
at lmtp-client.c:596

#2  0x02434170 in ?? ()

#3  0x004070d9 in proxy_send_more (proxy=0x2435870) at
lmtp-proxy.c:390

#4  lmtp_proxy_data_input (proxy=0x2435870) at lmtp-proxy.c:444

#5  0x7fa6e6af456f in lmtp_client_send_data (client=0x24347a0)
at lmtp-client.c:306

#6  0x02434f98 in ?? ()

#7  0xe6af73c5 in ?? ()

#8  0x02434840 in ?? ()

#9  0x in ?? ()


I don't have any ideas why the stream is 0. The configuration of the
dovecot director installation is attached. Please let me know if i
shall provide any more information or test something.


Kind regards

Reinhard



Hi,

You might need to limit the concurrent deliveries from postfix.
Check the maxproc parameter in your master.conf, which is 100 by default. You 
should reduce it to some lower value, I would say between 10 and 40 depending 
on your system. That would allow your queues to grow without putting too much 
stress on the deliveries, even when forcing it with postqueue -f.

Regards,

Thierry


Hi,

i don't think this problem is load related, because the load on the mail 
servers is generally around 0.1-0.2, the queue contained only 22 
messages and the only reason the queues was growing were that i stopped 
the dovecot director instance on this mailserver.


Kind regards
Reinhard

Re: [Dovecot] Segmentation fault in dovecot director lmtp service

[Per Jessen]

Thierry de Montaudry wrote:

> On 17 Aug 2011, at 13:42, Reinhard Vicinus wrote:
> 
>> Hi,
>> 
>> 
>>the lmtp service of our dovecot director installation quits with a
>>segmentation fault if a lot of mails are simultaneously delivered.
>>For example if the postfix mailqueue is filled (for whatever
>>reason) and postqueue -f is run the lmtp service quits with a
>>segmentation fault:
>> 
>> 
>>Program terminated with signal 11, Segmentation fault.
>> 
>>#0  o_stream_cork (stream=0x0) at ostream.c:75
>> 
>>75  if (unlikely(stream->closed))
>> 
>>(gdb) backtrace
>> 
>>#0  o_stream_cork (stream=0x0) at ostream.c:75
>> 
>>#1  0x7fa6e6af45d9 in lmtp_client_send_more (client=0x2435870)
>>at lmtp-client.c:596
>> 
>>#2  0x02434170 in ?? ()
>> 
>>#3  0x004070d9 in proxy_send_more (proxy=0x2435870) at
>>lmtp-proxy.c:390
>> 
>>#4  lmtp_proxy_data_input (proxy=0x2435870) at lmtp-proxy.c:444
>> 
>>#5  0x7fa6e6af456f in lmtp_client_send_data (client=0x24347a0)
>>at lmtp-client.c:306
>> 
>>#6  0x02434f98 in ?? ()
>> 
>>#7  0xe6af73c5 in ?? ()
>> 
>>#8  0x02434840 in ?? ()
>> 
>>#9  0x in ?? ()
>> 
>> 
>>I don't have any ideas why the stream is 0. The configuration of
>>the dovecot director installation is attached. Please let me know
>>if i shall provide any more information or test something.
>> 
>> 
>>Kind regards
>> 
>>Reinhard
>> 
> 
> 
> Hi,
> 
> You might need to limit the concurrent deliveries from postfix.
> Check the maxproc parameter in your master.conf, which is 100 by
> default. You should reduce it to some lower value, I would say between
> 10 and 40 depending on your system. That would allow your queues to
> grow without putting too much stress on the deliveries, even when
> forcing it with postqueue -f.

Regardless, Reinhard still seem to have stumbled on a bug. 


/Per Jessen, Zürich

Re: [Dovecot] Segmentation fault in dovecot director lmtp service

[Thierry de Montaudry]

On 17 Aug 2011, at 13:42, Reinhard Vicinus wrote:

> Hi,
> 
> 
>the lmtp service of our dovecot director installation quits with a
>segmentation fault if a lot of mails are simultaneously delivered.
>For example if the postfix mailqueue is filled (for whatever reason)
>and postqueue -f is run the lmtp service quits with a segmentation
>fault:
> 
> 
>Program terminated with signal 11, Segmentation fault.
> 
>#0  o_stream_cork (stream=0x0) at ostream.c:75
> 
>75  if (unlikely(stream->closed))
> 
>(gdb) backtrace
> 
>#0  o_stream_cork (stream=0x0) at ostream.c:75
> 
>#1  0x7fa6e6af45d9 in lmtp_client_send_more (client=0x2435870)
>at lmtp-client.c:596
> 
>#2  0x02434170 in ?? ()
> 
>#3  0x004070d9 in proxy_send_more (proxy=0x2435870) at
>lmtp-proxy.c:390
> 
>#4  lmtp_proxy_data_input (proxy=0x2435870) at lmtp-proxy.c:444
> 
>#5  0x7fa6e6af456f in lmtp_client_send_data (client=0x24347a0)
>at lmtp-client.c:306
> 
>#6  0x02434f98 in ?? ()
> 
>#7  0xe6af73c5 in ?? ()
> 
>#8  0x02434840 in ?? ()
> 
>#9  0x in ?? ()
> 
> 
>I don't have any ideas why the stream is 0. The configuration of the
>dovecot director installation is attached. Please let me know if i
>shall provide any more information or test something.
> 
> 
>Kind regards
> 
>Reinhard
> 


Hi,

You might need to limit the concurrent deliveries from postfix.
Check the maxproc parameter in your master.conf, which is 100 by default. You 
should reduce it to some lower value, I would say between 10 and 40 depending 
on your system. That would allow your queues to grow without putting too much 
stress on the deliveries, even when forcing it with postqueue -f.

Regards,

Thierry

[Dovecot] Segmentation fault in dovecot director lmtp service

[Reinhard Vicinus]

Hi,


the lmtp service of our dovecot director installation quits with a
segmentation fault if a lot of mails are simultaneously delivered.
For example if the postfix mailqueue is filled (for whatever reason)
and postqueue -f is run the lmtp service quits with a segmentation
fault:


Program terminated with signal 11, Segmentation fault.

#0  o_stream_cork (stream=0x0) at ostream.c:75

75  if (unlikely(stream->closed))

(gdb) backtrace

#0  o_stream_cork (stream=0x0) at ostream.c:75

#1  0x7fa6e6af45d9 in lmtp_client_send_more (client=0x2435870)
at lmtp-client.c:596

#2  0x02434170 in ?? ()

#3  0x004070d9 in proxy_send_more (proxy=0x2435870) at
lmtp-proxy.c:390

#4  lmtp_proxy_data_input (proxy=0x2435870) at lmtp-proxy.c:444

#5  0x7fa6e6af456f in lmtp_client_send_data (client=0x24347a0)
at lmtp-client.c:306

#6  0x02434f98 in ?? ()

#7  0xe6af73c5 in ?? ()

#8  0x02434840 in ?? ()

#9  0x in ?? ()


I don't have any ideas why the stream is 0. The configuration of the
dovecot director installation is attached. Please let me know if i
shall provide any more information or test something.


Kind regards

Reinhard
dovecot -c /etc/dovecot-director/dovecot-director.conf -n
# 2.0.13 (537d4b6d9a7a): /etc/dovecot-director/dovecot-director.conf
# OS: Linux 2.6.32-27-server x86_64 Ubuntu 10.04.1 LTS nfs
auth_verbose = yes
base_dir = /var/run/dovecot-director/
deliver_log_format = director msgid=%m: %$
director_mail_servers = 10.129.3.190-10.129.3.193
director_servers = 10.129.3.193:9090 10.129.3.192:9090 10.129.3.191:9090 
10.129.3.190:9090
info_log_path = /var/log/dovecot-director-debug.log
lmtp_proxy = yes
log_path = /var/log/dovecot-director.log
login_log_format = director %$: %s
mail_debug = yes
mail_gid = vmail
mail_location = mdbox:/mail/dovecot/%d/%n/mail:INDEX=/data/dovecot/%d/%n
mail_log_prefix = "director %s(%u): "
mail_nfs_storage = yes
mail_privileged_group = vmail
mail_uid = vmail
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope encoded-character 
vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy 
include variables body enotify environment mailbox date ihave
passdb {
  args = proxy=y nopassword=y user=%n@dovecottest.%d
  driver = static
}
plugin {
  sieve = ~/.dovecot.sieve
  sieve_dir = ~/sieve
}
protocols = imap pop3 lmtp
service auth {
  unix_listener auth-userdb {
user = dovecot
  }
}
service director {
  fifo_listener login/proxy-notify {
mode = 0666
  }
  inet_listener {
port = 9090
  }
  unix_listener director-userdb {
mode = 0600
  }
  unix_listener login/director {
mode = 0666
  }
}
service imap-login {
  executable = imap-login director
  inet_listener imap {
port = 20143
  }
  inet_listener imaps {
port = 20993
ssl = yes
  }
}
service lmtp {
  inet_listener lmtp {
address = *
port = 20024
  }
}
service pop3-login {
  executable = pop3-login director
  inet_listener pop3 {
port = 20110
  }
  inet_listener pop3s {
port = 20995
ssl = yes
  }
}
ssl_cert = 

[Dovecot] May Dovecot help in users education

[Alexandre Chapellon]

<><>

Re: [Dovecot] Dovecot-Antispam 2.0 with SpamAssassin (sa-learn)

[Tom Hendrikx]

On 17/08/11 08:26, Nikita Koshikov wrote:
> On Tue, 16 Aug 2011 22:38:34 +0200
> Nick Rosier wrote:
> 
>> Hi,
>>
>> has anyone figured out how to use the dovecot-antispam plugin with 
>> sa-learn? I need to pass the username (u...@domain.tld) to sa-learn and 
>> --ham or --spam depending on the move. I was thinking of using the CRM14 
>> option and replace the command and arguments but cannot find anything 
>> about the ability to pass the username.
>> Any pointers would be welcome.
>>
>> N.
> Write a wrapper on sa-learn. The script should parse env first and that exec 
> learning with appropriative args, like:
> antispam_mail_sendmail = /etc/dovecot/plugins/spam.sh
> 
> Scrip, something like:
> #!/bin/bash
> 
> (
> env > /tmp/antispam.$$
> /usr/bin/sa-learn $@
> exit 0
> )
> search for PWD environment in  /tmp/antispam.$$ .
> 
> 

I use the dspam backend and pass the user into the commandline with %u,
which seems to work, but is not documented in the man page.

To be clear, this is with the plugin from:
http://wiki2.dovecot.org/Plugins/Antispam

-- 
Regards,
Tom