Re: [Dovecot] using 'socat' to relay Dovecot SASL's auth socket over TCP?
snowcrash wrote: which, iiuc (?), can bidirectionally bridge the Dovecot unix-socket to a TCP socket that Exim can talk/listen to. I've used socat extensively on a completely unrelated project in order to bridge UNIX domain sockets across machines. I assume you currently have this: exim - /some/unix/socket - dovecot-auth If you want to use socat, then make sure it is installed on both machines. You can bridge using ssh (recommended) or just plain TCP/IP. For ssh, run the following command on eximhost: socat -t 10 UNIX-LISTEN:/some/unix/socket,fork \ EXEC:ssh [EMAIL PROTECTED] STDIO UNIX:/some/unix/socket The ssh will need to be able to complete without any form of prompting (ie you need private/authorized keys setup). If you don't care about security then you can use TCP connections between the machines. On eximhost run this replacing with your chosen port number: socat -t 10 UNIX-LISTEN:/some/unix/socket,fork \ TCP4:dovecot-auth-host: On dovecot-auth-host run: socat TCP4-LISTEN:,fork \ UNIX:/some/unix/socket The -t 10 option waits for 10 seconds after one direction is closed before closing the other direction. The socat default is .5 seconds which I found problematic on higher latency links. Roger
Re: [Dovecot] lazy_expunge and emails from Inbox, doesn't list INBOX in deleted
Charles Marcus wrote: Curious... was this copy/pasted from dovecot -n output? Or was that last line misspelling of 'maildur' a typo? Just one reason why copy/pasted output of dovecot -n is preferred... It was manually retyping. I was rebuilding a new server which I did by putting a new harddisk in my workstation and then making a VMWare guest using the raw disk. I don't install any of the vmware crud in that guest since it is a pain to get rid of and disk would be the new primary disk in a physical machine anyway. Consequently I had no copy and paste capability and had to retype manually. SSH would have been one alternative, but the ssh connections hang between a host and guest on the same machine under some circumstances (and always for me). It is some tcp level issue that I didn't bother resolving. But I am happy to have successfully migrated from Gentoo qmail, maildrop, courier and sqwebmail to Ubuntu postfix, procmail, dovecot and squirrelmail. Roger
[Dovecot] lazy_expunge and emails from Inbox, doesn't list INBOX in deleted
I'm using the dovecot available on Ubuntu Feisty (1.0rc17) and am trying
to migrate from courier-imap. A really important feature for me from
courier is that expunged messages end up in Trash where they are removed
after 7 days.
I can get an approximation of this feature as described in the
documentation:
namespace private {
prefix = INBOX.
seperator = .
inbox = yes
}
namespace private {
prefix = DELETED.
seperator = .
location = maildur:~/Maildir/deleted
}
lazy_expunge = DELETED. DELETED. DELETED.
This all works fine except for messages that were deleted from the
Inbox. They do end up in the right place (~/Maildir/deleted/cur) but
that location is not listed as a subscribable folder.
Here you can see that deleted messages from my ciontope folder show up,
but not the inbox.
a LIST DELETED. *
* LIST (\HasNoChildren) . DELETED.ciontope
a OK List completed.
You can't examine the namespace itself:
a EXAMINE DELETED
a NO Unknown namespace.
a EXAMINE DELETED.
a NO Invalid mailbox name
But the folder does exist:
a EXAMINE DELETED.INBOX
* FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
* OK [PERMANENTFLAGS ()] Read-only mailbox.
* 4 EXISTS
* 0 RECENT
* OK [UIDVALIDITY 1181423860] UIDs valid
* OK [UIDNEXT 5] Predicted next UID
a OK [READ-ONLY] Select completed.
Is there any way to convince dovecot to list DELETED.INBOX so that
clients can see it an subscribe to it?
Roger
Re: [Dovecot] lazy_expunge and emails from Inbox, doesn't list INBOX in deleted
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Timo Sirainen wrote:
On Sat, 2007-06-09 at 14:23 -0700, Roger Binns wrote:
namespace private {
prefix = DELETED.
seperator = .
location = maildur:~/Maildir/deleted
inbox = no
}
Does that help?
Nope. However I have a disgusting workaround :-) In Maildir/deleted I
create .INBOX/ and within that directory I then symlink cur/new/tmp to
Maildir/deleted/{cur/new/tmp}.
Everything works fine and the correct content is shown. I am patiently
waiting for the day when courier style Trash is implemented :-)
lazy_expunge = DELETED. DELETED. DELETED.
Have you tried what happens if you try to expunge mails from
DELETED.mailbox? When I wrote the code I assumed all those namespaces
would be different.
It works fine.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGbHefmOOfHg372QQRAoFmAKCKINGfDFMUCHoCELSYv37D4iLtzgCgrfNy
lqr8lHaB8D6HCKu7e4iGFnk=
=lGUG
-END PGP SIGNATURE-
