Email Field Validation Incorrectly Rejects RFC-Compliant Addresses (Forward Slashes)

Email Field Validation Incorrectly Rejects RFC-Compliant Addresses (Forward Slashes)

I've encountered a validation issue with Zoho Creator's Email field that rejects RFC-compliant email addresses containing forward slashes, and I'm hoping the Zoho team can address this in a future update.

The Issue
When entering an email address containing a forward slash in the local-part (before the @), Zoho Creator displays the error message: "Format for email address is example@example.com" — despite forward slashes being explicitly permitted by RFC standards.

What the RFC Standards Say
According to RFC 5321 and RFC 5322, the following printable characters are valid in the local-part of an email address:
!#$%&'*+-/=?^_`{|}~
The forward slash (/) is explicitly included in this list.

Valid Email Examples from RFC Documentation:
The Problem
Zoho Creator's email field validation incorrectly rejects RFC-compliant email addresses containing forward slashes, preventing users from entering legitimate email addresses.
Email Address RFC Compliant Zoho Creator Zoho CRM
john.smith@example.com ✓ Valid ✓ Accepted ✓ Accepted
user+tag@example.com ✓ Valid ✓ Accepted ✓ Accepted
name/surname@example.com ✓ Valid ✗ Rejected ✓ Accepted
dept/team/user@example.com ✓ Valid ✗ Rejected ✓ Accepted
Inconsistency Within Zoho Ecosystem
This creates a significant inconsistency: Zoho CRM correctly accepts forward slashes in email addresses, while Zoho Creator rejects them.

This means:
  • Data imported from Zoho CRM to Creator may fail validation
  • Integrations between CRM and Creator could encounter unexpected errors
  • Users accustomed to CRM's behavior are confused by Creator's stricter validation
  • Developers building cross-product solutions must implement additional handling
Real-World Impact
This limitation affects organizations where:
  • Departmental email structures use slashes (e.g., sales/support@company.com)
  • Legacy email systems employ UUCP-style routing with special characters
  • International organizations use RFC-compliant but unconventional email formats
  • Data migration projects encounter validation failures on legitimate addresses
  • API integrations fail when processing emails from external systems that allow forward slashes
What Should Happen Instead
Proposed Solution:
Update Zoho Creator's email field validation to align with RFC 5321/5322 standards and match the behavior of Zoho CRM. The validation regex should accept all RFC-permitted printable characters in the local-part, including forward slashes.

This would ensure:
  • Consistent behavior across Zoho products
  • Compliance with international email standards
  • Seamless data flow between CRM and Creator
  • No false rejections of legitimate email addresses
Request to Zoho Team

Can this be addressed in a future update?

The current validation forces users to either reject legitimate email addresses or implement custom text fields with manual validation — neither of which is ideal. The inconsistency with Zoho CRM is particularly problematic for organizations using both products.

1. Standards Compliance
Accept all RFC-compliant email addresses 		2. Product Consistency
Match Zoho CRM's validation behavior

Users shouldn't have to choose between using the built-in email field and accepting valid email addresses.

Community Input Requested: Has anyone else encountered this validation issue or found a reliable workaround?


📚 Documentation References: