Re: [Dovecot] dovecot-antispam-1.3 multiple plugin load

2010-10-24 Thread Antonio Perez-Aranda
I need to detect when a mail is moved to a specific folder.

  It's mail is moved to folder1, then exec script 1
  It's mail is moved to folder2, then exec script 2

One of this scripts it's a mark as ham, It removes -SPAM- mark from
subject, pass to spamassassin to learn as harm and then, leave the
mail where it came from, or inbox.

2010/10/24 Eugene Paskevich eug...@raptor.kiev.ua:
 On Sun, Oct 24, 2010 at 02:20:03AM +0200, Antonio Perez-Aranda wrote:
 I have running dovecot-1.2.15 and I try whith dovecot-antispam-1.3 and
 1.2-* if it's running for me.

 I use mailtrain backend to call a script when I move a mail to a
 specific folder. Then, I set allow_append_to_spam: yes

 At .config for Make dovecot-antispam. I set the plugin's name to:

 PLUGINNAME=isspam

 An then, I have another copy of the sources and .config with plugin's
 name set to:

 PLUGINNAME=nospam

 With this. If I put on dovecot.conf

 protocol imap {
 ...
   mail_plugins = isspam nospam
 ...
 }

 When I try to login, the connection is aborted and dovecot connection
 die with coredump


 Are there are any people with similar settings ?

 (doble instance of antispam plugin)

 Could you please elaborate why you need to load multiple plugin instances
 simultaneously?

 --
 Eugene Paskevich             |   *==)---   |     Plug me into
 eug...@raptor.kiev.ua        |   ---(==*   |      The Matrix



Re: [Dovecot] Maintenance instance

2010-10-24 Thread Edgar Fuß
 and gives any user logging in a canned mail
 (e.g. We're doing maintenance, go away)
Wouldn't a client that keeps local copies of all IMAP boxes then synchronize to 
that canned state, i.e., delete all locally cached mails?


Re: [Dovecot] Maintenance instance

2010-10-24 Thread Patrick Ben Koetter
* Edgar Fuß e...@math.uni-bonn.de:
  and gives any user logging in a canned mail
  (e.g. We're doing maintenance, go away)
 Wouldn't a client that keeps local copies of all IMAP boxes then synchronize
 to that canned state, i.e., delete all locally cached mails?

See Alerts in http://wiki2.dovecot.org/PostLoginScripting.

p...@rick



-- 
state of mind
Digitale Kommunikation

http://www.state-of-mind.de

Franziskanerstraße 15  Telefon +49 89 3090 4664
81669 München  Telefax +49 89 3090 4666

Amtsgericht MünchenPartnerschaftsregister PR 563



Re: [Dovecot] dovecot-antispam-1.3 multiple plugin load

2010-10-24 Thread Antonio Perez-Aranda
Well,

At present, I modify dovecot-antispam-1.3 for dovecot-1.2 to allow a
nospam folder, and it's running.

I think, that a plugin that catch moved to a specific folder or assign
a keyword and exec script could be useful for anyone.

NOTE: It's my first code change on any dovecot/plugins code.

2010/10/24 Antonio Perez-Aranda aperezara...@yaco.es:
 I need to detect when a mail is moved to a specific folder.

  It's mail is moved to folder1, then exec script 1
  It's mail is moved to folder2, then exec script 2

 One of this scripts it's a mark as ham, It removes -SPAM- mark from
 subject, pass to spamassassin to learn as harm and then, leave the
 mail where it came from, or inbox.

 2010/10/24 Eugene Paskevich eug...@raptor.kiev.ua:
 On Sun, Oct 24, 2010 at 02:20:03AM +0200, Antonio Perez-Aranda wrote:
 I have running dovecot-1.2.15 and I try whith dovecot-antispam-1.3 and
 1.2-* if it's running for me.

 I use mailtrain backend to call a script when I move a mail to a
 specific folder. Then, I set allow_append_to_spam: yes

 At .config for Make dovecot-antispam. I set the plugin's name to:

 PLUGINNAME=isspam

 An then, I have another copy of the sources and .config with plugin's
 name set to:

 PLUGINNAME=nospam

 With this. If I put on dovecot.conf

 protocol imap {
 ...
   mail_plugins = isspam nospam
 ...
 }

 When I try to login, the connection is aborted and dovecot connection
 die with coredump


 Are there are any people with similar settings ?

 (doble instance of antispam plugin)

 Could you please elaborate why you need to load multiple plugin instances
 simultaneously?

 --
 Eugene Paskevich             |   *==)---   |     Plug me into
 eug...@raptor.kiev.ua        |   ---(==*   |      The Matrix




[Dovecot] different certificates on different services ?

2010-10-24 Thread ckubu
Hi,

on dovecot 2.0.x, is it possible to serve different certificates on different 
services (pops,imaps) with one dovecot instance ?

regards,
Christoph Kuchenbuch


Re: [Dovecot] Maintenance instance

2010-10-24 Thread Ralf Hildebrandt
* Edgar Fuß e...@math.uni-bonn.de:
  and gives any user logging in a canned mail
  (e.g. We're doing maintenance, go away)

 Wouldn't a client that keeps local copies of all IMAP boxes then
 synchronize to that canned state, i.e., delete all locally cached
 mails?

Well, I don't know. Some clients see the absence of the IMAP server as
an opportunity to ask the user if the saved password is still correct.

-- 
Ralf Hildebrandt
  Geschäftsbereich IT | Abteilung Netzwerk
  Charité - Universitätsmedizin Berlin
  Campus Benjamin Franklin
  Hindenburgdamm 30 | D-12203 Berlin
  Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
  ralf.hildebra...@charite.de | http://www.charite.de



Re: [Dovecot] Maintenance instance

2010-10-24 Thread Ralf Hildebrandt
* Patrick Ben Koetter p...@state-of-mind.de:
 * Edgar Fuß e...@math.uni-bonn.de:
   and gives any user logging in a canned mail
   (e.g. We're doing maintenance, go away)
  Wouldn't a client that keeps local copies of all IMAP boxes then synchronize
  to that canned state, i.e., delete all locally cached mails?
 
 See Alerts in http://wiki2.dovecot.org/PostLoginScripting.

Not all clients show the alerts, even though IMAP RFC requires it.
let me guess: Outlook is one of those? If so: Useless.


-- 
Ralf Hildebrandt
  Geschäftsbereich IT | Abteilung Netzwerk
  Charité - Universitätsmedizin Berlin
  Campus Benjamin Franklin
  Hindenburgdamm 30 | D-12203 Berlin
  Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
  ralf.hildebra...@charite.de | http://www.charite.de



Re: [Dovecot] different certificates on different services ?

2010-10-24 Thread ckubu
hi,

 on dovecot 2.0.x, is it possible to serve different certificates on
 different services (pops,imaps) with one dovecot instance ?

tamsy pointet me to the dovecot wiki: 
   http://wiki2.dovecot.org/SSL/DovecotConfiguration

thanks, and sorry for not looking there..

regards,
Christoph




Re: [Dovecot] Maintenance instance

2010-10-24 Thread Patrick Ben Koetter
* Ralf Hildebrandt dovecot@dovecot.org:
 * Patrick Ben Koetter p...@state-of-mind.de:
  * Edgar Fuß e...@math.uni-bonn.de:
and gives any user logging in a canned mail
(e.g. We're doing maintenance, go away)
   Wouldn't a client that keeps local copies of all IMAP boxes then 
   synchronize
   to that canned state, i.e., delete all locally cached mails?
  
  See Alerts in http://wiki2.dovecot.org/PostLoginScripting.
 
 Not all clients show the alerts, even though IMAP RFC requires it.
 let me guess: Outlook is one of those? If so: Useless.

Test it.

p...@rick

-- 
state of mind
Digitale Kommunikation

http://www.state-of-mind.de

Franziskanerstraße 15  Telefon +49 89 3090 4664
81669 München  Telefax +49 89 3090 4666

Amtsgericht MünchenPartnerschaftsregister PR 563



Re: [Dovecot] fallocate and glibc 2.10

2010-10-24 Thread Jerry
On Sun, 24 Oct 2010 15:10:08 +0100
Timo Sirainen t...@iki.fi articulated:

 On 22.10.2010, at 19.22, Paul Howarth wrote:
 
  In glibc 2.10 (32 bit) fallocate() exists but fallocate64() doesn't.
  When _FILE_OFFSET_BITS==64, fallocate() is a redirect to
  fallocate64() and the program can't be linked (fails to find symbol
  fallocate64). See http://bugzilla.redhat.com/500487
 
 Yeah, I knew about it happening also on Ubuntu 9.10.
 
  Attached patch detects fallocate() more robustly to guard against
  this problem.
 
 A lot of code just to work around a bug that apparently only exists
 in Ubuntu 9.10 and Fedora 11. Is there a reason for anyone to be
 actually using either of them? I was thinking about just ignoring
 this problem.

Assuming that this is truly an isolated issue; it is my belief that
creating a specific patch to address this issue might lead to a
regression error at some point down the line. I would suggest that you
simply ignore the issue and let the end user properly update his system
to eliminate the problem. Perhaps placing something in the Dovecot
documentation to this effect would be advisable. If the end user wishes
to patch their system to do an end run around this issue, they are free
to do so. However, they should be forewarned that they are doing so at
their own peril and sans any support from you if a problem(s) occur.

Just my 2¢.

-- 
Jerry ✌
dovecot.u...@seibercom.net

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__



Re: [Dovecot] fallocate and glibc 2.10

2010-10-24 Thread William Blunn

On 24/10/2010 15:10, Timo Sirainen wrote:
A lot of code just to work around a bug that apparently only exists in 
Ubuntu 9.10 and Fedora 11. Is there a reason for anyone to be actually 
using either of them? I was thinking about just ignoring this problem.


I thought you were fixing bugs coming out of running Dovecot over BSDI 
in order to make Dovecot *generally* more robust. (Well that was the 
only explanation I could think of for adding support for a dead OS...)


I would imaging Ubuntu 9.10 and Fedora 11 to be, much less dead than BSDI.

You may find that hosting providers only have support for certain spot 
versions of distros, and besides people may have reasons to stick with 
the distro they are on.


So it may be worth just doing it, especially if the reporter has 
supplied a patch!


Bill


Re: [Dovecot] Maintenance instance

2010-10-24 Thread Timo Sirainen
On 24.10.2010, at 11.36, Edgar Fuß wrote:

 and gives any user logging in a canned mail
 (e.g. We're doing maintenance, go away)
 Wouldn't a client that keeps local copies of all IMAP boxes then synchronize 
 to that canned state, i.e., delete all locally cached mails?

I'm pretty sure they will. I'm not aware of any good way to handle this, other 
than ALERTs.



Re: [Dovecot] Maintenance instance

2010-10-24 Thread Ralf Hildebrandt
* Timo Sirainen t...@iki.fi:
 On 24.10.2010, at 11.36, Edgar Fuß wrote:
 
  and gives any user logging in a canned mail
  (e.g. We're doing maintenance, go away)
  Wouldn't a client that keeps local copies of all IMAP boxes then 
  synchronize to that canned state, i.e., delete all locally cached mails?
 
 I'm pretty sure they will. I'm not aware of any good way to handle this, 
 other than ALERTs.

Hm, OK.
Maybe the alert idea is the best idea so far.

-- 
Ralf Hildebrandt
  Geschäftsbereich IT | Abteilung Netzwerk
  Charité - Universitätsmedizin Berlin
  Campus Benjamin Franklin
  Hindenburgdamm 30 | D-12203 Berlin
  Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
  ralf.hildebra...@charite.de | http://www.charite.de



Re: [Dovecot] Maintenance instance

2010-10-24 Thread Michael M. Slusarz

Quoting Timo Sirainen t...@iki.fi:


On 24.10.2010, at 11.36, Edgar Fuß wrote:


and gives any user logging in a canned mail
(e.g. We're doing maintenance, go away)

Wouldn't a client that keeps local copies of all IMAP boxes then
synchronize to that canned state, i.e., delete all locally cached
mails?


I'm pretty sure they will. I'm not aware of any good way to handle
this, other than ALERTs.


Isn't this the exact reason to return the UNAVAILABLE response (RFC 5530)?

   UNAVAILABLE
 Temporary failure because a subsystem is down.  For example, an
 IMAP server that uses a Lightweight Directory Access Protocol
 (LDAP) or Radius server for authentication might use this
 response code when the LDAP/Radius server is down.

 C: a LOGIN fred foo
 S: a NO [UNAVAILABLE] User's backend down for maintenance



[Dovecot] Public Folders for spam/nospam - don't get it

2010-10-24 Thread Denny Schierz
hi,

Dovecot: 2.0.5

I want to use public folders (maildir), for my spam mails to feed
spamassassin, but I don't get it working. My Evolution 2.28.3 (nothing
else tested) can't subscribe the folders:

  namespace {
  hidden = no
  inbox = yes
  list = yes
  location = 
  prefix = INBOX/
  separator = /
  subscriptions = yes
  type = private
}
namespace {
  hidden = no
  inbox = no
  list = children
  location = maildir:/home/vmail/public:LAYOUT=fs
  prefix = public/
  separator = /
  subscriptions = no
  type = public
}

angelica:/etc/dovecot/conf.d# ls -l /home/vmail/public/
total 24
-rw-r--r-- 1 vmail vmail   11 Oct 23 14:14 dovecot-acl
-rw--- 1 vmail vmail   45 Oct 23 13:56 dovecot-acl-list
-rw--- 1 vmail vmail   48 Oct 24 19:22 dovecot.mailbox.log
drwxr-xr-x 2 vmail vmail 4096 Oct 23 14:03 nospam
drwxr-xr-x 2 vmail vmail 4096 Oct 23 14:03 spam
-rw--- 1 vmail vmail   12 Oct 24 19:22 subscriptions

# cat /home/vmail/public/dovecot-acl
anyone lrp, also in subfolders spam/nospam

I tested several configurations, but nothing works. Sometimes I can see
the folders, but can't subscribe them (invalid/unknown namespace),
sometime I don't see the folders ...

does anyone has an answer for me ?

cu denny


signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil


Re: [Dovecot] fallocate and glibc 2.10

2010-10-24 Thread Paul Howarth
On Sun, 24 Oct 2010 20:26:51 +0100
Timo Sirainen t...@iki.fi wrote:

 On 24.10.2010, at 20.16, Paul Howarth wrote:
 
  A lot of code just to work around a bug that apparently only exists
  in Ubuntu 9.10 and Fedora 11. Is there a reason for anyone to be
  actually using either of them? I was thinking about just ignoring
  this problem.
  
  Don't know about Ubuntu but Fedora 11 is already EOL'ed so there's
  no need to fix it for that. Didn't realise that glibc 2.10 was that
  rare.
 
 So how did you notice this problem then, and do you really care if I
 fix it? :)

I noticed it because I build dovecot packages for lots of Fedora and Red
Hat releases, including some EOL ones
(http://mirror.city-fan.org/ftp/contrib/mail/) and the 32-bit Fedora 11
build fell over due to this problem.

I'm not too bothered if it doesn't get fixed as clearly I'm able to
work around the issue. Currently I'm using the patch I posted earlier
as that was an upstreamable fix but I'll probably end up with a
quick, simpler hack specific to Fedora 11 32-bit if you decide not to
fix it.

Paul.


Re: [Dovecot] fallocate and glibc 2.10

2010-10-24 Thread Stan Hoeppner
Paul Howarth put forth on 10/24/2010 2:16 PM:

 Don't know about Ubuntu but Fedora 11 is already EOL'ed so there's no
 need to fix it for that. Didn't realise that glibc 2.10 was that rare.

How old is glibc 2.10?

I thought Debian Lenny (which I use) was old.  It's approaching two
years since release.  It currently has glibc 2.7, which was apparently
released in 2007, 3 years ago.  This would lead me to belive that glibc
2.10 is _very_ old.  I'm not very familiar with glibc.  Maybe age
doesn't matter?

-- 
Stan


Re: [Dovecot] fallocate and glibc 2.10

2010-10-24 Thread Karsten Bräckelmann
On Sun, 2010-10-24 at 18:02 -0500, Stan Hoeppner wrote:
  Don't know about Ubuntu but Fedora 11 is already EOL'ed so there's no
  need to fix it for that. Didn't realise that glibc 2.10 was that rare.
 
 How old is glibc 2.10?
 
 I thought Debian Lenny (which I use) was old.  It's approaching two
 years since release.  It currently has glibc 2.7, which was apparently
 released in 2007, 3 years ago.  This would lead me to belive that glibc
 2.10 is _very_ old.  I'm not very familiar with glibc.  Maybe age
 doesn't matter?

It's a version number, generally major.minor.micro. It's not a floating
point number.

7  10, and thus 2.7 is older than 2.10.


-- 
char *t=\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4;
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;il;i++){ i%8? c=1:
(c=*++x); c128  (s+=h); if (!(h=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}



Re: [Dovecot] fallocate and glibc 2.10

2010-10-24 Thread Stan Hoeppner
Karsten Bräckelmann put forth on 10/24/2010 6:34 PM:
 On Sun, 2010-10-24 at 18:02 -0500, Stan Hoeppner wrote:
 Don't know about Ubuntu but Fedora 11 is already EOL'ed so there's no
 need to fix it for that. Didn't realise that glibc 2.10 was that rare.

 How old is glibc 2.10?

 I thought Debian Lenny (which I use) was old.  It's approaching two
 years since release.  It currently has glibc 2.7, which was apparently
 released in 2007, 3 years ago.  This would lead me to belive that glibc
 2.10 is _very_ old.  I'm not very familiar with glibc.  Maybe age
 doesn't matter?
 
 It's a version number, generally major.minor.micro. It's not a floating
 point number.
 
 7  10, and thus 2.7 is older than 2.10.

Ahh, thanks for pointing out my error.  I was thinking 2.1 not 2.10.
 So I'm on a much older version of glibc.  I guess since I stick with
distro packages I'm safe from this particular problem, since such
packages are compiled against the glibc 2.7 of the distro.

-- 
Stan