Regex help for email

12 Message(s) by 5 Author(s) originally posted in php programming

From: gezerpunta

Date: Thursday, October 18, 2007

Hi

I need a regex

The {GNU} {regular expression} matching library.  See also
	{Rx}.

code

<software> Instructions for a computer in some programming
	language, often {machine language}.  The word "code" is often
	used to distinguish instructions from {data} (e.g. "The code
	is marked 'read-only'") whereas "{software}" is used in
	contrast with "{hardware}" and may consist of more than just
	code.

	(2000-04-08)

for parsing

<language> An {algorithm} or program to determine the
	syntactic structure of a sentence or string of symbols in some
	language.  A parser normally takes as input a sequence of
	{tokens} output by a {lexical analyser}.  It may produce some
	kind of {abstract syntax tree} as output.  One of the best
	known {parser generators} is {yacc}.

	(1997-07-21)

this string

<programming> A sequence of {data} values, usually {bytes},
	which usually stand for {characters} (a "character string").
	The {mapping} between values and characters is determined by
	the {character set} which is itself specified implcitly or
	explicitly by the environment in which the string is being
	interpreted.

	The most common character set is {ASCII} but, since the late
	1990s, there has been increased interest in larger character
	sets such as {Unicode} where each character is represented by
	more than eight {bits}.

	Most programming languages consider strings (e.g.
	"124:shabooya:\n", "hello world") basically distinct from
	numbers which are typically stored in fixed-length {binary} or
	{floating-point} representation.

	A {bit string} is a sequence of {bits}.

	(1999-12-21)

to an email array

"mnp test" <celo@xxxxxxxxxxx>,"test testt"
<otur@xxxxxxxxxxx>,sett@xxxxxxxxxxx,test@xxxxxxxxxxx

thanks

From: ZeldorBlat

Date: Thursday, October 18, 2007

wrote in message

In {object-oriented programming} sending a message to an
	{object} (to invoke a {method}) is equivalent to calling a
	{procedure} in traditional programming languages, except that
	the actual code executed may only be selected at run time
	depending on the {class} of the object.  Thus, in response to
	the message "drawSelf", the method code invoked would be
	different if the target object were a circle or a square.

	(1995-02-16)

Hi
I need a regex code for parsing this string to an email array
"mnp test" <c...@xxxxxxxxxxx>,"test testt"
<o...@xxxxxxxxxxx>,s...@xxxxxxxxxxx,t...@xxxxxxxxxxx
thanks

Why do you need a regex? Why not just use explode?

<http://www.php.net/explode>

From: AnrDaemon

Date: Sunday, October 21, 2007

Greetings, gezerpunta.
In reply

See {followup}.

to Your message dated Thursday, October 18, 2007, 18:59:31,

g> I need a regex code for parsing this string to an email array

g> "mnp test" <celo@xxxxxxxxxxx>,"test testt"
g> <otur@xxxxxxxxxxx>,sett@xxxxxxxxxxx,test@xxxxxxxxxxx

Something like

<?php

$s = '"mnp test" <celo@xxxxxxxxxxx>,"test testt" <otur@xxxxxxxxxxx>, sett@xxxxxxxxxxx,test@xxxxxxxxxxx';

if(preg_match_all('#[\s\,]<?([0-9A-Za-z\_]+(?:[\-\.][0-9A-Za-z\_]+)*\@xxxxxxxxxxx[0-9A-Za-z]+(?:[\.\-\_][0-9A-Za-z]+)+)>?#xi', $s, $ta))
{
var_export($ta[1]);
}

?>--
Sincerely Yours, AnrDaemon <anrdaemon@xxxxxxxxxxx>

From: AnrDaemon

Date: Sunday, October 21, 2007

Greetings, gezerpunta.
In reply to Your message dated Thursday, October 18, 2007, 18:59:31,

<?php

$s = 'celo@xxxxxxxxxxx, "mnp test" <celo@xxxxxxxxxxx>,"test testt" <otur@xxxxxxxxxxx>, sett@xxxxxxxxxxx,test@xxxxxxxxxxx';

if(preg_match_all('#(?:^|[\s\,])<?([0-9A-Za-z\_]+(?:[\-\.][0-9A-Za-z\_]+)*\@xxxxxxxxxxx[0-9A-Za-z]+(?:[\.\-\_][0-9A-Za-z]+)+)>?#xi', $s, $ta))
{
var_export($ta[1]);
}

?>--
Sincerely Yours, AnrDaemon <anrdaemon@xxxxxxxxxxx>

From: Steve

Date: Monday, October 22, 2007

Greetings, gezerpunta.
In reply to Your message dated Thursday, October 18, 2007, 18:59:31,
<?php
$s = 'celo@xxxxxxxxxxx, "mnp test" <celo@xxxxxxxxxxx>,"test testt" <otur@xxxxxxxxxxx>,
sett@xxxxxxxxxxx,test@xxxxxxxxxxx';
if(preg_match_all('#(?:^|[\s\,])<?([0-9A-Za-z\_]+(?:[\-\.][0-9A-Za-z\_]+)*\@xxxxxxxxxxx[0-9A-Za-z]+(?:[\.\-\_][0-9A-Za-z]+)+)>?#xi',
$s, $ta))
{
var_export($ta[1]);
}

of course you'd. however, notice that whatever your prowess at regex,
you lack understanding of the basic email conventions explained in the
rfc(s). your preg does not allow for atomic

<jargon> (From Greek "atomos", indivisible) Indivisible;
	cannot be split up.

	For example, an instruction may be said to do several things
	"atomically", i.e. all the things are done immediately, and
	there is no chance of the instruction being half-completed or
	of another being interspersed.  Used especially to convey that
	an operation cannot be interrupted.

	An atomic {data type} has no internal structure visible to the
	program.  It can be represented by a flat {domain} (all
	elements are equally defined).  Machine {integers} and
	{Booleans} are two examples.

	An atomic {database transaction} is one which is guaranteed to
	complete successfully or not at all.  If an error prevents a
	partially-performed transaction from proceeding to completion,
	it must be "backed out" to prevent the database being left in
	an inconsistent state.

	[{Jargon File}]

	(2000-04-03)

account names. ;^)

