Tried, but that doesn't help. The cluster is AD joined, so adding a mapping makes no sense in this case.
Ok, that seems to be the issue. Login names are not the same as emailadresses... How to proceed with 5000+ users which have their emailadress correctly in the email field in AD?
If you check with Isilon wether they can provide some customized solution, let us know the response.
A non-intrusive solution could be: map to @isilonusers.example.com and have a mail sever for that domain which forwards or re-sends the mails to addresses listed in AD.
There is also a (small) chance for this minimal-intrusive method on the Isilon (still requires quite sophistical crafting):
[1] have the Isilon attempt to deliver mail to each user locally (on the Isilon itself).
[2] have a $HOME/.forward file for each user containing the address taken for AD
[3] have the Isilon mail system honor the .forward files and send stuff out...
ad [1]: need to figure out how to do it: is that the default without mapping? need to map to @localhost? need to add some id mapping (not to confuse with mail notif. mapping) to make AD accounts also behave as UNIX accounts?
ad [2]: need to understand the Isilon system's notion of UNIX home dirs for AD accounts: add explicitly in AD (with UNIX support enabled in AD)? The local UNIX dirs and .forward files will need to be created/updated by some script.
ad [3]: might need to enable use of .forward files in the Isilon mail config, if not on by default. Might be frowned upon by Isilon support.
The is a very rough outline, I hope you get the idea. Definitely not trivial to implement if at all possible, but requires no external resources nor large modification of Isilon internal stuff.
Peter_Sero
4 Operator
•
1.2K Posts
0
December 6th, 2013 05:00
Have you tried out the "Email Mapping Rules" for quota notifications?
See p 228 of the 7.0 Admin guide.
-- Peter
jpveen
1 Rookie
•
85 Posts
0
December 11th, 2013 00:00
Tried, but that doesn't help. The cluster is AD joined, so adding a mapping makes no sense in this case.
Something goes wrong inside, maybe need to enable some debugging for quota notifications somewhere. Anybody a clue where? Or another tip?
Peter_Sero
4 Operator
•
1.2K Posts
1
December 11th, 2013 04:00
Check /var/log/messages for:
... isi_quota_notify_d: Error sending ....
... isi_quota_notify_d: Successfully sent to ...
> The cluster is AD joined, so adding a mapping makes no sense in this case.
Sorry I don't agree -- the way it is supposed to work with AD (as well as LDAP which we are using here):
- mail addresses from AD or LDAP resp. are ignored
- the user (login) name is extracted from the account: DOMAIN\joe
- the configured "mapping" email domain is appended: joe@example.com
Anyway, you will see what's going on in the log messages.
Cheers
-- Peter
jpveen
1 Rookie
•
85 Posts
0
December 11th, 2013 05:00
Ok, thanks for the tip, we will check this!
jpveen
1 Rookie
•
85 Posts
0
December 11th, 2013 08:00
Tried, but that doesn't help. The cluster is AD joined, so adding a mapping makes no sense in this case.
Ok, that seems to be the issue. Login names are not the same as emailadresses... How to proceed with 5000+ users which have their emailadress correctly in the email field in AD?
Any script that will fix this?
Peter_Sero
4 Operator
•
1.2K Posts
0
December 12th, 2013 06:00
I see...
If you check with Isilon wether they can provide some customized solution, let us know the response.
A non-intrusive solution could be: map to @isilonusers.example.com and have a mail sever for that domain which forwards or re-sends the mails to addresses listed in AD.
There is also a (small) chance for this minimal-intrusive method on the Isilon (still requires quite sophistical crafting):
[1] have the Isilon attempt to deliver mail to each user locally (on the Isilon itself).
[2] have a $HOME/.forward file for each user containing the address taken for AD
[3] have the Isilon mail system honor the .forward files and send stuff out...
ad [1]: need to figure out how to do it: is that the default without mapping? need to map to @localhost? need to add some id mapping (not to confuse with mail notif. mapping) to make AD accounts also behave as UNIX accounts?
ad [2]: need to understand the Isilon system's notion of UNIX home dirs for AD accounts: add explicitly in AD (with UNIX support enabled in AD)? The local UNIX dirs and .forward files will need to be created/updated by some script.
ad [3]: might need to enable use of .forward files in the Isilon mail config, if not on by default. Might be frowned upon by Isilon support.
The is a very rough outline, I hope you get the idea. Definitely not trivial to implement if at all possible, but requires no external resources nor large modification of Isilon internal stuff.
Good luck
-- Peter