date:20090810

Re: [Dovecot] Released Sieve v0.1.11 and ManageSieve v0.11.8 for Dovecot v1.2.3

2009-08-10 Thread Michal Hlavinka

 Hello Dovecot users,

Hi,

 Apart from unfinished development of the date extension, this is a set
 of bug-fix releases. A few portability issues were found, a few
 stupidities were fixed and the ManageSieve proxy now also works with
 TLS. Most notably, the include extension had an issue regarding  the
 expansion of $HOME in the personal include path.

 I've built a project site at: http://pigeonhole.dovecot.org

 Changelog Sieve v0.1.11:

  + Built skeleton implementation for the date extension (RFC5260).
It compiles, but it does not do anything useful yet. Therefore, it
is not part of the default compilation.
  - Fixed ARM portability issues caused by char type not being signed
on that platform. Reading optional operands from a binary would
fail for action side effects. Also, an accidental mixup of an int
return type with bool caused the interpreter to continue on ARM
even though an error occured.
  - Removed direct stdint.h includes to prevent portability issues.
  - Fixed segfault bug in the handling of script open failures.
  - Include: improved user error messages and system log messages.
  - Fixed copy-paste mixup between sieve_after and sieve_before
settings in the LDA Sieve plugin. If only a sieve_after script was
active, nothing would have been executed. Patch by Mike Abbott.
  - Include: fixed a bug in HOME substitution in the sieve_dir path.
Surfaced in ManageSieve.


...

 Have fun testing the new releases and don't hesitate to notify me when
 there are problems.

build process for Sieve fails when --with-unfinished-features option is set:
...
make[2]: Entering directory 
`/home/mihl/myroot/job/cvsf/dovecot/devel/dovecot-1.2.3/dovecot-1.2-
sieve-0.1.11'
make[2]: *** No rule to make target `doc/man/sieve-filter.1', needed by `all-
am'.  Stop.


without this it works.

Regards,
Michal Hlavinka

[Dovecot] how secure is Dovecot when exposed to the Internet?

2009-08-10 Thread Florin Andrei


$ dovecot -n
# 1.1.11: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.28-11-server x86_64 Ubuntu 9.04
protocols: imap imaps managesieve

I need to make an IMAP (actually imaps) server available over the 
Internet. Unfortunately, VPN is not available (not all clients support 
VPN), so I will have to expose the imaps port to the Internet.


My question is: how reliable is Dovecot in such a setup? I am not 
talking about encryption (protecting the traffic between server and 
client). I am talking about having the daemon exposed to anything coming 
in from the Internet, buffer overflows and stuff like that.


What's the security history of this software in situations like this?

--
Florin Andrei

http://florin.myip.org/

Re: [Dovecot] how secure is Dovecot when exposed to the Internet?

2009-08-10 Thread Timo Sirainen


On Aug 10, 2009, at 2:55 AM, Florin Andrei wrote:

My question is: how reliable is Dovecot in such a setup? I am not  
talking about encryption (protecting the traffic between server and  
client). I am talking about having the daemon exposed to anything  
coming in from the Internet, buffer overflows and stuff like that.


What's the security history of this software in situations like this?


http://dovecot.org/security.html

Re: [Dovecot] how secure is Dovecot when exposed to the Internet?

2009-08-10 Thread Florin Andrei


Timo Sirainen wrote:


http://dovecot.org/security.html


OK, that's pretty convincing. Thanks.

--
Florin Andrei

http://florin.myip.org/

Re: [Dovecot] Released Sieve v0.1.11 and ManageSieve v0.11.8 for Dovecot v1.2.3

2009-08-10 Thread Wolfgang . Friebel

On Mon, 10 Aug 2009, Michal Hlavinka wrote:

build process for Sieve fails when --with-unfinished-features option is set:
...
make[2]: Entering directory
`/home/mihl/myroot/job/cvsf/dovecot/devel/dovecot-1.2.3/dovecot-1.2-
sieve-0.1.11'
make[2]: *** No rule to make target `doc/man/sieve-filter.1', needed by `all-
am'. Stop.