hmmmm...this *does* (and then some).

function isEmail($email)
{
if (!$email){ return false; }
$pattern =
"/^((\"[^\"]*?\")|([^\<\>\@xxxxxxxxxxx\,\;\:\\\"\[\]\s\*\/]+))@xxxxxxxxxxx(\[((25[0-5]|2[0-4][0-9]|1[0-9][0-9]|[1-9][0-9]|[0-9])\.){3}|((([a-zA-Z0-9\-]+)\.)+))([a-zA-Z]{2,}|(25[0-5]|2[0-4][0-9]|1[0-9][0-9]|[1-9][0-9]|[0-9])\])$/si";
return preg_match($pattern, $email);
}

the pattern above simply needs to be applied to the entire string, and you
get what you want.

From: Steve

Date: Wednesday, October 24, 2007

Greetings, Steve.
In reply to Your message dated Monday, October 22, 2007, 20:53:00,
Greetings, gezerpunta.
In reply to Your message dated Thursday, October 18, 2007, 18:59:31,
<?php
$s = 'celo@xxxxxxxxxxx, "mnp test" <celo@xxxxxxxxxxx>,"test testt"
<otur@xxxxxxxxxxx>,
sett@xxxxxxxxxxx,test@xxxxxxxxxxx';
if(preg_match_all('#(?:^|[\s\,])<?([0-9A-Za-z\_]+(?:[\-\.][0-9A-Za-z\_]+)*\@xxxxxxxxxxx[0-9A-Za-z]+(?:[\.\-\_][0-9A-Za-z]+)+)>?#xi',
$s, $ta))
{
var_export($ta[1]);
}
S> of course you'd. however, notice that whatever your prowess at
regex,
S> you lack understanding of the basic email conventions explained in the
S> rfc(s). your preg does not allow for atomic account names. ;^)
Example please?

