2011/1/25 Norman Maurer <[email protected]>: > 2011/1/25 Eric Charles <[email protected]>: > [...] >> 2.- Since we enabled the SMTP ValidRcptHandler, we need to really create the >> user, before using it as an virtual user. This was not the case before. The >> need to previously create a user does not worry me, but I find strange that, >> depending on smtp configuration, we would or not need to create a user to >> define a virtualuser. > > I think the need of having the existing user before add the mapping is > a good think. We also would need to check if there is a mapping when > deleting a user and remove it too.
I don't agree. I usually think at aliasing as "rewriting" so I expect to write aliases like this alias@mydomain maps to existinguser@mydomain At least this is what I was used to do in sendmail (are other MTA different from this??) It's like "search&replace" you usually put "search" on the left and replace on the "right". >> 3.- JIRA-1126 Disallow the creation of alias from non-existing username: I >> think this is needed so we don't arrive to situation where mails are no more >> delivered in case a bad usage of the API (reversing the method params). > > +1 Not sure. I often use aliasing to "virtual addresses". THen I have matchers to match this virtual addresses and do something. So they are not users. In my James I usually have 1 single user that is used from my webapplication to submit messages, no other james users. Still I use aliasing. Sendmail also allow bounces to be generated by virtusertable, e.g: *@your-comapny.com maps to "error:5.1.1:550 No such user." (I don't know what aliasing is supported by trunk VUTs, so maybe I'm completely wrong) Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
