需在RE2引擎下实现不含指定前缀的有效邮箱匹配正则（无环视）

Got it, let's work through this problem since RE2 doesn't support lookarounds—we'll need to structure the regex to explicitly match only the valid emails we want, instead of trying to exclude the unwanted ones with negative assertions.

Step 1: Fix & Optimize the Base Email Regex #

First, let's tweak your original regex to address gaps and simplify it:

• Your original local part didn't include /, but your examples have emails like blern/firstname.lastname@gmail.com, so we need to add / to the allowed characters.
• We can simplify the repetitive patterns for local and domain parts to make the regex cleaner and more efficient.

Here's the optimized base pattern (without exclusion logic yet):

\b[A-Za-z0-9](?:[A-Za-z0-9\-._/]*[A-Za-z0-9])?@(?:[A-Za-z0-9](?:[A-Za-z0-9-]*[A-Za-z0-9])?\.)+[A-Za-z0-9](?:[A-Za-z0-9-]*[A-Za-z0-9])?\b

• Local part: [A-Za-z0-9](?:[A-Za-z0-9\-._/]*[A-Za-z0-9])? ensures it starts/ends with alphanumeric, and allows -._/ in between (supports single-character local parts like a@example.com too).
• Domain part: Simplified to match valid domain segments (starts/ends with alphanumeric, allows hyphens in between) followed by a TLD.
• Word boundaries (\b): Kept to match emails within text; if you're validating full email strings, replace \b with ^ and $ for stricter anchoring.

Step 2: Add Exclusion for "blern" Prefixes (No Lookarounds) #

Since RE2 can't do negative lookarounds, we'll split the local part into branches that explicitly avoid starting with blern (either directly or followed by /). We cover every possible way a local part doesn't start with blern:

\b(?:
  [A-Za-cd-z0-9](?:[A-Za-z0-9\-._/]*[A-Za-z0-9])?|  # Starts with non-'b' alphanumeric
  b[A-Za-km-z0-9](?:[A-Za-z0-9\-._/]*[A-Za-z0-9])?| # Starts with 'b' but not 'bl'
  bl[A-Za-df-z0-9](?:[A-Za-z0-9\-._/]*[A-Za-z0-9])?|# Starts with 'bl' but not 'ble'
  ble[A-Za-cs-z0-9](?:[A-Za-z0-9\-._/]*[A-Za-z0-9])?|# Starts with 'ble' but not 'bler'
  bler[A-Za-mo-z0-9](?:[A-Za-z0-9\-._/]*[A-Za-z0-9])?# Starts with 'bler' but not 'blern'
)@(?:[A-Za-z0-9](?:[A-Za-z0-9-]*[A-Za-z0-9])?\.)+[A-Za-z0-9](?:[A-Za-z0-9-]*[A-Za-z0-9])?\b

• Each branch covers a scenario where the local part can't possibly start with blern, so any email starting with blern (like blernsoandso@gmail.com or blern/soandso@gmail.com) won't match.

Step 3: Extend to Multiple Excluded Prefixes (e.g., "blern" + "other") #

If you need to exclude another prefix like other, just add corresponding branches for that word:

\b(?:
  # Existing branches for 'blern' exclusion
  [A-Za-cd-z0-9](?:[A-Za-z0-9\-._/]*[A-Za-z0-9])?|
  b[A-Za-km-z0-9](?:[A-Za-z0-9\-._/]*[A-Za-z0-9])?|
  bl[A-Za-df-z0-9](?:[A-Za-z0-9\-._/]*[A-Za-z0-9])?|
  ble[A-Za-cs-z0-9](?:[A-Za-z0-9\-._/]*[A-Za-z0-9])?|
  bler[A-Za-mo-z0-9](?:[A-Za-z0-9\-._/]*[A-Za-z0-9])?|
  # New branches for 'other' exclusion
  o[A-Za-np-z0-9](?:[A-Za-z0-9\-._/]*[A-Za-z0-9])?|
  ot[A-Za-su-z0-9](?:[A-Za-z0-9\-._/]*[A-Za-z0-9])?|
  oth[A-Za-gi-z0-9](?:[A-Za-z0-9\-._/]*[A-Za-z0-9])?|
  othe[A-Za-df-z0-9](?:[A-Za-z0-9\-._/]*[A-Za-z0-9])?
)@(?:[A-Za-z0-9](?:[A-Za-z0-9-]*[A-Za-z0-9])?\.)+[A-Za-z0-9](?:[A-Za-z0-9-]*[A-Za-z0-9])?\b

Key Optimizations Recap #

1. Included / in local part: Supports your use case with slashes in the local segment.
2. Simplified patterns: Replaced repetitive capture groups with non-capturing groups for efficiency, and merged redundant logic.
3. Explicit exclusion: Used branch logic to avoid unwanted prefixes without relying on lookarounds, which works perfectly with RE2.
4. Flexible boundaries: Use \b for matching emails in text, or ^/$ if validating full email strings.

内容的提问来源于stack exchange，提问作者B. Allred