Well, before even thinking about %d in mail_location, answer these first: 1. Where will Dovecot find the domain that should be used? From the IP address that the client connects to? Your dovecot -n output showed that it listened in only one IP. It's not possible to know where the client connected to from anything else except the IP.
2. Where are the users listed for different domains? Your dovecot -n output showed only a single dovecot.pwd file. Are you going to use multiple dovecot.pwd files? On Mon, 2008-12-15 at 11:37 +0100, Manuel Schmidt wrote: > I do have more than one domain. So "hardcoding" the domain somewhere > will fail someday. Or i would have to make the username unique across > domains? Which would not be a problem right now. But i'd rather not to. > > And Choosing between using the domain name with login, and hardcoding > the domain in file system structure i would choose using it in the login ... > > Cheers > Manuel > > Timo Sirainen schrieb: > > On Mon, 2008-12-15 at 11:28 +0100, Manuel Schmidt wrote: > > > >> If I connect to the server using my username as in the text file i can > >> not access my Maildirs as %d gets not replaced. If i user > >> usern...@domain.com the %d is correctly replaced. > >> > > > > Do you have more than one domain? How about just forcing the username to > > the domain? Like: > > > > auth_username_format = %...@domain.com > > > > (Or just not using %d at all anywhere) > > > >
signature.asc
Description: This is a digitally signed message part
