tisdagen den 29 juli 2003 17.38 skrev tonix (Antonio Nati): > At 29/07/03 29/07/03 -0400, Jeff Hedlund wrote: > >Alex Pleiner wrote: > >>I had problems with the following setup: > >>Two POP3 Accounts [EMAIL PROTECTED] and [EMAIL PROTECTED] and a file .qmail-foo > >> with: /home/vpopmail/domains/test.com/foo/Maildir/ > >>/home/vpopmail/domains/test.com/bar/Maildir/ > >>Worked like a charm. alias2forward.pl changed it to: > >>&[EMAIL PROTECTED] > >>&[EMAIL PROTECTED] > >>Now deliveries to [EMAIL PROTECTED] fail (looping). > >>This problem can be solved but could break existing systems. > > > >Yes, it would break existing systems that have an alias that matches an > >existing account. The new interface would not have allowed an alias of > >"foo" if an account already existed with the name "foo". I'm surprised > >that older versions allowed this. (or did you create that alias by hand?) > > I feel old version was correct to allow that, and I hope this way of > working remains.
vpopmail and qmailadmin should mimic default qmail behaviour as closely as possible. If this change was made to make spamassassin like stuff work, then I propose a workaround that does not break the previous standard. Wouldn't it be possible to make vpopmail more intelligent? Maybe also implement a plugin system and a backend auth daemon like the stuff Mr. Sam has done? -- Regards // Oden Eriksson, Deserve-IT.com
