Regexes fail on APEX 3.0

Question

Hello - I've got an application written in APEX 2.2 that I have deployed onto the apex public server. The application makes extensive use of regex validations, and I notice that they all fail on the apex public server. Is there something I need to do to 'convert' these regexes?
For example - here's my old date (DD/MM/YYYY) regex: ^(((0[1-9]|[12]\d|3[01])\/(0[13578]|1[02])\/((1[6-9]|[2-9]\d)\d{2}))|((0[1-9]|[12]\d|30)\/(0[13456789]|1[012])\/((1[6-9]|[2-9]\d)\d{2}))|((0[1-9]|1\d|2[0-8])\/02\/((1[6-9]|[2-9]\d)\d{2}))|(29\/02\/((1[6-9]|[2-9]\d)(0[48]|[2468][048]|[13579][26])|((16|[2468][048]|[3579][26])00))))$
That works fine on my test environment, but on the public site it fails. The 3.0 designer suggests the following instead:
^([012]?[[:digit:]]|3[01])/(0?[[:digit:]]|1[012])/[[:digit:]]{4}$
However, that doesn't take date validity into account. I have another one used to validate UK postcodes:
(((^[BEGLMNS][1-9]\d?)|(^W[2-9])|(^(A[BL]|B[ABDHLNRST]|C[ABFHMORTVW]|D[ADEGHLNTY]|E[HNX]|F[KY]|G[LUY]|H[ADGPRSUX]|I[GMPV]|JE|K[ATWY]|L[ADELNSU]|M[EKL]|N[EGNPRW]|O[LX]|P[AEHLOR]|R[GHM]|S[AEGKL-PRSTWY]|T[ADFNQRSW]|UB|W[ADFNRSV]|YO|ZE)\d\d?)|(^W1[A-HJKSTUW0-9])|(((^WC[1-2])|(^EC[1-4])|(^SW1))[ABEHMNPRVWXY]))(\s*)?([0-9][ABD-HJLNP-UW-Z]{2}))$|(^GIR\s?0AA$)
it doesn't work on the public site and I don't know why - again it's fine on my dev env.
My application is ID 38935, and these regexes can be found at page 100.
Many thanks for any help,
Danny Layne

Answer 1

Just FYI - the online help in your installation of Application Express has a search interface, and will return the results sorted by score. A simple search for 'SMTP' of the online help returns 2 pages of results, with the 5th result being for "Configuring Email Settings".
Joel