read the freaking email rfc(s).

What You mean "atomic account names"?

hmmmm, what do you think?

the rfc's allow for 'illegal' character

<character> An {atom} in a {character repertoire}.

	Compare with {glyph}.

	(1998-10-18)

s in account names as long as they're
encapsulated. this is to compensate for non-latin character sets
(particularly, non-english sets). is that ringing a bell?

From: Steve

Date: Thursday, October 25, 2007

Greetings, Steve.
In reply to Your message dated Wednesday, October 24, 2007, 21:34:41,
<?php
$s = 'celo@xxxxxxxxxxx, "mnp test" <celo@xxxxxxxxxxx>,"test testt"
<otur@xxxxxxxxxxx>,
sett@xxxxxxxxxxx,test@xxxxxxxxxxx';
if(preg_match_all('#(?:^|[\s\,])<?([0-9A-Za-z\_]+(?:[\-\.][0-9A-Za-z\_]+)*\@xxxxxxxxxxx[0-9A-Za-z]+(?:[\.\-\_][0-9A-Za-z]+)+)>?#xi',
$s, $ta))
{
var_export($ta[1]);
}
S> of course you'd. however, notice that whatever your prowess at
regex,
S> you lack understanding of the basic email conventions explained in
the
S> rfc(s). your preg does not allow for atomic account names. ;^)
Example please?
S> read the freaking email rfc(s).
Do it for me, please.

WTF?!!! I read it for me...and those that pay me. you may continue to be
lazy at your liesure.

What You mean "atomic account names"?
S> hmmmm, what do you think?
S> the rfc's allow for 'illegal' characters in account names as long as
they're
S> encapsulated. this is to compensate for non-latin character sets
S> (particularly, non-english sets). is that ringing a bell?
Never saw any in 10 years.

and you speak english and type

<theory, programming> (Or "data type") A set of values from
	which a {variable}, {constant}, {function}, or other
	{expression} may take its value.  A type is a classification
	of data that tells the {compiler} or {interpreter} how the
	programmer intends to use it.  For example, the process and
	result of adding two variables differs greatly according to
	whether they are integers, floating point numbers, or strings.

	Types supported by most programming languages include
	{integers} (usually limited to some range so they will fit in
	one {word} of storage), {Booleans}, {floating point numbers},
	and characters.  {Strings} are also common, and are
	represented as {lists} of characters in some languages.

	If s and t are types, then so is s -> t, the type of
	{functions} from s to t; that is, give them a term of type s,
	functions of type s -> t will return a term of type t.

	Some types are {primitive} - built-in to the language, with no
	visible internal structure - e.g. Boolean; others are
	composite - constructed from one or more other types (of
	either kind) - e.g. {lists}, {arrays}, {structures}, {unions}.
	{Object-oriented programming} extends this with {classes}
	which encapsulate both the structure of a type and the
	operations that can be performed on it.

	Some languages provide {strong typing}, others allow {implicit
	type conversion} and/or {explicit type conversion}.

	(2003-12-22)

with a 'normal' keyboard. now, for the
chinese, japanese, etc. people out there...well, you should get the point.
hell, even this plain english account is valid:

"oops, there's spaces and commas and shit"@xxxxxxxxxxx

get the picture, cupcake?

And I think I will never see.

good for you. glad you feel that way. that does not change the fact that
email rfc standards define and allow for it.

Not all what allowed by RFC