I have added a dummy sieve-filter.1 file to get it going. See the
attachment.

--
Wolfgang Friebel Deutsches Elektronen-Synchrotron DESY
Phone/Fax: +49 33762 77372/216Platanenallee 6
Mail: Wolfgang.Friebel AT desy.de D-15738 Zeuthen Germany.TH SIEVE-FILTER 1 8 August 2009
.SH NAME
sieve-filter \- Sieve filter for the Dovecot secure IMAP server
.SH SYNOPSIS
sieve-filter
[\fB-c\fR]
[\fB-m\fR \fIdefault-mailbox\fR]
[\fB-s\fR \fIscript-file\fR]
[\fB-x\fR \fIextension extension ...\fR]
\fIscript-file\fR \fImail-store\fR \fI[dest-mail-store]\fR
.SH DESCRIPTION
.PP
The \fBsieve-filter\fP command is part of the Sieve implementation for the
Dovecot secure
IMAP server. Sieve (RFC 5228) is a simple and highly extensible language for
filtering
e-mail messages. It can be implemented for any type of mail access protocol,
mail
architecture and operating system. The language cannot execute external
programs and in
its basic form it does not provide the means to cause infinite loops, making it
suitable
for running securely on mail servers where mail users have no permission run
arbitrary programs.
.PP
Using the \fBsieve-filter\fP command,
bla bla (to be done)
.SH OPTIONS
.TP
\fB-c\fP
Force compilation. By default, the compiled binary is stored on disk. When this
binary is found
during the next execution of \fBsieve-filter\fP and its modification time is
more recent than the
script file, it is used and the script is not compiled again. This option
forces the script to be
compiled, thus ignoring any present binary. Refer to \fBsievec\fP(1) for more
information about
Sieve compilation.
.TP
\fB-m\fP \fIdefault-mailbox\fP
The mailbox where the keep action stores the message. This is INBOX by
default.
\fB-s\fP \fIscript-file\fP
Specify additional scripts to be executed before the main script. Multiple
\fB-s\fP arguments are
allowed and the specified scripts are executed sequentially in the order
specified at the command
line.
.TP
\fB-x\fP \fIextension extension ...\fP
Set the available extensions. The parameter is a space-separated list of the
active extensions. By
prepending the extension identifiers with \fB+\fP or \fB-\fP, extensions can be
included or excluded
relative to the default set of extensions. If no extensions have a \fB+\fP or
\fB-\fP prefix, only
those extensions that are explicitly listed will be enabled. Unknown extensions
are ignored and a
warning is produced. By default, all supported extensions are available, except
for deprecated extensions
or those that are still under development.

For example \fB-x\fP +imapflags -enotify will enable the deprecated imapflags
extension along with all
extensions that are available by default, except for the enotify extension.
.SH DEBUG SUPPORT
.PP
To improve script debugging, the Sieve command line tools such as
\fBsieve-filter\fP support a custom
Sieve language extension called 'vnd.dovecot.debug'. It adds the
\fBdebug_print\fP command that allows
printing debug messages to \fBstdout\fP.
.PP
Example:
.PP
require vnd.dovecot.debug;
.PP
if header :contains subject hello {
.PP
debug_print Subject header contains hello!;
.PP
}
.PP
Other tools like \fBsievec\fP and \fBsieved\fP also recognize the
vnd.dovecot.debug extension. In contrast,
the actual Sieve plugin for the Dovecot LDA does not allow the use of the debug
extension. So, keep in mind that
scripts and compiled binaries that refer to de debug extension will fail to be
run by the Sieve plugin itself.
.PP
Note that it is not necessary to enable nor possible to disable the
availability of the debug extension with
the \fB-x\fP option.
.SH AUTHOR
.PP
The Sieve implementation for Dovecot was written by Stephan Bosch
step...@rename-it.nl.
.PP
Dovecot was written by Timo Sirainen t...@iki.fi.
.SH SEE ALSO
.BR sievec (1),
.BR sieved (1)

Re: [Dovecot] More effective mailbox fetching over high RTT link

