johndoe@gmail.com
john.doe@gmail.com
j.o.h.n.d.o.e@gmail.com
johndoe+spam@gmail.com
john....doe+spam@gmail.com
but johndoe.spam@gmail.com wouldn't go to the same mailbox.But sure, you could have `(my name is)john."..".doe+spam(...)@gmail.com` if you wanted to. Syntactically valid! The parenthesised bits would be stripped out before sending, and I have no idea whether Gmail would be willing to accept the quoted dots bit.
As for parens, I recollect the spec lets you nest your parens and quotes! It's insane. e.g. `f(oo."(bar."baz")."quux)@example.com` is valid in the spec.
I wrote an Oracle regex to parse for valid email addresses and I went against the spec rather than what is what's practically used. It was an insane thing.
For example: foobar@ foo.bar@ f.o.o.b.a.r@ are all valid and normalize the case without the periods.
bar.foo@gmail.com
gets rejected as email address doesn't exist when my gmail is bar@gmail.com
So if you wanted to use it like this you would try something like b.ar@gmail.com