From 79d4c6fd0708d70861e1083c1a2cc41ba3a1a23b Mon Sep 17 00:00:00 2001 From: Winni Neessen Date: Mon, 11 Nov 2024 20:06:47 +0100 Subject: [PATCH] Correct spelling errors in email validation comments Fixed the spelling of "dot-separated" in comment explanations to ensure clarity. This makes the comments more accurate and easier to understand. --- msg_test.go | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/msg_test.go b/msg_test.go index 117e8e7..ce98447 100644 --- a/msg_test.go +++ b/msg_test.go @@ -126,8 +126,8 @@ var ( {`" "@domain.tld`, true}, // Still valid, since quoted {`"<\"@\".!#%$@domain.tld"`, false}, // Quoting with illegal characters is not allowed {`<\"@\\".!#%$@domain.tld`, false}, // Still a bunch of random illegal characters - {`hi"@"there@domain.tld`, false}, // Quotes must be dot-seperated - {`"<\"@\\".!.#%$@domain.tld`, false}, // Quote is escaped and dot-seperated which would be RFC822 compliant, but not RFC5322 compliant + {`hi"@"there@domain.tld`, false}, // Quotes must be dot-separated + {`"<\"@\\".!.#%$@domain.tld`, false}, // Quote is escaped and dot-separated which would be RFC822 compliant, but not RFC5322 compliant {`hi\ there@domain.tld`, false}, // Spaces must be quoted {"hello@tld", true}, // TLD is enough {`你好@域名.顶级域名`, true}, // We speak RFC6532