On 24/10/2014 5:58 AM, mozilla-lists.mbou...@spamgourmet.com wrote:
Daniel wrote:
Using my Linux SM 2.30, I just noticed that this address corruption is
still occurring, at least for addresses that have @ as part of the
Name field, e.g. I have a spam reporting address
1-Spam @ ACMA
Daniel wrote:
Using my Linux SM 2.30, I just noticed that this address corruption is
still occurring, at least for addresses that have @ as part of the
Name field, e.g. I have a spam reporting address
1-Spam @ ACMArep...@submit.spam.acma.gov.au
If I select it, as an address that I wish
On 10/10/14 05:35, Paul B. Gallagher wrote:
Snip
Thus, it is not a feasible option with this program to use quotation
marks to delineate such a display name -- unless they must be entered
with some escape character such as a backslash. I did try this:
\Paul @ Gallagher\
as my display name,
On 15/10/14 10:46, Neil wrote:
Daniel wrote:
So Paul, it would seem that I can confirm your problem with SM 2.29
*on Win7* at least.
If it's a difference between 2.26.1 and 2.29 then the most likely cause
is bug 858337, but that's just a wild guess.
Neil, it may not be a difference between
On 13/10/14 23:35, Paul B. Gallagher wrote:
Daniel wrote:
On 13/10/2014 9:35 PM, Daniel wrote:
On 13/10/2014 9:19 PM, Daniel wrote:
On 12/10/2014 7:35 PM, Daniel wrote:
On 11/10/14 20:26, Paul B. Gallagher wrote:
Daniel wrote:
On 11/10/14 19:09, Paul B. Gallagher wrote:
Snip
In the
Daniel wrote:
So Paul, it would seem that I can confirm your problem with SM 2.29
*on Win7* at least.
If it's a difference between 2.26.1 and 2.29 then the most likely cause
is bug 858337, but that's just a wild guess.
--
Warning: May contain traces of nuts.
On 12/10/2014 7:35 PM, Daniel wrote:
On 11/10/14 20:26, Paul B. Gallagher wrote:
Daniel wrote:
On 11/10/14 19:09, Paul B. Gallagher wrote:
Snip
In the composition window, as we have seen, if I manually enter
Paul @ Gallagher mypre...@mydomain.com
SeaMonkey overrides the punctuation and
On 13/10/2014 9:19 PM, Daniel wrote:
On 12/10/2014 7:35 PM, Daniel wrote:
On 11/10/14 20:26, Paul B. Gallagher wrote:
Daniel wrote:
On 11/10/14 19:09, Paul B. Gallagher wrote:
Snip
In the composition window, as we have seen, if I manually enter
Paul @ Gallagher mypre...@mydomain.com
On 13/10/2014 9:35 PM, Daniel wrote:
On 13/10/2014 9:19 PM, Daniel wrote:
On 12/10/2014 7:35 PM, Daniel wrote:
On 11/10/14 20:26, Paul B. Gallagher wrote:
Daniel wrote:
On 11/10/14 19:09, Paul B. Gallagher wrote:
Snip
In the composition window, as we have seen, if I manually enter
Daniel wrote:
On 13/10/2014 9:35 PM, Daniel wrote:
On 13/10/2014 9:19 PM, Daniel wrote:
On 12/10/2014 7:35 PM, Daniel wrote:
On 11/10/14 20:26, Paul B. Gallagher wrote:
Daniel wrote:
On 11/10/14 19:09, Paul B. Gallagher wrote:
Snip
In the composition window, as we have seen, if I
On 11/10/14 20:26, Paul B. Gallagher wrote:
Daniel wrote:
On 11/10/14 19:09, Paul B. Gallagher wrote:
Snip
In the composition window, as we have seen, if I manually enter
Paul @ Gallagher mypre...@mydomain.com
SeaMonkey overrides the punctuation and attempts to send to
David E. Ross wrote:
In my tests, the @ character was bracketed by a blank space on each
side. I then repeated the tests without blank spaces bracketing the
@.
...
Have you tried your cases in SeaMonkey's Safe Mode? I will redo my
tests in Thunderbird's Safe Mode later today, after I tend my
On 11/10/14 19:09, Paul B. Gallagher wrote:
Snip
In the composition window, as we have seen, if I manually enter
Paul @ Gallagher mypre...@mydomain.com
SeaMonkey overrides the punctuation and attempts to send to
Paul@Gallaghermyprefix@mydomain.com
which fails.
As explained elsewhere
On 11/10/14 19:45, Daniel wrote:
On 11/10/14 19:09, Paul B. Gallagher wrote:
Snip
Maybe the problem is when an e-mail is received *and then* the @ is
added to the address line, so initial send is o.k., but reply/return
causes problems!!
But, then again, *NO*, because that's what I'm doing,
Daniel wrote:
On 11/10/14 19:09, Paul B. Gallagher wrote:
Snip
In the composition window, as we have seen, if I manually enter
Paul @ Gallagher mypre...@mydomain.com
SeaMonkey overrides the punctuation and attempts to send to
Paul@Gallaghermyprefix@mydomain.com
which fails.
As
On 10/11/2014 1:09 AM, Paul B. Gallagher wrote:
David E. Ross wrote:
In my tests, the @ character was bracketed by a blank space on each
side. I then repeated the tests without blank spaces bracketing the
@.
...
Have you tried your cases in SeaMonkey's Safe Mode? I will redo my
tests
A colleague wrote to me from the email
Personal Name @ Gmail personal.n...@gmail.com
which was misinterpreted by SeaMonkey as
\Personal Name\@Gmailpersonal.name@gmail.com
which Google read as
Personal n...@gmailpersonal.name@gmail.com
and of course that bounced.
Obviously, I've
@ is not allowed in that context; she should have declared herself as
Personal Name @ Gmail personal.n...@gmail.com
Philip Taylor
Paul B. Gallagher wrote:
A colleague wrote to me from the email
Personal Name @ Gmail personal.n...@gmail.com
which was misinterpreted by
On 09/10/14 17:30, Philip Taylor wrote:
@ is not allowed in that context; she should have declared herself as
Personal Name @ Gmail personal.n...@gmail.com
Philip Taylor
Paul B. Gallagher wrote:
A colleague wrote to me from the email
Personal Name @ Gmail
On 10/8/2014 11:15 PM, Paul B. Gallagher wrote:
A colleague wrote to me from the email
Personal Name @ Gmail personal.n...@gmail.com
which was misinterpreted by SeaMonkey as
\Personal Name\@Gmailpersonal.name@gmail.com
which Google read as
Personal
David E. Ross wrote:
RFC 5322 requires that your
Personal Name @ Gmail personal.n...@gmail.com
instead be
Personal Name @ Gmail personal.n...@gmail.com.
The quotes are required because the display name (Personal Name @
Gmail) contains the restricted character @ (special
On 10/9/2014 8:02 AM, David E. Ross wrote:
On 10/8/2014 11:15 PM, Paul B. Gallagher wrote:
A colleague wrote to me from the email
Personal Name @ Gmail personal.n...@gmail.com
which was misinterpreted by SeaMonkey as
\Personal Name\@Gmailpersonal.name@gmail.com
which Google read as
David E. Ross wrote:
RFC 5322 requires that your
Personal Name @ Gmail personal.n...@gmail.com
instead be
Personal Name @ Gmail personal.n...@gmail.com.
The quotes are required because the display name (Personal Name @ Gmail)
contains the restricted character @ (special
On 10/9/2014 11:35 AM, Paul B. Gallagher wrote:
David E. Ross wrote:
RFC 5322 requires that your
Personal Name @ Gmail personal.n...@gmail.com
instead be
Personal Name @ Gmail personal.n...@gmail.com.
The quotes are required because the display name (Personal Name @ Gmail)
David E. Ross wrote:
In my tests, the @ character was bracketed by a blank space on each
side.
Mine, too, as you've seen.
I then repeated the tests without blank spaces bracketing the @.
Interesting, I haven't tried that.
I sent the messages to my daughter but used Send Later so that
On 10/9/2014 12:17 PM, David E. Ross wrote:
On 10/9/2014 11:35 AM, Paul B. Gallagher wrote:
David E. Ross wrote:
RFC 5322 requires that your
Personal Name @ Gmail personal.n...@gmail.com
instead be
Personal Name @ Gmail personal.n...@gmail.com.
The quotes are required because the
26 matches
Mail list logo
