Multiple Addresses, Single Account, Filter to Folder - How?

[Flish]

Ok, can't flaw the result, that works fine, accounts@ is showing as the To: header, and I assume the scalix rules will work on that and hence filter nicely.

I can pick some big holes in the method though, just feels like the wrong way to do things. Is this a bug, or part of the deliberate 'feature' where you can only send from the primary email address? Because at the moment it does merit asking the question as to what the point of addition email addresses is?

Will reconfigure all this way, just hope I can sell this 'method' in the mean time as we've got at least 2 clients begging for something like this, at this pricepoint.

[florian]

Hi Flish,

for the time being, I am tracking this as a bug as I agree that your use case is a valid and probably not totally uncommon one.

On the other hand, I would probably not call this a critical problem; most people would put aliases on users that still identify the person - e.g. you can reach me at givenname@scalix.com as well as given.last@scalix.com, but I as recipient couldn't care less about which one you use. Outgoing it will be given.last@, which is what I want.

It's certainly different for "generic" addresses such as "sales@"; however, there is multiple ways modelling those:
- use as alias on a personal account (that's what you and probably many small shops do)
- use as PDL with one or multiple people on it (more generic)
- use as eMail address on public folder (multiple readers, independent read/unread marks, can't send as)
- create separate mailbox (multiple readers through delegation, common read/unread marks, can send as)

Anyway, if you need any more help on this one, please let us know.

Florian.

[Flish]

Anyway, if you need any more help on this one, please let us know.

No, No, all's good for now, this much is working nicely. That said I've a problem with clamd killing the service router, but that's for tomorrow and a different thread.

As to this problem, I think you need to make this product as flexible as possible. Everyone works differently, and not necessarily the logical way, but any form of change will be frowned upon, so if people evaluating Scalix can't see an obviosu way of doing what they currently do they'll walk away. This, and the ability to send as another alias or similar (this could be an on / off feature set by an admin) could be a stumbling block that costs you guys money.

Actually, if you know who deals with the Partner / Reseller aplications you could give them a prod as heard nothing since sent details on line, there's not a hurry, but contact is good.