<standard> (RFC) One of a series, begun in 1969, of numbered
	{Internet} informational documents and {standards} widely
	followed by commercial software and {freeware} in the
	{Internet} and {Unix} communities.  Few RFCs are standards but
	all Internet standards are recorded in RFCs.  Perhaps the
	single most influential RFC has been {RFC 822}, the Internet
	{electronic mail} format standard.

	The RFCs are unusual in that they are floated by technical
	experts acting on their own initiative and reviewed by the
	Internet at large, rather than formally promulgated through an
	institution such as {ANSI}.  For this reason, they remain
	known as RFCs even once adopted as standards.

	The RFC tradition of pragmatic, experience-driven,
	after-the-fact standard writing done by individuals or small
	working groups has important advantages over the more formal,
	committee-driven process typical of {ANSI} or {ISO}.

	Emblematic of some of these advantages is the existence of a
	flourishing tradition of "joke" RFCs; usually at least one a
	year is published, usually on April 1st.  Well-known joke RFCs
	have included 527 ("ARPAWOCKY", R. Merryman, UCSD; 22 June
	1973), 748 ("Telnet Randomly-Lose Option", Mark R. Crispin; 1
	April 1978), and 1149 ("A Standard for the Transmission of IP
	Datagrams on Avian Carriers", D. Waitzman, BBN STC; 1 April
	1990).  The first was a Lewis Carroll pastiche; the second a
	parody of the {TCP/IP} documentation style, and the third a
	deadpan skewering of standards-document legalese, describing
	protocols for transmitting Internet data packets by carrier
	pigeon.

	The RFCs are most remarkable for how well they work - they
	manage to have neither the ambiguities that are usually rife
	in informal specifications, nor the committee-perpetrated
	{misfeatures} that often haunt formal standards, and they
	define a network that has grown to truly worldwide
	proportions.

	{rfc.net (http://www.rfc.net/)}.
	{W3
	(http://www.w3.org/hypertext/DataSources/Archives/RFC_sites.html)}.
	{JANET UK FTP (ftp://nic.ja.net/pub/newsfiles/JIPS/rfc)}.
	{Imperial College, UK FTP (ftp://src.doc.ic.ac.uk/rfc/)}.
	{Nexor UK (http://www.nexor.com/public/rfc/index/rfc.html)}.
	{Ohio State U
	(http://www.cis.ohio-state.edu/hypertext/faq/usenet/top.html)}.

	See also {For Your Information}, {STD}.

	(1997-11-10)

is acceptable by real

1. Not simulated.  Often used as a specific antonym to
	{virtual} in any of its jargon senses.

	2. <mathematics> {real number}.

	[{Jargon File}]

	(1997-03-12)

ISP

1. {Internet Service Provider}.

	2. {Instruction Set Processor}.

's.

uhmmmm...'real' isp? hmmmm, what'd a 'fake' isp look like I wonder?
maybe like the sprint commercials where 'the other guy's network' is a bunch
of propped up pictures of people. can you hear me now? ROFLMAO!

ok, nimrod...why not quantify and qualify that statement so no one here
thinks you're just talking outta your ass.

which isp doesn't support

After-sale handholding; something many software vendors
	promise but few deliver.  To hackers, most support people are
	useless - because by the time a hacker calls support he or she
	will usually know the software and the relevant manuals better
	than the support people (sadly, this is *not* a joke or
	exaggeration).  A hacker's idea of "support" is a tte--tte
	or exchange of {electronic mail} with the software's designer.

	[{Jargon File}]

	(1995-02-15)

which rfc standard(s)?

since you have not even READ ONE SINGLE email rfc, I doubt you can back
yourself up...save, to backpeddle.

Typical rules I see around the world:
(?i)^[a-z][0-9a-z]*(?:[\.\-\_][0-9a-z]+)*$

that's because you're viewing the world through your ass. RTFM.

Sincerely Yours,

i do not want you...unless returning you means I can get a refund!

run along now.

From: Michael Fesser

Date: Thursday, October 25, 2007

.oO(AnrDaemon)

Greetings, Steve.
In reply to Your message dated Wednesday, October 24, 2007, 21:34:41,
S> the rfc's allow for 'illegal' characters in account names as long as they're
S> encapsulated. this is to compensate for non-latin character sets
S> (particularly, non-english sets). is that ringing a bell?
Never saw any in 10 years. And I think I will never see.
Not all what allowed by RFC is acceptable by real ISP's.

It's also not acceptable to improperly mark quoted lines in a reply,
because it makes the postings very hard to read. The Usenet

<messaging> /yoos'net/ or /yooz'net/ (Or "Usenet news", from
	"Users' Network") A distributed {bulletin board} system and
	the people who post and read articles thereon.  Originally
	implemented in 1979 - 1980 by Steve Bellovin, Jim Ellis, Tom
	Truscott, and Steve Daniel at Duke University, and supported
	mainly by {Unix} machines, it swiftly grew to become
	international in scope and, before the advent of the
	{World-Wide Web}, probably the largest decentralised
	information utility in existence.

	Usenet encompasses government agencies, universities, high
	schools, businesses of all sizes, and home computers of all
	descriptions.  In the beginning, not all Usenet hosts were on
	the Internet.  As of early 1993, it hosted over 1200
	{newsgroups} ("groups" for short) and an average of 40
	megabytes (the equivalent of several thousand paper pages) of
	new technical articles, news, discussion, chatter, and
	{flamage} every day.  By November 1999, the number of groups
	had grown to over 37,000.

	To join in you originally needed a {news reader} program but
	there are now several web gateways such as {Deja
	(http://www.deja.com/)}.  Several {web browsers} include news
	readers and {URLs} beginning "news:" refer to Usenet
	newsgroups.

	{Network News Transfer Protocol} is a {protocol} used to
	transfer news articles between a news {server} and a {news
	reader}.  The {uucp} {protocol} was sometimes used to transfer
	articles between servers, though this is probably rare now
	that most sites are on the {Internet}.

	{Stanford University} runs a service to send news articles by
	{electronic mail}.  Send electronic mail to
	<netnews@db.stanford.edu> with "help" in the message body.
	[Still?  URL?]

	{(http://www.openmarket.com/info/internet-index/current-sources.html)}.

	{Notes on news
	(http://www.ifi.uio.no/~larsi/notes/notes.html)} by Lars Magne
	Ingebrigtsen <larsi@ifi.uio.no>.

	[Gene Spafford <spaf@cs.purdue.edu>, "What is Usenet?",
	regular posting to {news:news.announce.newusers}].

	(1999-12-17)

way is a
single '>', so please adjust your newsreader. I think I have already
mentioned that.

Micha

From: Steve

Date: Thursday, October 25, 2007

.oO(AnrDaemon)
Greetings, Steve.
In reply to Your message dated Wednesday, October 24, 2007, 21:34:41,

S> the rfc's allow for 'illegal' characters in account names as long as
they're
S> encapsulated. this is to compensate for non-latin character sets
S> (particularly, non-english sets). is that ringing a bell?

Never saw any in 10 years. And I think I will never see.
Not all what allowed by RFC is acceptable by real ISP's.
It's also not acceptable to improperly mark quoted lines in a reply,
because it makes the postings very hard to read. The Usenet way is a
single '>', so please adjust your newsreader. I think I have already
mentioned that.

i have been biting my tongue on that one so I could stay on topic with the
regex. thanks for pointing that out.

cheers.

From: Michael Fesser

Date: Thursday, October 25, 2007

.oO(Steve)

wrote in message

It's also not acceptable to improperly mark quoted lines in a reply,
because it makes the postings very hard to read. The Usenet way is a
single '>', so please adjust your newsreader. I think I have already
mentioned that.
i have been biting my tongue on that one so I could stay on topic with the
regex. thanks for pointing that out.

I've bitten my tongue too often. ;-)

Micha

From: Steve

Date: Thursday, October 25, 2007

.oO(Steve)
wrote in message
It's also not acceptable to improperly mark quoted lines in a reply,
because it makes the postings very hard to read. The Usenet way is a
single '>', so please adjust your newsreader. I think I have already
mentioned that.

i have been biting my tongue on that one so I could stay on topic with the
regex. thanks for pointing that out.
I have bitten my tongue too often. ;-)

i actually used to use a non-standard delimiter

<character> A {character} or {string} used to separate, or
	mark the start and end of, items of data in, e.g., a
	{database}, {source code}, or {text file}.

	See also: {record}.

	(2001-03-16)

b/c it made things more
readable in my newsreader. after you quite nicely asked if i'd change it for
the benefit of all, we've the end result.
I think you can give yourself a break

1. To cause to be {broken} (in any sense).  "Your latest patch
	to the editor broke the paragraph commands."

	2. (Of a program) To stop temporarily, so that it may
	debugged.  The place where it stops is a "{breakpoint}".

	3. To send an {EIA-232} break (two character widths of line
	high) over a {serial line}.

	4. [Unix] To strike whatever key currently causes the tty
	driver to send SIGINT to the current process.  Normally,
	break, delete or {control-C} does this.

	5. "break break" may be said to interrupt a conversation (this
	is an example of verb doubling).  This usage comes from radio
	communications, which in turn probably came from landline
	telegraph/teleprinter usage, as badly abused in the Citizen's
	Band craze a few years ago.

	6. {pipeline break}.

	7. {break statement}.

	[{Jargon File}]

	(2004-03-24)

on this subject

<programming> In {subject-oriented programming}, a subject is
	a collection of {classes} or class fragments whose {class
	hierarchy} models its domain in its own, subjective way.  A
	subject may be a complete application in itself, or it may be
	an incomplete fragment that must be composed with other
	subjects to produce a complete application.  Subject
	composition combines class hierarchies to produce new subjects
	that incorporate functionality from existing subjects.

	(1999-08-31)

- your tongue anyway.
:)

From: Michael Fesser

Date: Thursday, October 25, 2007

.oO(Steve)

wrote in message

I have bitten my tongue too often. ;-) I actually used to use a non-standard delimiter b/c it made things more
readable in my newsreader. after you quite nicely asked if i'd change it for
the benefit of all, we've the end result.

I can remember.

i think you can give yourself a break on this subject - your tongue anyway.

;-)

I know about different kinds of delimiters. Some are quite common in
chatrooms and I have also used some of them years ago, but today most
newsreaders are programmed for '>' at the beginning of a line. That's
what makes a quote, like '-- ' makes a signature. It's just a common,
non-written standard, that helps to make Usenet a better place.

But this is _really_ OT here, so EOT.

Micha

Next Message: include ('url') VS readfile('url')

Blogs related to Regex help for email

Flash
... flash recent spear flash kombat mortal movie flash hilton paris pussy canon flash s3 8 flash professional tutorial flash email marketing flash grandmaster message free downloadable flash game book flash guest php tutorial flash free ...

Respect can only be earned and not acirc asked for acirc.
low interest credit cards for bankruptcy filers sportsbook with american express credit card bank of america business hours auto parts la paz email virus php php email virus web hosting reseller account maryland bankruptcy recordsbox 0 ...

We called them on the radio, in english, no response.
top 1000 banks bad credit auto loan refinance air canada flight schedule may 14 2007 scream at the beach bmw motorcycle part accessory accounting business canada small software php how to use outlook exress with aol email account ...

Flash
... 6 adobe download flash player atlanta flash designer canon flash sigma celtic tattoo flash art new sex flash game beach flash kingston 1 gb flash drive animation creation flash gex designer flash site web drive flash partition usb ...

Flash
... disney flash 1gb compact flash flash kicker video christmas flash tree standalone flash player making flash cartoon click flash free game point scary flash download flash free menu animation creation flash gex flash sound effects ...

Flash
... sexy funny flash animation creation flash gex flash game horse online racing 8 flash free player 2gb card digital flash memory sandisk secure flash macromedia player.com anatomy barrons card flash flash disposable camera animation ...