Re: [Dovecot] Multiple dovecot versions side-by-side
On May 19, 2009, at 1:05 AM, Max Ivanov wrote: I'm current maintainer of dovecot packages in ALTLinux distro and I plan to make possible to install multiple dovecot versions side-by-side (1.0, 1.1, 1.2) to make upgrade process easier and more robust. So you mean actually running both at the same time? The most important part is to have different base_dir for each Dovecot installation. Is there any consequences of doing that? I worry about locking maildirs and mboxes, does dovecot handle it correctly if another dovecot process tries to work on same mail location? Yes. Works just fine. I even ran stress testing v1.0 and v1.1 at the same time modifying the same mailbox. Although that was around v1.1.0 release, hopefully it hasn't broken since. :) There is one minor incompatibility with v1.0 and v1.1 index files, but it has to do with handling \recent flags and shouldn't really cause any real problems. They were more or less broken in v1.0 (and most other IMAP servers) anyway.
[Dovecot] Multiple dovecot versions side-by-side
I'm current maintainer of dovecot packages in ALTLinux distro and I plan to make possible to install multiple dovecot versions side-by-side (1.0, 1.1, 1.2) to make upgrade process easier and more robust. Is there any consequences of doing that? I worry about locking maildirs and mboxes, does dovecot handle it correctly if another dovecot process tries to work on same mail location?
[Dovecot] imap cann't read the mail that foxmail send
Hi everyone: I use dovecot only as the imap server, For smtp and pop3, I use apache james. The dovecot version: 1.1.14 And the configuration is : protocols: imap ssl_disable: yes login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login mail_location: mbox:/usr/local/edupass/mail/repo/%u:INBOX=/usr/local/edupass/mail/%u auth default: passdb: driver: sql args: /etc/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot-sql.conf I have no porblems to login. When I use "telent host 25" to send a email, dovecot read it no problems. But when I use outlook and foxmail to send a email, dovecot cann't read the email data. I compared the data that using the two way to send, and found the reason: use outlook and foxmail: at the beginning of the eamil data is "From zxjteacher_SP_LZU "; and if I telnet host 25 to send the mail: at the beginning of the eamil data is "From ", so I delete "zxjteacher_SP_LZU", dovecot read it out. "zxjteacher_SP_LZU" is because that outlook and foxmail need an account name to represent the eamil address. So, anyone ever confront with this situation? Any helps appreciate. Thx.
Re: [Dovecot] 1.2.beta1: expire-tool and 'mail_location' setting
Timo Sirainen wrote: > On Sun, 2009-02-22 at 12:49 +0100, e-frog wrote: >> Trying 1.2.beta1 with expire plugin currently: >> When I set mail_location = maildir:~/.maildir the expire plugin doesn't >> delete messages. > > Should be fixed in hg now. > >> My guess is that mail_location is not respected by expire-tool for some >> reason and in second >> case mailbox auto-detection makes it working? > > Yes. > Thanks Timo! It works now as long as there is no namespace for the virtual plugin defined: f...@test:/etc/dovecot$ sudo /usr/sbin/dovecot --exec-mail ext /usr/lib/dovecot/expire-tool --test Info: auth input: system_groups_user=foo Info: auth input: uid=1000 Info: auth input: gid=1000 Info: auth input: home=/home/foo Info: Namespace: type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes Info: maildir: data=~/.maildir Info: maildir++: root=/home/foo/.maildir, index=, control=, inbox=/home/foo/.maildir Info: foo/Trash: seq=1 uid=1: Expunge Info: foo/Trash: seq=2 uid=2: Expunge --snip -- Info: foo/Trash: seq=18 uid=18: Expunge Info: foo/Trash: seq=19 uid=19: Expunge Info: foo/Trash: timestamp 1242499040 -> 1242759162 Having the virtual namespace I see the following (dovecot -n below): f...@test:/etc/dovecot$ sudo /usr/sbin/dovecot --exec-mail ext /usr/lib/dovecot/expire-tool --test Info: auth input: system_groups_user=foo Info: auth input: uid=1000 Info: auth input: gid=1000 Info: auth input: home=/home/foo Info: Namespace: type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes Info: maildir: data=~/.maildir Info: maildir++: root=/home/foo/.maildir, index=, control=, inbox=/home/foo/.maildir Info: Namespace: type=private, prefix=virtual/, sep=/, inbox=no, hidden=no, list=children, subscriptions=no Error: Namespace 'virtual/': Unknown mail storage driver virtual Info: User lookup failed: foo - # 1.2.rc4: /etc/dovecot/dovecot.conf # OS: Linux 2.6.27-14-server i686 Ubuntu 8.10 protocols: imap imaps managesieve disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login verbose_proctitle: yes mail_location: maildir:~/.maildir mail_debug: yes mail_drop_priv_before_exec: yes mail_executable(default): /usr/lib/dovecot/rawlog /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/rawlog /usr/lib/dovecot/imap mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugins(default): expire virtual mail_plugins(imap): expire virtual mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: private separator: / prefix: virtual/ location: virtual:~/.maildir/virtual list: children auth default: passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 plugin: expire: Trash 1 expire_dict: proxy::expire sieve: ~/.dovecot.sieve sieve_dir: ~/sieve dict: expire: mysql:/etc/dovecot/dovecot-dict-sql.conf
Re: [Dovecot] LDA and postfix with recipient delimiter:documentation
mr.maX wrote:
>> ${domain} is a somewhat recent addition to Postfix. I guess the docs
>> could say to use ${domain} instead of ${nexthop} if Postfix is newer
>> than X (should look up what version added that).
>
> ${domain} parameter has been added starting with Postfix 2.5, which
> means that people using "enterprise" linux distros that usually ship
> with old versions of software won't be able to use it.
>
> Anyway, I'm guessing that the real problem here lies in the fact that
> John used "mailbox_transport = dovecot" to instruct Postfix how to
> deliver e-mails, instead of using virtual_transport Postfix parameter
> as instructed in the Dovecot's wiki. Parameter mailbox_transport is
> used to set optional message delivery transport that Postfix's *local*
> delivery agent should use for delivery and since it's actually a local
> delivery, nexthop is by default set to $myhostname (using
> local_transport parameter), instead of the actual virtual domain.
Hi Marko
thanks for that clarification. That clears up why next_hop was not
evaluating to the domain. I don't have a mixture of local and virtual
mailboxes so for me using postfix local delivery via mailbox transport
(what I used to do with cyrus and with dbmail) was fine too and also
evaluates the local aliases file, though I could rewrite that to
virtual_alias_maps...
However, it means the wiki documentation doesn't need changing: the
next_hop parameter is consistent with the rest of the instructions. It's
my setup that was different. If someone choses to do it the way I have
done, they can see the solution in the list archives.
thanks everyone.
John
Re: [Dovecot] dovecot 2.0 (revision 9271:d467712aee77) compile problems on AIX 5.3
On May 18, 2009, at 2:02 PM, Timo Sirainen wrote: On Mon, 2009-05-18 at 13:57 -0400, Jonathan Siegle wrote: Yes fixed. Is it to "early" to be reporting stuff like this? No, it's not too early. Better early than late :) I now have this error(rev 9321:4c4b95def1fa): "ssl-proxy.c", line 12.5: 1506-343 (S) Redeclaration of ssl_proxy_new differs from previous declaration on line 17 of "ssl-proxy.h". Fixed: http://hg.dovecot.org/dovecot-2.0/rev/9c6597ba9e3e Thanks. No more compilation errors to report. smime.p7s Description: S/MIME cryptographic signature
Re: [Dovecot] How to manage Seen flags via sieve?
On Mon, May 18, 2009 at 6:30 PM, Max Ivanov wrote: > I use public namespace for group mailboxes. If someone sends email > from this mailbox , MTA detects it and delivers copy of that message > to mailbox/Sent folder, to keep history of all messages available for > every group member. I'd like to set Seen flag on all messages that > dovecots deliver puts into "Sent" folder. Is it posible somehow? > addflag "\\Seen" http://wiki.fastmail.fm/index.php?title=SieveFAQ http://www.fastmail.fm/docs/sieve/draft-melnikov-sieve-imapflags-04.txt Chris
Re: [Dovecot] dovecot 2.0 (revision 9271:d467712aee77) compile problems on AIX 5.3
On Mon, 2009-05-18 at 13:57 -0400, Jonathan Siegle wrote: > Yes fixed. Is it to "early" to be reporting stuff like this? No, it's not too early. Better early than late :) > I now have this error(rev 9321:4c4b95def1fa): > > "ssl-proxy.c", line 12.5: 1506-343 (S) Redeclaration of ssl_proxy_new > differs from previous declaration on line 17 of "ssl-proxy.h". Fixed: http://hg.dovecot.org/dovecot-2.0/rev/9c6597ba9e3e signature.asc Description: This is a digitally signed message part
Re: [Dovecot] dovecot 2.0 (revision 9271:d467712aee77) compile problems on AIX 5.3
On May 17, 2009, at 2:42 PM, Timo Sirainen wrote: On Wed, 2009-05-13 at 15:04 -0400, Jonathan Siegle wrote: Having some problems compiling on AIX 5.3 with IBM vac version 8. Programs that I had problems building: test-mail test-imap test-index Should be fixed in hg now? Yes fixed. Is it to "early" to be reporting stuff like this? I now have this error(rev 9321:4c4b95def1fa): "ssl-proxy.c", line 12.5: 1506-343 (S) Redeclaration of ssl_proxy_new differs from previous declaration on line 17 of "ssl-proxy.h". "ssl-proxy.c", line 12.5: 1506-376 (I) Redeclaration of ssl_proxy_new has a different number of fixed parameters than the previous declaration. "ssl-proxy.c", line 12.5: 1506-377 (I) The type "struct ssl_proxy**" of parameter 3 differs from the previous type "const struct login_settings*". "ssl-proxy.c", line 19.5: 1506-343 (S) Redeclaration of ssl_proxy_client_new differs from previous declaration on line 19 of "ssl-proxy.h". "ssl-proxy.c", line 19.5: 1506-376 (I) Redeclaration of ssl_proxy_client_new has a different number of fixed parameters than the previous declaration. "ssl-proxy.c", line 19.5: 1506-377 (I) The type "int(*)(void*)" of parameter 3 differs from the previous type "const struct login_settings*". gmake[3]: *** [ssl-proxy.lo] Error 1 gmake[3]: Leaving directory `/usr/sadmin/src/imapservers/dovecothg/ dovecot-2.0psu/src/login-common' thanks, Jonathan smime.p7s Description: S/MIME cryptographic signature
Re: [Dovecot] 1.1.13 squat core dump
So far the crashes continue, but I haven't seen anything in particular that sets it off. I'll trying coming up with a way of reproducing it and get back to you if I can. In the meantime, I'm upgrading to the latest version to see if anything changes. Timo Sirainen wrote: On Thu, 2009-04-23 at 11:51 -0400, David Halik wrote: I did some more digging and here's the actual error that it fails with: Apr 23 09:28:21 batman.rutgers.edu IMAP(kmech): : [ID 107833 mail.crit] Panic: file squat-trie.c: line 441: assertion failed: (!node->have_sequential) Are you still getting these? If you can get it into a state where you can reproduce the crash every time when doing something, I'd like to get all the index files from that mailbox (except dovecot.index.cache isn't necessary and it contains parts of message headers). If I can't reproduce it I don't think I'm going to spend time anytime soon on figuring out why it's crashing. -- David Halik System Administrator OIT-CSS Rutgers University dha...@jla.rutgers.edu
Re: [Dovecot] FTS Plugin design
On Mon, 2009-05-18 at 17:35 +0100, Rui Carneiro wrote: > I think binary data is being corrupted anywhere before > fts_backend_build_more() and I don't have any idea where. All the data comes from lib-mail/message-decoder.c. Hmm. Looks like it tries to force giving only valid UTF-8 output. I guess it should have some flag or something that makes it do that only for text/* parts, not for binary parts. OK, implemented, see if it works with this and using the flag: http://hg.dovecot.org/dovecot-1.2/rev/44548a7fb10d signature.asc Description: This is a digitally signed message part
Re: [Dovecot] ext3/ext4 performance issue
on 5-18-2009 8:46 AM Matthijs Kooijman spake the following: > Hi Scott, > >> One could always run the mailstore on LVM and then you could snapshot the >> mount and then fsck it while still technically in use. It would probably slow >> down the filesystem, but it is still live. > Uhm, and then you have a nice and fsck'd snapshot, but your live filesystem > will still be untouched? Or do you propose replacing the mailstore with a > (readonly?) versioned mounted from the lvm snapshot? I'm not aware of anything > that can swap filesystems like this online (ie, with files open) and that > would also mean that while fsck'ing, you can only read mail, not receive, move > or delete mail? > > Gr. > > Matthijs I re-read the howto on using fsck on LVM snapshots, and it is only good if the FS passes. Then you can update the fsck details in the filesystem. If the FS doesn't pass, you would still need to schedule a fsck when inactive. My bad. signature.asc Description: OpenPGP digital signature
Re: [Dovecot] ext3/ext4 performance issue
Matthijs Kooijman wrote: > Hi Scott, > >> One could always run the mailstore on LVM and then you could snapshot the >> mount and then fsck it while still technically in use. It would probably slow >> down the filesystem, but it is still live. > Uhm, and then you have a nice and fsck'd snapshot, but your live filesystem > will still be untouched? Or do you propose replacing the mailstore with a > (readonly?) versioned mounted from the lvm snapshot? I'm not aware of anything > that can swap filesystems like this online (ie, with files open) and that > would also mean that while fsck'ing, you can only read mail, not receive, move > or delete mail? > Changes made to a snapshot will never been seen by the fs it was snapshotted from and vice-versa. It uses copy on write which will get progressively slower as the snapshot and the origional diverge until you end up with a performance disaster. http://www.nikhef.nl/~dennisvd/lvmcrap.html ~Seth
Re: [Dovecot] FTS Plugin design
Citando Timo Sirainen : > Nope. If you still see corruption, try with some simple test mails and > see if it's adding garbage, losing contents or adding more content. I tried something more advanced than that. I hexdumped my pdf test file and on the first line I get: 25 50 44 46 2d 31 2e 33 0a 25 e2 e3 cf d3 0a 31 Where "e2 e3 cf d3" is binary data. When I do the same for my copied file I get: 25 50 44 46 2d 31 2e 33 0a 25 ef bf bd 0a 31 20 It is weird but the binary data changed. Further, I print to logs the 11 character from the first block.data just before fts_backend_build_more() and the value is EF (the correct one would be E2). I think binary data is being corrupted anywhere before fts_backend_build_more() and I don't have any idea where. Any help would be appreciated. Thank you, Rui Carneiro -- Portugalmail, Comunicações S.A. www.portugalmail.net
[Dovecot] How to manage Seen flags via sieve?
I use public namespace for group mailboxes. If someone sends email from this mailbox , MTA detects it and delivers copy of that message to mailbox/Sent folder, to keep history of all messages available for every group member. I'd like to set Seen flag on all messages that dovecots deliver puts into "Sent" folder. Is it posible somehow?
Re: [Dovecot] LDA and postfix with recipient delimiter:documentation
${domain} is a somewhat recent addition to Postfix. I guess the docs
could say to use ${domain} instead of ${nexthop} if Postfix is newer than
X (should look up what version added that).
${domain} parameter has been added starting with Postfix 2.5, which means
that people using "enterprise" linux distros that usually ship with old
versions of software won't be able to use it.
Anyway, I'm guessing that the real problem here lies in the fact that John
used "mailbox_transport = dovecot" to instruct Postfix how to deliver
e-mails, instead of using virtual_transport Postfix parameter as instructed
in the Dovecot's wiki. Parameter mailbox_transport is used to set optional
message delivery transport that Postfix's *local* delivery agent should use
for delivery and since it's actually a local delivery, nexthop is by default
set to $myhostname (using local_transport parameter), instead of the actual
virtual domain.
--
Best Regards,
Marko Njezic - mr.maX @ MAX Interactive corp.
Personal: http://www.markonjezic.com/
MAX's Empire: http://www.maxempire.com/
MAX's HTML Beauty++ 2004: http://www.htmlbeauty.com/
Re: [Dovecot] ext3/ext4 performance issue
Hi Scott, > One could always run the mailstore on LVM and then you could snapshot the > mount and then fsck it while still technically in use. It would probably slow > down the filesystem, but it is still live. Uhm, and then you have a nice and fsck'd snapshot, but your live filesystem will still be untouched? Or do you propose replacing the mailstore with a (readonly?) versioned mounted from the lvm snapshot? I'm not aware of anything that can swap filesystems like this online (ie, with files open) and that would also mean that while fsck'ing, you can only read mail, not receive, move or delete mail? Gr. Matthijs signature.asc Description: Digital signature
Re: [Dovecot] LDA and postfix with recipient delimiter: documentation
On May 18, 2009, at 3:56 AM, John Fawcett wrote:
Can anyone see a reason for not using always ${us...@${domain}
instead of ${us...@${nexthop}?
${domain} is a somewhat recent addition to Postfix. I guess the docs
could say to use ${domain} instead of ${nexthop} if Postfix is newer
than X (should look up what version added that).
Re: [Dovecot] FTS Plugin design
On May 18, 2009, at 6:42 AM, Rui Carneiro wrote: I am having some troubles sending all data to a file. When I finish to send all data to a file, I tried to open it and the file is corrupted. The first think I noticed is that all chars are capitalized what destroy all the file format. Where are the chars capitalized? Hmm. I'll see about getting it fixed in a better way, but for now you could just change: decoder = message_decoder_init(TRUE); to decoder = message_decoder_init(FALSE); I'm thinking about making message_decoder uppercase only text/* body parts. Any other idea why files are getting corrupted? Nope. If you still see corruption, try with some simple test mails and see if it's adding garbage, losing contents or adding more content.
Re: [Dovecot] LDA and postfix with recipient delimiter: documentation
john...@erba.tv schrieb:
>> Hi John,
>> no i didnt wrote that, i only have u...@domain.ext
>> layout in use currently in my test servers
>>
>> --
>> Best Regards
>>
>> MfG Robert Schetterer
>>
>> Germany/Munich/Bavaria
>>
> Hi Robert
> I probably didn't make it clear. The problem with the
> published syntax is that it does not work for
> receipient delimiter and delivery to mailbox, except
> as far as I can see when next_hop is the same as
> domain, which is not always the case. I think that
> the documentation should report the syntax with
> ${domain} instead of ${next_hop}, unless there's
> something I'm missing, since this should always
> work.
> thanks again
> John
>
>
>
>
>
Hi John, i cant say somthing about that, unless self testing
my mail was just for info about other setups working
but your arguments to change doku sounds plausible to me
i think Timo will clear us about it later
--
Best Regards
MfG Robert Schetterer
Germany/Munich/Bavaria
Re: [Dovecot] LDA and postfix with recipient delimiter: documentation
> Hi John,
> no i didnt wrote that, i only have u...@domain.ext
> layout in use currently in my test servers
>
> --
> Best Regards
>
> MfG Robert Schetterer
>
> Germany/Munich/Bavaria
>
Hi Robert
I probably didn't make it clear. The problem with the
published syntax is that it does not work for
receipient delimiter and delivery to mailbox, except
as far as I can see when next_hop is the same as
domain, which is not always the case. I think that
the documentation should report the syntax with
${domain} instead of ${next_hop}, unless there's
something I'm missing, since this should always
work.
thanks again
John
Re: [Dovecot] LDA and postfix with recipient delimiter: documentation
john...@erba.tv schrieb:
>> John Fawcett schrieb:
>>> Just a comment about the documentation for postfix integration when
>>> using receipient delimiter and delivery of user+...@domain.ext to
>>> u...@domain:
>>>
>>> http://wiki.dovecot.org/LDA/Postfix
>>>
>> Hi John, just for info, in my test server i use
>>
>> dovecot_destination_recipient_limit = 1
>> virtual_transport = dovecot
>>
>> dovecot unix - n n - - pipe
>> flags=DRhu user=vmail:vmail argv=/usr/lib/dovecot/deliver -f ${sender}
>> -d ${recipient}
>>
> Hi Robert
> thanks for your reply.
> Ar you saying that this handles + addresses correctly (i.e.
> user+...@domain.ext delivered to u...@domain.ext)?
> thanks,
> John
>
Hi John,
no i didnt wrote that, i only have u...@domain.ext
layout in use currently in my test servers
--
Best Regards
MfG Robert Schetterer
Germany/Munich/Bavaria
Re: [Dovecot] migration and conversion from courier
On M 18 May, 2009, at 01:00 , Timo Sirainen wrote: On Mon, 2009-05-18 at 00:57 +0200, Giuliano Gavazzi wrote: There's only one point that escapes me, why perform the conversion when migrating (using the --convert option) given that on the system where I did not perform it the flags have been preserved (the files got their name change consistently). Does dovecot detect the presence of the courierimapkeywords/:list file and use its content? No. Seems unlikely as a grep on the source does not reveal any match. Maybe it's the MUA (Mail.app in the instance I checked) that did synchronise the flags? I guess something like that is possible. But did you check that it's also correct on the server side too and not just on client side? yes, is on the server: that's why I said that the files had the consistent name change. Well, that means that with all its faults Mail.app is not sooo bad! I checked on another system with many OutLook and Thunderbird clients and it looks like they might have lost the flags previous to the change. I could write a script to update those files consistently to the current dovecot-keywords, when required. This could be an option of the migration script, say a --fix switch that would make it look in courierimapkeywords and add the keys to dovecot-keywords when they do not exist and then update the name of the message files when required. Giuliano
Re: [Dovecot] FTS Plugin design
Hi again, I am having some troubles sending all data to a file. When I finish to send all data to a file, I tried to open it and the file is corrupted. The first think I noticed is that all chars are capitalized what destroy all the file format. Where are the chars capitalized? Any other idea why files are getting corrupted? Thank you, Rui Carneiro -- Portugalmail, Comunicações S.A. www.portugalmail.net
Re: [Dovecot] LDA and postfix with recipient delimiter: documentation
> John Fawcett schrieb:
>> Just a comment about the documentation for postfix integration when
>> using receipient delimiter and delivery of user+...@domain.ext to
>> u...@domain:
>>
>> http://wiki.dovecot.org/LDA/Postfix
>>
> Hi John, just for info, in my test server i use
>
> dovecot_destination_recipient_limit = 1
> virtual_transport = dovecot
>
> dovecot unix - n n - - pipe
> flags=DRhu user=vmail:vmail argv=/usr/lib/dovecot/deliver -f ${sender}
> -d ${recipient}
>
Hi Robert
thanks for your reply.
Ar you saying that this handles + addresses correctly (i.e.
user+...@domain.ext delivered to u...@domain.ext)?
thanks,
John
Re: [Dovecot] LDA and postfix with recipient delimiter: documentation
John Fawcett schrieb:
> Just a comment about the documentation for postfix integration when
> using receipient delimiter and delivery of user+...@domain.ext to
> u...@domain:
>
> http://wiki.dovecot.org/LDA/Postfix
>
> I had some issues to get this working, so thought I'd share my
> experience. Dovecot version 1.2.rc3. Postfix version
> postfix-2.7-20090511.
>
> I have no local (unix) mailboxes, everything is delivered to dovecot,
> so in postfix I have set mailbox_transport = dovecot.
> In this case the following syntax taken from the docs
> does not work:
>
> dovecot unix - n n - - pipe
> flags=DRhu user=vmail:vmail argv=/usr/lib/dovecot/deliver -f ${sender} -d
> ${us...@${nexthop}
>
> whereas the following does work:
>
> dovecot unix - n n - - pipe
> flags=DRhu user=vmail:mail argv=/usr/lib/dovecot/deliver -f ${sender} -d
> ${us...@${domain}
>
> I think that ${domain} is always what is wanted and only when
> ${nexthop} happens to have the same value as ${domain}
> - for example when using a transport table entry like this:
>
> /etc/postfix/transport
> domain.extdovecot:
>
> will the ${us...@${nexthop} form be deliverable.
> Can anyone see a reason for not using always ${us...@${domain}
> instead of ${us...@${nexthop}?
>
>
> John
>
>
>
>
>
>
>
>
>
>
>
>
>
Hi John, just for info, in my test server i use
dovecot_destination_recipient_limit = 1
virtual_transport = dovecot
dovecot unix - n n - - pipe
flags=DRhu user=vmail:vmail argv=/usr/lib/dovecot/deliver -f ${sender}
-d ${recipient}
without any problems with users full domain layout but without local users
and postfix 2.5.5
currently testing this ( but havent looked about unwanted sideeffects yet)
dovecot unix - n n - - pipe
flags=DRhu user=vmail:vmail argv=/usr/bin/spamc -e
/usr/lib/dovecot/deliver -f ${sender} -d ${recipient}
evantually i will use
mailbox_command = procmail -a "$EXTENSION"
vor having an archive with local users later
--
Best Regards
MfG Robert Schetterer
Germany/Munich/Bavaria
[Dovecot] LDA and postfix with recipient delimiter: documentation
Just a comment about the documentation for postfix integration when
using receipient delimiter and delivery of user+...@domain.ext to
u...@domain:
http://wiki.dovecot.org/LDA/Postfix
I had some issues to get this working, so thought I'd share my
experience. Dovecot version 1.2.rc3. Postfix version
postfix-2.7-20090511.
I have no local (unix) mailboxes, everything is delivered to dovecot,
so in postfix I have set mailbox_transport = dovecot.
In this case the following syntax taken from the docs
does not work:
dovecot unix - n n - - pipe
flags=DRhu user=vmail:vmail argv=/usr/lib/dovecot/deliver -f ${sender} -d
${us...@${nexthop}
whereas the following does work:
dovecot unix - n n - - pipe
flags=DRhu user=vmail:mail argv=/usr/lib/dovecot/deliver -f ${sender} -d
${us...@${domain}
I think that ${domain} is always what is wanted and only when
${nexthop} happens to have the same value as ${domain}
- for example when using a transport table entry like this:
/etc/postfix/transport
domain.ext dovecot:
will the ${us...@${nexthop} form be deliverable.
Can anyone see a reason for not using always ${us...@${domain}
instead of ${us...@${nexthop}?
John
Re: [Dovecot] example sql acl_shared_dict wiki
Timo Sirainen schrieb: > On Mon, 2009-05-18 at 01:40 +0200, Robert Schetterer wrote: >> could you include an example for having >> acl_shared_dict in sql ? > > See if you can get it working with these kind of settings: > http://www.dovecot.org/list/dovecot/2009-April/038922.html > Thanks Timo, i will try this and report -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria
