Scalix Forums

Hi:

I still receive bounced messages from two users that were recently removed from the SAC. I run omsearch -e "G=<firstname>/S=<lastname>" -m @all-attr@ and see no sign of the users existing.

Any ideas?

Thanks.

Can you post the message received from the bounce

Craig

Message could not be delivered to the following recipient:

Jay Adelson / internet/CN=Jay Adelson

because: 'Recipient name not found at destination' [OM 9300]

Supplementary Information:

550 5.1.1 <Adelson@mail.esascorp.com>... User unknown

so you deleted the user.....Do you see the user in the system address book? If you deleted the user, I would think you should receive a bounce back fro the email address, since it does not exist. can you omshowu -n <authID> for the user, and does it give you output??

Craig

I would also take a look at distrobution lists you might be sending to. (personal ones you made in outlook) this could have the names of the people in question, and since they don't exist, then the bounce back will happen....delete them from the distribution list

Thanks for the fast response.

Can't see them in system address book. Already elminated personal distribution lists. When I run the command, I get:

omshowu : [OM 8040] The user can't be found, or has been deleted.

Do you think the SAC groups somehow could be causing the issue?

I am not sure the issue you get? If the user has been deleted should you not receive a bounce? since the user no longer exists

I sent this to a fake user on my server and received back the error
----------------------------- ERROR REPORT ----------------------------- Message could not be delivered to the following recipient:

/ internet
DDT1=RFC-822; DDV1=nouser@digital-adrenaline.com;

because: 'Recipient name not found at destination' [OM 9300]

Supplementary Information:

550 5.1.1 <nouser@digital-adrenaline.com>... User unknown


Do You get me?

We also had a problem with bounces from deleted users. It turned out that some current users had rules which forwarded copies of meeting invitations to those deleted users. I think these rules may have been generated automatically when they delegated access to their calendars at some point in the past.

Deleting those rules using sxaa fixed the problem. It would be cleaner if deleting a user also deleted such rules, but I can see that would be difficult to implement.

Cheers, Paul.

Also, in some version of Outlook, when you send an email to another user, their name is saved and stored for later use with the quick drop down (when you type in Sm you might see Smith, Joe and Smith, Jane). I dont know what this feature is called exactly but I hope i discribed it well. Anyways, These are stored at each users computer within their outlook. Take a look at the "Message in error from:" part and visit that user. You are going to need to type in the deleted user and delete the name from that drop down list.

I have been running into this problem lately and I had no clue how to fix it. I discovered thats what was causing it when I changed the spelling in a users name withing SAC and the drop down name from the old spelling was still in my Outlook. I tried sending the email to the old spelling and I got the same error. So i deleted these names for the deleted users and all is fine!

Hope this helps!

NOTE: On older versions of Outlook (the version that dont have the drop down names), i havent been able to fix it. There is still an association somewhere that i have to find. -This is for users that had forwards set and then one of the users was deleted.

Sorry for the delay, but we are still receiving bounces from a particular deleted user. No issue with any other deleted users. In addition to the items listed above, I have already eliminated the Outlook "cache" feature.

Any other ideas? Thanks much.

Try to check where these users are sending these messages from. I have a couple users that use saved calendar items that have attendees saved with it. 2 of the users have since left so i get the bounces. Check the bounced messages and see those users and watch what they are doing.
See how that works...

Nobody sends to the account in question. The account actually was created as a test user several months ago. Unfortunately, the account is somehow still a part of a system group that many users send to. Don't see the account in the SAC though.