2009-08-10 Thread Andrzej Adam Filip

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

 On Sun, 2009-08-09 at 22:20 +0200, Andrzej Adam Filip wrote:
 Could you offer some suggestion how to fetch mailbox content over 
 high RTT link (with negligible packet loss)?
 
 Currently I use IMAP+IDLE *but* it fails to use full available bandwidth
 due to high RTT and send command wait for response nature of POP3 and
 IMAP4 protocols.

 I'm not entirely sure what you want. Download all new messages
 automatically whenever they show up?

It is maximum version of what I would like to get.
( maximum: IMAP+IDLE equivalent, acceptable: faster POP3)

 And by mailbox do you mean user or folder? 
 So would you want to download all new mails in all folders?

One folder is acceptable. All folders would be nice.

 And is it ok to create your own software to do the downloading?

I was thinking about creating perl script for the task.

 If all of them were yes, the best you could right now would be to set
 up a virtual all mailbox containing all mailboxes. Then in IDLE you'd
 see whenever new messages pop up and then issue FETCH n:* BODY.PEEK[] or
 whatever. There's also IMAP NOTIFY extension that would allow your
 client to ask server to immediately send the message body instead of the
 client having to ask for it. But Dovecot doesn't currently support that.

 Or if you just always wanted to download all mails, again a virtual
 mailbox and FETCH 1:* BODY.PEEK[] gives you all mails.

-- 
[plen: Andrew] Andrzej Adam Filip : a...@onet.eu
Men never make passes at girls wearing glasses.
  -- Dorothy Parker

Re: [Dovecot] virtual plugin and ACL

2009-08-10 Thread Nikita Koshikov

On Fri, 07 Aug 2009 15:23:32 -0400
Timo Sirainen t...@iki.fi wrote:

 That's because in private namespaces user owns the mails, and
 authenticated doesn't reduce the user's privileges. You could use
 owner instead.
 
 Also I don't think you should use ACLs at all here. It's easier and more
 secure to just make /var/mail/virtual non-writable to imap process. For
 example change file/dir owners to root and make them world-readable.

Thank you, Timo.

Both variants are working fine for me.

[Dovecot] inconsistency with expire-tool and expire dict

2009-08-10 Thread LEVAI Daniel

Hi!

Here is the problem:

passdb:
daniell:*::user=daniell2

userdb:
daniell2::uid:gid:gecos:home::

dovecot.conf:
plugin {
  expire = SA.* 1
  # (There are SA.HAM and SA.SPAM directories)
}

When copying a message to eg. the SA.HAM directory, then dovecot inserts this 
into my expires table:

dovecot=# select * from expires ;
  username   | mailbox | expire_stamp
-+-+--
 daniell | SA.HAM  |   1249976454

 ^^^ wrong username

This causes an error when running expire-tool (after changing expire_stamp):
# /usr/local/sbin/dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-
tool --test
Info: User lookup failed: daniell
Info: daniell/SA.HAM: no messages left


If I change the username field in the expires table... :

# UPDATE expires SET username = 'daniell2';
UPDATE 1

... expire-tool is fine:

# /usr/local/sbin/dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-
tool --test
Info: daniell2/SA.HAM: timestamp 1249880093 (Mon Aug 10 06:54:53 2009) - 
1249976454 (Tue Aug 11 09:40:54 2009)


Daniel

-- 
LÉVAI Dániel
PGP key ID = 0x4AC0A4B1
Key fingerprint = D037 03B9 C12D D338 4412  2D83 1373 917A 4AC0 A4B1

Re: [Dovecot] Released Sieve v0.1.11 and ManageSieve v0.11.8 for Dovecot v1.2.3

2009-08-10 Thread Stephan Bosch


Michal Hlavinka wrote:

Hello Dovecot users,


Hi,



Have fun testing the new releases and don't hesitate to notify me when
there are problems.


build process for Sieve fails when --with-unfinished-features option is set:
...
make[2]: Entering directory 
`/home/mihl/myroot/job/cvsf/dovecot/devel/dovecot-1.2.3/dovecot-1.2-

sieve-0.1.11'
make[2]: *** No rule to make target `doc/man/sieve-filter.1', needed by `all-
am'.  Stop.


