Closed Bug 904153 Opened 11 years ago Closed 11 years ago

Not receiving LDAP expiration emails

Categories

(Infrastructure & Operations :: Infrastructure: LDAP, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: peter, Assigned: peter)

Details

This came into the service desk mailbox. Not sure what the best way to assist here is. Yumi's email address is ochiai@mozilla-japan.org but her LDAP is yochiai@mozilla-japan.org so she does not receive her expiration emails. _________________________________ Hi Peter, Thank you ! Do you send notice to people who are expiring password and need to create new one? If so, it would be very appreciated that you send the notice to ochiai@mozilla-japan.org, not yochiai@mozilla-japan.org. Regards, Yumi
The reminder mail always sends to the DN of the account. If that DN is not a routable address, there isn't anything we can do. Perhaps it can be made routable on their end? (not sure who manages that domain). If not, then perhaps the account can be disabled and a new account created with the proper address.
Flags: needinfo?(peter)
Hey Yumi, Do you know who manages your mailing system? And can you file a ticket to have them create yochiai@mozilla-japan.org as an alias for your email address? Alternatively we can just recreate your account with the ochiai@mozilla-japan.org as the name. Please let me know which you prefer.
Flags: needinfo?(peter) → needinfo?(ochiai)
Hi Peter, I think Makoto Kato(mkato@mozilla-japan.org) manages our email system, but he is on PTO.I will ask him which is better and let you know possibly next Tuesday.Thank you very much for help.
Flags: needinfo?(ochiai)
Hi Peter, I talked to Makoto this issue and he is creating yochiai@mozilla-japan.org as an alias for ochiai@mozilla-japan.org. He said it's the best way, not to change everything. Thank you very much for your support.
Awesome =) Marking this as resolved.
Assignee: infra → peter
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.