[dev] "Recipient address does not match the currently selected identity"

[Michael M Slusarz]

Quoting Chuck Hagenbuch <chuck at horde.org>:

> Quoting Michael M Slusarz <slusarz at horde.org>:
>
>> Quoting Chuck Hagenbuch <chuck at horde.org>:
>>
>>> This seems rather unfriendly. First of all the error message is  
>>> confusing; even knowing the code I didn't know what it could mean.  
>>> It might be okay if it was smart enough to somehow know which  
>>> addresses were list addresses and which weren't, but it's not.  
>>> I've seen this:
>>
>> Very confused by this statement.  IMP isn't smart enough to figure  
>> out whether the message is a list message or not - more accurately,  
>> IMP doesn't care.  It is the *user* who explicitly determines this  
>> via their identity preferences.
>
> Okay. Where did I do that?

IMP -> Options -> Personal Information -> "Addresses to explicitly tie  
to this identity"

List addresses should go here (e.g. dev at lists.horde.org)

>> This recipient checking feature has *nothing* to do with list  
>> addresses - it deals solely with tied addresses.  OTOH, list  
>> addresses are probably the main thing tied addresses are useful for.
>
> I'm still not sure what tied addresses are, and I'm pretty sure I  
> don't have any of them - the tied addresses field of all of my  
> identities is empty.

See above for list addresses - they are useful as tied addresses.   
Also, say you have a certain person (business contact) that you always  
want to reply to with a certain identity (e.g. your business e-mail)  
rather than the default identity (which might be your personal e-mail  
address).  This person's e-mail address will also go into the tied  
addresses list.

>> As far as tied addresses - if you are unsure of what they are then  
>> this is probably bad news on our part re: documentation since tied  
>> addresses have been around for 6-7 years.  A tied address indicates  
>> what identity to use when replying to a message.  It is a list of  
>> From e-mail addresses that are used, at the time of replying, to  
>> determine what the default identity should be.
>
> Is there any reason that this check should ever trigger when not  
> replying, then?

Yes.  Example:

Goal: I want to send a new message to a mailing list.
1. Click on new message and enter list's address in To: field
2. Type message
3. Send message.

In my personal case, I am subscribed to all Horde lists as  
slusarz at horde.org.  But this is not my default e-mail address.  So if  
I go through the above steps, my message will always bounce back since  
Horde lists are closed.  Doing the tied address check after hitting  
send (the first time only) will prevent this from happening - or at  
least give me a chance to prevent it from happening.

Same thing with forwards.  If I forward a message to someone else, I  
am most likely manually entering their e-mail address.  So we need to  
check before sending that the sending identity is correct in relation  
to the recipient addresses.

>> The issue you have raised has to do with including the identity  
>> e-mail itself in the the list of addresses for an identity.  You've  
>> raised a case that seems to indicate that these e-mail addresses  
>> should be excluded from this list.

I've excluded own addresses when doing this tied/recipient check.   
Let's see if that fixes things.

michael

-- 
___________________________________
Michael Slusarz [slusarz at horde.org]