We received an email from xxxx@hallo.ms. When our support operator tries to send the reply, OTRS returns a message: "invalid config (xxxx@hallo.ms). The email address works, we have confirmed this.

Bug or feature? My guess is, the email address validation subroutine does not know this relatively new domain.

Feature. There's code to explicitly try to filter out test/junk addresses; in fact, I think it actually checks for mailbox names of "junk", "test" and "xxxx", etc. This is set in SysConfig, see "Config Options: Framework -> Core" and it's "CheckEmailInvalidAddress". The default regexp pattern to detect invalids is: @(aa|aaa|aaaa|aaaaa|abc|any|anywhere|anonymous|bar|demo|example|foo|hello| hallo|me|nospam|nowhere|null|some|somewhere|test|teste.|there|user|xx|xxx|xxxx )\.(..|...)$ Mike Morris The Music Place 1617 Willowhurst Avenue San Jose, CA 95125 (408) 445-ARTS (2787) ------------------------------------ Your Free Quote: I have never been so well pleased, as when I could shift power from my own, on[to] the sholders of others; nor have I ever been able to conceive how any rational being could propose happiness to himself from the exercise of power over others. - Thomas Jefferson, January 26, 1811, letter to Monsieur Destutt de Tracy ------------------------------------