I have a requirement to create the mailboxes of the users with their mailbox alias in Arabic.
I want to know that does Microsoft Exchange allows non-English characters for the alias attribute?
thanks
Arabic not allowed..
The value of Alias can contain letters, numbers and the characters !,
'#', $, %, &, ', *, +, -, /, =, ?, ^, _, `, {, |, } and ~. Periods (.) are allowed, but each period must be surrounded by other valid
characters (for example, help.desk). Unicode characters from U+00A1 to
U+00FF are also allowed. The maximum length of the Alias value is 64
characters.
When you create a recipient without specifying an email address, the
Alias value you specify is used to generate the primary email address
(#). Supported Unicode characters are mapped to
best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed
to oe in the primary email address.
https://learn.microsoft.com/en-us/powershell/module/exchange/users-and-groups/enable-mailuser?view=exchange-ps
Related
What is the usage of tilde symbol (~) in Oracle.
Please share me the output for the below query if we are using the column name and table name with two tilde symbols.
SELECT ~column_name~ from ~Table_name~
From the Database Object Names and Qualifiers documentation:
Nonquoted identifiers must begin with an alphabetic character from your database character set. Quoted identifiers can begin with any character.
Nonquoted identifiers can contain only alphanumeric characters from your database character set and the underscore (_), dollar sign ($), and pound sign (#). Database links can also contain periods (.) and "at" signs (#). Oracle strongly discourages you from using $ and # in nonquoted identifiers.
Quoted identifiers can contain any characters and punctuations marks as well as spaces. However, neither quoted nor nonquoted identifiers can contain double quotation marks or the null character (\0).
In the query:
SELECT ~column_name~ from ~Table_name~
~column_name~ and ~Table_name~ are non-quoted identifiers as they are not surrounded by double-quotes ". However, since they do not start with an alphabetic character and they contain ~ characters (which are not alpha-numeric, _, $ or #) then the identifiers are invalid and the query will raise an exception, outputting:
ORA-00911: invalid character
and will not execute.
fiddle
To directly answer the title of your question, tilde is rarely used as a PL/SQL not equals operator:
begin
if 1 ~= 2 then
dbms_output.put_line('Not equal');
end if;
end;
/
As far as I know, that is the only valid use of tilde in Oracle, and as MTO explained, it certainly can't be used for object names without double quotes.
a%&8b is valid variable name basic
Suggest me if it is valid in VB6
Help me. It is my exams
a%&8b is NOT a valid name. Specifically, you cannot have & and % in the name.
The rules for VBA are:
You must use a letter as the first character.
You can't use a space, period (.), exclamation mark (!), or the characters #, &, $, # in the name.
Name can't exceed 255 characters in length.
Another source on VB6 lists the following:
Variable names in Visual Basic are made up of letters (upper and lower case) and digits. The underscore character, "_", is also permitted. Names must not begin with a digit. Names can be as long as you like.
Some examples of valid (but not very descriptive) Visual Basic variable names:
foo
Bar
BAZ
foo_bar
a_foo42_
QuUx
Some examples of invalid Visual Basic variable names:
2foo
must not begin with a digit
my foo
spaces not allowed in names
$foo
$ not allowed -- only letters, digits, and _
while
language keywords cannot be used as names
_xxx
leading underscore not allowed.
In Oracle '%' stands for any characters in that position.
Example:
Select * from table where id like '%1'
This stands for anything behind the number 1 : XXXXXXXXXXXX1 99999999991.
Is there any other character to express only 1 character ?.
Example of what I mean: (im going to use ~ as that reserved character)
Select * from table where id like '~1'
In this case only 91, x1, X1... etc would enter the select, but XX1 woudn't as you only used one ~.
Select * from table where id like '~~~1'
xxx1, 9991, 8881, etc....
Hope I explained myself, english is not my native language.
Only one wildcard character is represented by underscore, _
You can refer to Oracle's LIKE condition documentation:
like_condition::=
In this syntax:
char1 is a character expression, such as a character column, called the search value.
char2 is a character expression, usually a literal, called the pattern.
esc_char is a character expression, usually a literal, called the escape character.
[...]
The pattern can contain special pattern-matching characters:
An underscore (_) in the pattern matches exactly one character (as opposed to one byte in a multibyte character set) in the value.
A percent sign (%) in the pattern can match zero or more characters (as opposed to bytes in a multibyte character set) in the value. The pattern '%' cannot match a null.
Use an _ underscore.
We are using Microsoft Certificate Request (CertReq.exe) to build certificate requests programmatically. For this purpose, we have to create input INF files, see docs here.
The Subject property is defined as Relative Distinguished Name string values, which should be encoded like specified by RFC 1779.
That essentially means to simply escape some characters (", +, ,, ;, <, >, or \) by prefixing it with \.
The problem is, that I could not figure out, how to properly encode a Subject that has the property "O=Foo + Bar".
Input (relevant INF part):
[NewRequest]
Subject = "CN=www.foo.de,OU=Foobar,O=Foo \+ Bar,L=Foo,S=Bar,C=DE"
Output:
The string contains an invalid X500 name attribute key, oid, value or delimiter. 0x80092023 (-2146885597 CRYPT_E_INVALID_X500_STRING)
c:\file_path.inf([NewRequest] Subject = "CN=www.foo.de,OU=Foobar,O=Foo \+ Bar,L=Foo,S=Bar,C=DE")
Duplicate escaping (using "and \) is discouraged by RFC 1799, but seems to solve problems in LDAP queries (see here, f.i.).
However, we also tried do not use the quotation to specify a subject, but got another unwanted result.
Input:
[NewRequest]
Subject = CN=www.foo.de,OU=Foobar,O=Foo \+ Bar,L=Foo,S=Bar,C=DE
Output:
The data is invalid. 0x8007000d (WIN32: 13 ERROR_INVALID_DATA)
c:\file_path.inf([NewRequest] Subject = "CN=www.foo.de", "OU=Foobar", "O=Foo \+ Bar", "L=Foo", "S=Bar", "C=DE")
The whole process works without the + sign. What is the correct way to encode a RDN (relative distinguished name) in the INF file?
Normally the + character has special meaning. You can disable that behavior like this and just use the + character like you would any other.
Subject = CN=www.foo.de,OU=Foobar,O=Foo + Bar,L=Foo,S=Bar,C=DE
X500NameFlags = 0x20000000
The plus character is normally reserved to separate multiple values for multi-valued RDNs.
I'm not entirely sure why escaping it does not work with CertEnroll as you are expecting it to.
I am using Ruby on Rails 3.0.9 and I would like to validate a string that can contain only characters (case insensitive characters), blank spaces and numbers.
More:
special characters are not allowed (eg: !"£$%&/()=?^) except - and _;
accented characters are allowed (eg: à, è, é, ò, ...);
The regex that I know from this question is ^[a-zA-Z\d\s]*$ but this do not validate special characters and accented characters.
So, how I should improve the regex?
I wrote the ^(?:[^\W_]|\s)*$ answer in the question you referred to (which actually would have been different if I'd known you wanted to allow _ and -). Not being a Ruby guy myself, I didn't realize that Ruby defaults to not using Unicode for regex matching.
Sorry for my lack of Ruby experience. What you want to do is use the u flag. That switches to Unicode (UTF-8), so accented characters are caught. Here's the pattern you want:
^[\w\s-]*$
And here it is in action at Rubular. This should do the trick, I think.
The u flag works on my original answer as well, though that one isn't meant to allow _ or - characters.
Something like ^[\w\s\-]*$ should validate characters, blank spaces, minus, and underscore.
Validation string only for not allowed characters. In this case |,<,>," and &.
^[^|<>\"&]*$