Yes i think it is a IMAPdir but how do i undo the softlink Ideally i
would like to move the entire directory structure over to a folder named
IMAPdir minus the strange INBOX/INBOX/INBOX/

here is ls -a

v22.computerking.ca > /home/rmvg/IMAPdir/INBOX #ls -a
.                       SERVERS.Monthy          Trash
..                      SERVERS.daily           bincimap-cache
Drafts                  SERVERS.security        bincimap-uidvalidity
INBOX                   SERVERS.weekly          cur
Junk                    Save                    new
Mail Delivery System    Save.job                supervise
SERVERS                 Sent                    tmp
SERVERS.Cron            Sent Items

The reason i did the ln -s . INBOX thing is because i could not find my
messages when i first set up bincimap.  Since then i have setup bincimap
on another server without using the ln -s . INBOX and it is very
painless to setup new users.

In short i want lose the softlink and work out of a directory called
IMAPdir but do not want any of my users to lose there mails.




Henry Baragar wrote:

On Tue, 15 Jun 2004 13:38:46 -0600, RYAN vAN GINNEKEN <[EMAIL PROTECTED]> wrote:



Henry Baragar wrote:

On Tue, 15 Jun 2004 12:24:42 -0600, RYAN vAN GINNEKEN <[EMAIL PROTECTED]> wrote:

trying to use the script but keep getting this error

v22.computerking.ca > /home/rmvg #./Maildir2IMAPdir.sh Maildir IMAPdir
mv: rename . to INBOX.: Invalid argument

Note that Maildir++2IMAPdir.sh (and Maildir2IMAPdir.sh) contains this warning:

# WARNING:
#       Soft links are not always handled correctly.

If you have soft links, then you are advised to use Maildir++2IMAPdir.pl which handles soft links properly.

Thanks for the error report. May I ask to what Maildir was linked?



Not sure what you mean all my Maildir are linked. when i create a new user account i have to go into that users INBOX and do this
rm -rf INBOX
ln -s . INBOX


Why do you do this? Is it to preserve the delivery instructions of your MTA?

my INBOX seems to go on forever  as you can see

22.computerking.ca > ~/Maildir/INBOX/INBOX/INBOX $l
total 64
drwx------  5 rmvg  rmvg    512 Jun  8 23:20 Drafts
lrwxr-xr-x  1 rmvg  rmvg      1 Mar  5 04:32 INBOX -> .
drwxr-xr-x  5 rmvg  rmvg    512 Jun 12 02:08 Junk
drwx------  5 rmvg  rmvg    512 Jun 15 13:31 Mail Delivery System
drwxr-xr-x  5 rmvg  rmvg    512 Jun  8 23:23 SERVERS
drwxr-xr-x  5 rmvg  rmvg    512 Jun 12 13:00 SERVERS.Cron
drwx------  5 rmvg  rmvg    512 Jun  8 23:23 SERVERS.Monthy
drwxr-xr-x  5 rmvg  rmvg    512 Jun 12 13:00 SERVERS.daily
drwxr-xr-x  5 rmvg  rmvg    512 Jun  8 23:23 SERVERS.security
drwxr-xr-x  5 rmvg  rmvg    512 Jun 12 13:00 SERVERS.weekly
drwx------  5 rmvg  rmvg    512 Jun  8 23:22 Save
drwx------  5 rmvg  rmvg    512 Jun  8 23:22 Save.job
drwxr-xr-x  5 rmvg  rmvg    512 Jun 10 19:50 Sent
drwx------  5 rmvg  rmvg    512 Jun 10 19:50 Sent Items
drwxr-xr-x  5 rmvg  rmvg    512 Jun 15 13:31 Trash
-rw-------  1 rmvg  rmvg  17288 Jun 15 13:31 bincimap-cache
-rw-------  1 rmvg  rmvg     73 Jun 15 13:26 bincimap-uidvalidity
drwx------  2 rmvg  rmvg   8704 Jun 15 13:31 cur
drwx------  2 rmvg  rmvg    512 Jun 15 13:26 new
drwx------  2 rmvg  rmvg    512 Mar  7 00:52 supervise
drwx------  2 rmvg  rmvg    512 Jun 15 12:20 tmp
[Tue Jun 15] 01:37 PM [0]
v22.computerking.ca > ~/Maildir/INBOX/INBOX/INBOX $

This looks more like an IMAPdir than a Maildir++. What does "l -a" produce?

The proper sequence for migrating a Maildir++ depot to an IMAPdir depot is:
1. shutdown Binc and the MTA (e.g. qmail)
2. run Maildir++2IMAPdir.sh for all mail users
3. Change the delivery instructions for the MTA
4. Change the depot in bincimapd.conf
5. Start up Binc and the MTa
Note that step 3 can be skipped if Maildir++2IMAPdir.pl is used instead of Maildir++2IMAPdir.sh.


Henry :-)



Henry :-)

I have my Maildir symbolicly linked with ln -s . INBOX but get a weird INBOX loop that seems to go on forever.
Also it was too much hassle to link for every new user
set up a new server and set postfix to deliver to IMAPdir/INBOX/ and do not have to create a symlink for every user on this new machine












Reply via email to