Fixed:

http://hg.rename-it.nl/dovecot-1.2-sieve/rev/03cb0e6d4a35

Regards,

Stephan

Re: [Dovecot] Listing shared mailboxes with a domainpart

2009-08-10 Thread Mathias Tausig

Hy!

Am Freitag, den 07.08.2009, 14:13 -0400 schrieb Timo Sirainen:
 On Fri, 2009-08-07 at 13:29 +0200, Mathias Tausig wrote:
  I am currently configuring a new mailserver using postfix and dovecot
  1.2.1. The filesystem strucutre in my spool directory is
  user1/
  user2/
  domain/info/
  domain/office/
  
  I configured a shared namespace:
  
  namespace shared {
  separator = /
  prefix = shared/%%d/%%n/
  location = maildir:/var/spool/vmaildir/%%d/%%n/
 
 I don't think you should use a shared namespace for this. You just want
 everything in domain/ to be shared to users in that domain?

Not neccesarily everything. I want to be able to share i...@domain to
user1 and off...@domain to user2.

  Do you have multiple domains?

Yes.

  Do user1 and user2 contain @domain?

No. They can receive mails under various domains which are aggregated
into one domainless account.

 [...]
 
 If that doesn't do what you want, explain more clearly what you need.

I hope I was able to clarify my (desired) setup now.
Thanks for trying to help me.

cheers
Mathias

Re: [Dovecot] Mail not begin processed

2009-08-10 Thread André Labuschagné


Thank you for the response
postconf -n:

alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
command_directory = /usr/sbin
config_directory = /etc/postfix
daemon_directory = /usr/libexec/postfix
data_directory = /var/lib/postfix
debug_peer_level = 2
header_checks = regexp:/etc/postfix/header_checks
html_directory = no
inet_interfaces = all
local_recipient_maps = $alias_maps $virtual_mailbox_maps unix:passwd.byname
mail_owner = postfix
mailq_path = /usr/bin/mailq
manpage_directory = /usr/local/man
mydestination = localhost
mydomain = paranoidandroid.co.za
myhostname = mail.paranoidandroid.co.za
mynetworks_style = host
myorigin = $myhostname
newaliases_path = /usr/bin/newaliases
queue_directory = /var/spool/postfix
readme_directory = no
sample_directory = /etc/postfix
sendmail_path = /usr/sbin/sendmail
setgid_group = postdrop
smtpd_recipient_limit = 500
smtpd_recipient_restrictions = permit_mynetworks, 
permit_sasl_authenticated, reject_unauth_destination

smtpd_sasl_auth_enable = yes
smtpd_sasl_path = private/auth
smtpd_sasl_type = dovecot
unknown_local_recipient_reject_code = 550
virtual_alias_maps = 
proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_maps.cf

virtual_mailbox_base = /
virtual_mailbox_domains = 
proxy:mysql:/etc/postfix/sql/mysql_virtual_domains_maps.cf
virtual_mailbox_maps = 
proxy:mysql:/etc/postfix/sql/mysql_virtual_mailbox_maps.cf

virtual_transport = dovecot

master.cf:
--
pickupfifo  n   -   n   60  1   pickup
cleanup   unix  n   -   n   -   0   cleanup
qmgr  fifo  n   -   n   300 1   qmgr
#qmgr fifo  n   -   n   300 1   oqmgr
tlsmgrunix  -   -   n   1000?   1   tlsmgr
rewrite   unix  -   -   n   -   -   trivial-rewrite
bounceunix  -   -   n   -   0   bounce
defer unix  -   -   n   -   0   bounce
trace unix  -   -   n   -   0   bounce
verifyunix  -   -   n   -   1   verify
flush unix  n   -   n   1000?   0   flush
proxymap  unix  -   -   n   -   -   proxymap
proxywrite unix -   -   n   -   1   proxymap
smtp  unix  -   -   n   -   -   smtp
relay unix  -   -   n   -   -   smtp
   -o smtp_fallback_relay=
showq unix  n   -   n   -   -   showq
error unix  -   -   n   -   -   error
retry unix  -   -   n   -   -   error
discard   unix  -   -   n   -   -   discard
local unix  -   n   n   -   -   local
virtual   unix  -   n   n   -   -   virtual
lmtp  unix  -   -   n   -   -   lmtp
anvil unix  -   -   n   -   1   anvil
scacheunix  -   -   n   -   1   scache
dovecot   unix  -   n   n   -   -   pipe
flags=DRhu user=vmail:vmail argv=/usr/lib/dovecot/deliver -d 
${recipient}


Many thanx

Timo Sirainen wrote:

On Sat, 2009-08-08 at 14:57 +0200, André Labuschagné wrote:
  
Aug  8 14:55:02 li73-31 postfix/qmgr[20163]: warning: connect to 
transport private/dovecot: Connection refused



What does master.cf contain? Or postconf -n? This is anyway Postfix
configuration problem, nothing really to do with Dovecot (your transport
name just happens to be dovecot).

Re: [Dovecot] GSSAPI Authentication in v1.2.1

2009-08-10 Thread Angel Marin


Phillip Macey wrote:


In the release notes for v1.2.2, Timo said:

Found and fixes several v1.2-specific bugs. Hopefully it's now stable
for most people's usage.

* GSSAPI: More changes to authentication. Hopefully good now.
  

What were the GSSAPI changes? I am having problems with _some_ of my
users using GSSAPI auth. I am using version 1.2.1. The client 
(thunderbird) reports that the server does not support 'secure 
authentication'. When I switch on auth_debug in dovecot, I see errors 
such as these in the logs:


Aug  3 16:45:57 fury dovecot: auth(default): client in: AUTH1
GSSAPI  service=imaplip=10.1.0.20 rip=10.8.5.72   lport=143
rport=4027
Aug  3 16:45:57 fury dovecot: auth(default): gssapi(?,10.8.5.72): Using
all keytab entries
Aug  3 16:45:57 fury dovecot: auth(default): client out: CONT   1
Aug  3 16:45:57 fury dovecot: imap-login: Disconnected: Input buffer
full (auth failed, 1 attempts): method=GSSAPI, rip=10.8.5.72, lip=10.1.0.20


Other users work perfectly (eg. all of the user accounts I tested
against). Would this have been a bug that was fixed in 1.2.2 or is it
something else? If it is most likely something else, I will post
`dovecot -n`.


Same here (1.2.3), it's been working fine adding all possible principals 
to the keytab and setting:


auth_gssapi_hostname = $ALL

There are all sorts of resolvers out there that seem to mess with 
principal name selection on the clients all the time. Weird thing is 
this particular one didn't happen with 1.1.x


--
Angel Marin
http://anmar.eu.org/

Re: [Dovecot] sieve vacation response

2009-08-10 Thread Steffen Kaiser


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, 7 Aug 2009, Timo Sirainen wrote:


On Fri, 2009-08-07 at 20:26 +0200, Jure Pečar wrote:

On Fri, 07 Aug 2009 13:57:57 -0400
Timo Sirainen t...@iki.fi wrote:


Currently, you need to add all allowed aliases to the :addresses
argument of the vacation command. My TODO list contains a new feature
that lets you extract additional valid aliases directly from a
dictionary (e.g. an SQL database). It is not at the top of my TODO list
yet, but since you are not the only one needing this, I'll give it some
more priority.


I don't think the above really needs a dict? Rather maybe there's a way
to have the script check the original unexpanded address. Is it stored
in some specific header, or how would Dovecot/Sieve know about it?


I agree - for example, we have X-Original-To. I'll suggest our team to
match against that header.


What about Delivered-To?


Not all MTAs add this header, e.g. stock sendmail. In case of a stock 
sendmail installation there is _no_ evidence of the RCPT TOs at all, if 
there is not exactly one recipient.


I would re-raise my suggestion to have:

localPart -or- localp...@*

matches any domain or - if I just read it, I prefer this - an 
admin-defined list of domains.


This would at least won't require a dict and will fail, if one hosts 
at least two distinct domains and a mail is sent to


localp...@example.com   explicitly, but
localp...@example.net   implicitly (same local part, domain clash).

Moreover, locally I have users, who do selectivly pick particular 
(recipient) domains, which to respond to, whereas others want that it 
just works. To trigger to fetch aliases from the dict should be 
controllable by each user, e.g. an empty :addresses list or a * in the 
list pulls the default from there or something like that.


Regards,

- -- 
Steffen Kaiser

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iQEVAwUBSn/f0nWSIuGy1ktrAQJYxwf/eMrxbmKcxbAUphVjzMh7Nit6GuTEi2+W
3zdX3cOIxl8IZrSZWD+cxlS27AYrbwKBy2g5nL6v6fuwO+a24mfmgYbzzsPJxpvl
zexldhqiEzlqtikuEUcMv0FBMqI9DJIIWTueENsN9PH0/GtfVk0gY0erbi2MW7I7
mwD9xbMvN2wnkG4Fe2bBcLBaneP0E2QJBZ3sniDfAIkrjdjrnmJbkWLRIOX3zleV
WuXd343vmQ8JRYPriSpLqdBhmBCLJA/lyMGLJI3VrzFDxR/pGhCROoaRNydxEzmH
p+tLTdiDHuFc3bmqI/iedTOicSUjM+PuHxIXMI8RhgDaioGaEKapiw==
=8Ftl
-END PGP SIGNATURE-

[Dovecot] getmail and Dovecot LDA deliver

2009-08-10 Thread spacejam


Hello,

my first post in this list. Hope it's the right place.:-)

I'm having a problem running getmail together with Dovecot LDA for virtual
users. To achive this I let getmail run under the user that owns the virtual
email accounts-root. The problem is that getmail is running under the user
vmail and therefore the emails received will be put into vmail's mailbox.
But the emails getmail collected are actually for a virtual Dovecot user
which has its maildir in a subdirectory of vmails home.
The settings for the virtual users seem to be okay: I can login on Dovecot
with virtual user account and I can send emails to Postfix for the virtual
user. Postfix correctly uses devlier with the name of the virtual user and
so the emails are going to the correct directory.
For me it seems that getmail always uses the username under which getmail is
currently running. As this must be a local user, getmails always announces
this local user to deliver and deliver therefore puts the emails into the
wrong account.
My question is: How do I let deliver know that it should use a virtual user?
I tried with the -d agrument in my getmail rc File, but deliver never
accepts the parameter -d (always says unknown parameter -d). I tried as well
to let getmail or deliver to be run as root, but then the emails will be
delivered to roots home, which is not the goal too...
Does anyone know a way how I can set getmail to handle emails for a virtual
account properly?

Any hint is appreciated as it already costed me hours of try-and-error

Regards

tobi 
-- 
View this message in context: 
http://www.nabble.com/getmail-and-Dovecot-LDA-deliver-tp24896318p24896318.html
Sent from the Dovecot mailing list archive at Nabble.com.

Re: [Dovecot] getmail and Dovecot LDA deliver

2009-08-10 Thread Timo Sirainen


On Aug 10, 2009, at 4:50 AM, spacejam wrote:

My question is: How do I let deliver know that it should use a  
virtual user?

I tried with the -d agrument in my getmail rc File, but deliver never
accepts the parameter -d (always says unknown parameter -d).


Either you're using some really ancient deliver version or the error  
message comes from getmail or something else besides deliver. So, what  
Dovecot version do you use? And also copypaste the exact error  
message (and maybe other messages too) that you get. And the getmailrc  
could help too.

Re: [Dovecot] getmail and Dovecot LDA deliver

2009-08-10 Thread spacejam



Timo Sirainen wrote:
 
 On Aug 10, 2009, at 4:50 AM, spacejam wrote:
 
 My question is: How do I let deliver know that it should use a  
 virtual user?
 I tried with the -d agrument in my getmail rc File, but deliver never
 accepts the parameter -d (always says unknown parameter -d).
 
 Either you're using some really ancient deliver version or the error  
 message comes from getmail or something else besides deliver. So, what  
 Dovecot version do you use? And also copypaste the exact error  
 message (and maybe other messages too) that you get. And the getmailrc  
 could help too.
 
 
 
I compiled deliver from Dovecot-1.0.15 The -d parameter is accepted by
deliver if Postfix invokes the mailbox_command to deliver emails to
virtual accounts. The error message from deliver is something like deliver
unknown argument -d username (I will check the exact message this evening
after work). As well I will post the content of the destination section from
my rc file which tries so invoke deliver for mail delivery to virtual
account.
I'm pretty sure that the error message comes from deliver as the program
name (deliver) is mentioned in the logfiles with the error message

-- 
View this message in context: 
http://www.nabble.com/getmail-and-Dovecot-LDA-deliver-tp24896318p24896701.html
Sent from the Dovecot mailing list archive at Nabble.com.

Re: [Dovecot] Mail archive

2009-08-10 Thread Robert Schetterer

ferna...@dfcom.com.br schrieb:
 Hi,
 
 I´m using dovecot at our storages, accounts is distributed among many
 storages (not entire domain), all of them with compression (when message 
 30Kb), nightly crontab script.
 
 Even though compression and many storages, we always have problems with
 disk space and need to migrate accounts.
 
 Have you ever implemented any archive solution working with dovecot ?
 
 Regards,
 Fernando
 
you might give more info what kind of archive you exactly mean

meanwhile study

http://wiki.dovecot.org/HowTo/ReadOnlyArchive
http://wiki.dovecot.org/Plugins/Zlib

http://wiki.dovecot.org/Plugins/Expire
Alternative dbox directory expiration

-- 
Best Regards

MfG Robert Schetterer

Germany/Munich/Bavaria

Re: [Dovecot] Mail archive

2009-08-10 Thread fernando

I would like 'some process' to store old mails at a cheap storage.

I know how to do it with symlinks, but I don´t know if it is the best
option. So, I´m asking if dovecot improves it somehow.

Fernando


fernando at dfcom.com.br schrieb:
 Hi,

 I´m using dovecot at our storages, accounts is distributed among many
 storages (not entire domain), all of them with compression (when message 
 30Kb), nightly crontab script.

 Even though compression and many storages, we always have problems with
 disk space and need to migrate accounts.

 Have you ever implemented any archive solution working with dovecot ?

 Regards,
 Fernando

you might give more info what kind of archive you exactly mean

meanwhile study

http://wiki.dovecot.org/HowTo/ReadOnlyArchive
http://wiki.dovecot.org/Plugins/Zlib

http://wiki.dovecot.org/Plugins/Expire
Alternative dbox directory expiration

-- 
Best Regards

MfG Robert Schetterer

Germany/Munich/Bavaria

Re: [Dovecot] Mail archive

2009-08-10 Thread Robert Schetterer

ferna...@dfcom.com.br schrieb:
 I would like 'some process' to store old mails at a cheap storage.
 
 I know how to do it with symlinks, but I don´t know if it is the best
 option. So, I´m asking if dovecot improves it somehow.

have you read ?
http://wiki.dovecot.org/Plugins/Expire
Alternative dbox directory expiration

 
 Fernando
 
 
 fernando at dfcom.com.br schrieb:
 Hi,

 I´m using dovecot at our storages, accounts is distributed among many
 storages (not entire domain), all of them with compression (when message 
 30Kb), nightly crontab script.

 Even though compression and many storages, we always have problems with
 disk space and need to migrate accounts.

 Have you ever implemented any archive solution working with dovecot ?

 Regards,
 Fernando

 you might give more info what kind of archive you exactly mean
 
 meanwhile study
 
 http://wiki.dovecot.org/HowTo/ReadOnlyArchive
 http://wiki.dovecot.org/Plugins/Zlib
 
 http://wiki.dovecot.org/Plugins/Expire
 Alternative dbox directory expiration
 


-- 
Best Regards

MfG Robert Schetterer

Germany/Munich/Bavaria

Re: [Dovecot] expire plugin no delete 1.2.1 / 1.2.2 / 1.2.3

2009-08-10 Thread Robert Schetterer

Robert Schetterer schrieb:
 Timo Sirainen schrieb:
 On Tue, 2009-08-04 at 10:22 +0200, Robert Schetterer wrote:
 Info: maildir:
 data=/usr/local/virtual//root/:CONTROL=/usr/local/virtual//root/:INDEX=/usr/local/virtual//root/:INBOX=/usr/local/virtual//root/
 Oh, right, this is the problem. You can't use %variables in
 mail_location setting. They get expanded too early. Since you're
 returning home anyway, use:

 mail_location = maildir:~/

 HI Timo,
 ok i try this and report
 

Hi, Timo
sorry to say
setting
mail_location = maildir:~/
does not change anything
mail is still not deleted, latest test were with 1.2.3

-- 
Best Regards

MfG Robert Schetterer

Germany/Munich/Bavaria

Re: [Dovecot] expire plugin no delete 1.2.1 / 1.2.2 / 1.2.3

2009-08-10 Thread Timo Sirainen


On Aug 10, 2009, at 11:17 AM, Robert Schetterer wrote:


Info: maildir:
data=/usr/local/virtual//root/:CONTROL=/usr/local/virtual// 
root/:INDEX=/usr/local/virtual//root/:INBOX=/usr/local/virtual// 
root/

..

setting
mail_location = maildir:~/
does not change anything
mail is still not deleted, latest test were with 1.2.3


What does it log now?

Re: [Dovecot] rename() non-atomic on HFS? (was: Dovecot-1.1.15 panics)

2009-08-10 Thread Timo Sirainen


On Aug 10, 2009, at 8:59 AM, Edgar Fuß wrote:


[...] mv foo.tmp foo [...]


[...]


So, apparently HFS+'s rename() isn't really atomic after all..
Are you sure OS X's mv(1) simply calls rename(2)? Maybe some magic  
in mv(1) for ._xxx resource forks or directory hardlinks?


I also wrote a C program that used rename() to verify it. Anyway, I  
heard it was also verified by Apple's HFS+ people.

Re: [Dovecot] getmail and Dovecot LDA deliver

2009-08-10 Thread spacejam



Robert Schetterer wrote:
 
 just as an idea
 it may work using postfix sendmail
 
 [destination]
 
 type = MDA_external
 
 path = /path/to/sendmail ( parameters )
 
 
That was the idea. First I tried to use getmail_fetch which allows to
specify a virtual username on the command line. It received the emails and
put them into the virtual users Maildir. But with getmail_fetch I could not
see to integrate the email received into Spamassassins scannig process.
So the idea with sendmail was just the one which works as wished. So my rc
File (dest part) looks like that

[destination]
type = MDA_external
path = /usr/syno/mailstation/sbin/sendmail
arguments = (vu...@virtual-domain.tld,)

I know that I should update the dovecot as well but my system is a NAS
system. And as I use this system for my email accounts I don't want to risk
to update the dovecot. But next week I will receive a second NAS server
which I will use for backups. But before I will try to install an up-to-date
Dovecot-Version and see if everything works fine with the firmware from the
manufactor.

Best regards

tobi


-- 
View this message in context: 
http://www.nabble.com/getmail-and-Dovecot-LDA-deliver-tp24896318p24903371.html
Sent from the Dovecot mailing list archive at Nabble.com.

[Dovecot] v2.0 configuration parsing

2009-08-10 Thread Timo Sirainen

I'm trying to figure out how exactly v2.0 should be parsing
configuration files. The most annoying part is if it should always just
use whatever comes first in config or try some kind of a use most
specific rule. The most specific kind of makes more sense initially,
but then you start wondering how to handle e.g.:

1) User logs in to imap from 192.168.0.1. What is foo's value?

protocol imap {
  remote_ip 192.168.0.0/16 {
foo = foo
  }
}
remote_ip 192.168.0.0/24 {
  foo = bar
}

2) User logs in from 192.168.0.1 to 10.1.2.3. What is foo's value?

local_ip 192.168.0.1 {
  remote_ip 10.1.2.0/24 {
foo = foo
  }
}
remote_ip 10.1.2.3 {
  local_ip 192.168.0.0/24 {
foo = bar
  }
}

Any thoughts?


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

59 matches

Mail list logo