While configuring JEMH, we encountered the following problem:
We have an Inbound Mail Account *.*.*@gmail.com.
This throws the following error/exception:
Capture.PNG
Capture.PNG
When we use the same E-Mail as a test case, there is no error.
What's wrong?
Do I have to fill in the jemhAddresseeRegexps field and handle the "*.*.*@gmail.com*?
The expression you have is a broken regexp. In Regexp, dot '.' means any character, star '*' means any number of the preceding character. to match anything use (without quotes) .*@gmail.com
Supplying a catchemail address (specific) and/or a regular expressions helps JEMH identify the 'inbox' mail addresses, so they can be filtered from storage and related notifications. Without this, JEMH will start notifying your mailbox by considering at an email only user...
I changed the expression in the jemhAddresseeRegexps field:
E-Mail.PNG
But the error / exception is thrown.
Initially, we only had a Catch Email Address defined. That's when the exception was thrown the first time. Then I added the regexps...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
He might actually want to ensure that there are at least two dots in it, in which case ".*\..*\..*@gmail.com" would get you there. But the basic idea of this answer, that the field takes a formal regular expression as opposed to simple filename-style wildcard globbing looks correct to me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Join the largest European gathering of the Atlassian Community and reimagine what’s possible when great teams and transformative technology come together. Plus, grab your Super Fan ticket now and save over €1,000 on your pass before prices rise on 3 June.
Register nowOnline forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.