eZ Publish Email Validation Excludes Google Mail Wildcards

Previous topic

Suggestions

Next topic

Author	Message
Heath	Friday 06 July 2007 3:33:57 am Hello Everyone, I'm looking, asking, respectfully pleading for subscriptions, votes and comments in support for improvements to the eZ Publish Email Validation. http://issues.ez.no/IssueView.php?Id=11080 Long title: eZ Publish Email Validation Excludes Google Mail Wildcards from Approved Email Validation Codes eZ Publish Email Validation Excludes Google Mail Wild cards from Approved Email Validation as invalid input. Example #0: thekracker+ezpedia@gmail.com Example #1: thekracker+iHaveAnEzTatooOnMyUpperLeftShoulder@gmail.com Is a valid email I could send email too yet eZ Publish email input validation (Re: ezmail) I have applications where I wish to accept email addresses with +string within the email (A wildcard / label) as valid email input, yet this feature (all be it new from google in the past few years) is not supported but it seems like such a small change to allow these email addresses as valid input. Here is some info about this feature, There are a large number of articles on and in support of this feature world wide! http://www.google.com/search?q=+disposable+Gmail+addresses From: http://lifehacker.com/software/gmail/instant-disposable-gmail-addresses-144397.php `Let's say you need to sign up for a mailing list that interests you, but you're afraid spammers might get your address. We'll call the list "exoticflowers". Sign up with the list using the address "johndoe+exoticflowers@gmail.com". Email to that address will still come to your "johndoe@gmail.com" address even though the "To:" will include that "+exoticflowers" in it. Then set up Gmail filters to shuttle that +exoticflowers email past the inbox to a specific label. Neat.` I and my friends use this feature all the time, yet sadly, a few web sites / cms frameworks do not understand or support this input as a valid email address ... when they should consider the benefits it offers without detracting from existing validation rules. Please update the validation to support this feature! Please show your support for this simple feature to support within eZ Publish! Respectfully, Heath Brookins Consulting http://issues.ez.no/IssueView.php?Id=11080 Brookins Consulting \| http://brookinsconsulting.com/ Certified \| http://auth.ez.no/certification/verify/380350 Solutions \| http://projects.ez.no/users/community/brookins_consulting eZpedia community documentation project \| http://ezpedia.org
kracker (the)	Friday 06 July 2007 3:58:03 am Agreed! Kristof pointed out to me this issue some time ago had been brought up in the eZ Components Mailing List in a rather 'thick' / long thread message, http://lists.ez.no/pipermail/components/2007-July/002754.html I think this can be and <b>should</b> be addressed in eZ Publish <i>separate</i> from eZ Components. I too have longed for this negative feature to be addressed for far too long. <i>//kracker Swollen Members : Bad Dreams : Dark Riders (feat. Buc Fifty)</i> Member since: 2001.07.13 \|\| http://ezpedia.se7enx.com/

Author

Message

Heath

Friday 06 July 2007 3:33:57 am

Hello Everyone,

I'm looking, asking, respectfully pleading for subscriptions, votes and comments in support for improvements to the eZ Publish Email Validation.

http://issues.ez.no/IssueView.php?Id=11080

Long title: eZ Publish Email Validation Excludes Google Mail Wildcards from Approved Email Validation Codes

eZ Publish Email Validation Excludes Google Mail Wild cards from Approved Email Validation as invalid input.

Example #0: thekracker+ezpedia@gmail.com
Example #1: thekracker+iHaveAnEzTatooOnMyUpperLeftShoulder@gmail.com

Is a valid email I could send email too yet eZ Publish email input validation (Re: ezmail)

I have applications where I wish to accept email addresses with +string within the email (A wildcard / label) as valid email input, yet this feature (all be it new from google in the past few years) is not supported but it seems like such a small change to allow these email addresses as valid input.

Here is some info about this feature, There are a large number of articles on and in support of this feature world wide!
http://www.google.com/search?q=+disposable+Gmail+addresses

From: http://lifehacker.com/software/gmail/instant-disposable-gmail-addresses-144397.php

`Let's say you need to sign up for a mailing list that interests you, but you're afraid spammers might get your address. We'll call the list "exoticflowers". Sign up with the list using the address "johndoe+exoticflowers@gmail.com". Email to that address will still come to your "johndoe@gmail.com" address even though the "To:" will include that "+exoticflowers" in it.

Then set up Gmail filters to shuttle that +exoticflowers email past the inbox to a specific label. Neat.`

I and my friends use this feature all the time, yet sadly, a few web sites / cms frameworks do not understand or support this input as a valid email address ... when they should consider the benefits it offers without detracting from existing validation rules.

Please update the validation to support this feature!
Please show your support for this simple feature to support within eZ Publish!

Respectfully,
Heath
Brookins Consulting

http://issues.ez.no/IssueView.php?Id=11080

Brookins Consulting | http://brookinsconsulting.com/
Certified | http://auth.ez.no/certification/verify/380350
Solutions | http://projects.ez.no/users/community/brookins_consulting
eZpedia community documentation project | http://ezpedia.org

kracker (the)

Friday 06 July 2007 3:58:03 am

Agreed!

Kristof pointed out to me this issue some time ago had been brought up in the eZ Components Mailing List in a rather 'thick' / long thread message,
http://lists.ez.no/pipermail/components/2007-July/002754.html

I think this can be and should be addressed in eZ Publish separate from eZ Components.

I too have longed for this negative feature to be addressed for far too long.

//kracker

Swollen Members : Bad Dreams : Dark Riders (feat. Buc Fifty)

Member since: 2001.07.13 || http://ezpedia.se7enx.com/

eZ debug

Timing:	Jan 30 2025 21:26:04
Script start
Timing:	Jan 30 2025 21:26:04
Module start 'layout'
Timing:	Jan 30 2025 21:26:04
Module start 'content'
Timing:	Jan 30 2025 21:26:04
Module end 'content'
Timing:	Jan 30 2025 21:26:04
Script end

Main resources:

Total runtime	0.0424 sec
Peak memory usage	6,144.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0070	588.3906	151.2422
Module start 'layout'	0.0070	0.0039	739.6328	220.7500
Module start 'content'	0.0109	0.0295	960.3828	1,001.8672
Module end 'content'	0.0405	0.0019	1,962.2500	33.9922
Script end	0.0424		1,996.2422

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0032	7.5143	14	0.0002
Check MTime	0.0013	3.0782	14	0.0001
Mysql Total
Database connection	0.0015	3.6007	1	0.0015
Mysqli_queries	0.0024	5.5542	3	0.0008
Looping result	0.0000	0.0303	1	0.0000
Template Total	0.0013	3.1	1	0.0013
Template load	0.0010	2.4316	1	0.0010
Template processing	0.0003	0.6292	1	0.0003
Override
Cache load	0.0007	1.7158	1	0.0007
General
dbfile	0.0046	10.9364	8	0.0006
String conversion	0.0000	0.0157	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs