While configuring JEMH, we encountered the following problem:
We have an Inbound Mail Account *.*.*@gmail.com.
This throws the following error/exception:
When we use the same E-Mail as a test case, there is no error.
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...
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.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs