Two more gmail / eudora mac questions
jemple
the gmail server.
Two new ones. Again, Eudora 5.2 with OS 9.2.
1. When I download messages using Eudora, because of the "conversation"
format of gmail, it downloads even message I've sent. I'd like to only
download incoming messages. Is this configurable? I guess I could
always set up a filter and toss downloaded messages that were originally
sent by me.
2. When I'm sending from Eudora, I get a TCP/IP error after the gmail
messages (my "dominant" personality) are sent. The messages all go
okay, but immediately after the last message is sent, I get an error:
"TCP/IP error -3162. The server is not responding. (37:590). From
what I've read, this suggests an error on the gmail side. I've used
this Eudora for a long time, to retrieve and send messages from multiple
servers and ISPs, and have never seen this come up. Happens 100% of the
time I'm sending using Eudora and my dominant gmail personality. Again,
the messages actually DO get sent, but the error I get is annoying. Any
suggestions on how to stop it.
Thanks.
Bill Cole
jemple <n...@ooo.way> wrote:
> Thanks to all who answered my earlier question about leaving messages on
> the gmail server.
>
> Two new ones. Again, Eudora 5.2 with OS 9.2.
>
> 1. When I download messages using Eudora, because of the "conversation"
> format of gmail, it downloads even message I've sent. I'd like to only
> download incoming messages. Is this configurable? I guess I could
> always set up a filter and toss downloaded messages that were originally
> sent by me.
That's a question for Google.
> 2. When I'm sending from Eudora, I get a TCP/IP error after the gmail
> messages (my "dominant" personality) are sent. The messages all go
> okay, but immediately after the last message is sent, I get an error:
> "TCP/IP error -3162. The server is not responding. (37:590). From
> what I've read, this suggests an error on the gmail side. I've used
> this Eudora for a long time, to retrieve and send messages from multiple
> servers and ISPs, and have never seen this come up. Happens 100% of the
> time I'm sending using Eudora and my dominant gmail personality. Again,
> the messages actually DO get sent, but the error I get is annoying. Any
> suggestions on how to stop it.
I think the short answer is that you'll have to live with it.
It may actually be an error in how Eudora is interpreting technically
acceptable behavior OR how the MacOS network stack is showing that to
Eudora. It looks to me like Google is pushing its 'FIN' packet
(TCP-level close of its half of the session) right behind the
SMTP-level acknowledgment of the QUIT verb, rather than waiting for the
client side to initiate the TCP close. That's not wrong, but it could
result in a client seeing the closure before reading the QUIT
acknowledgment.
--
Now where did I hide that website...
John H Meyers
> Two new ones. Again, Eudora 5.2 with OS 9.2.
>
> When I download messages using Eudora, because of the "conversation"
> format of gmail, it downloads even message I've sent. I'd like
> to only download incoming messages. Is this configurable?
Not at Gmail's end, AFAIK.
> I guess I could always set up a filter and toss downloaded messages
> that were originally sent by me.
Yep, but see below for another possibility.
> When I'm sending from Eudora, I get a TCP/IP error after the gmail
> messages (my "dominant" personality) are sent. The messages all go
> okay, but immediately after the last message is sent, I get an error:
> "TCP/IP error -3162. The server is not responding. (37:590). From
> what I've read, this suggests an error on the gmail side.
> The messages actually DO get sent, but the error I get is annoying.
> Any suggestions on how to stop it.
Run Windows on your Mac, and use Eudora 7.1 for Windows :)
This is actually true,
per this quote from Windows Eudora 7.1 Release Notes:
Added a new hidden setting, <x-Eudora-option:IgnoreSMTPQUITErrors>,
which allows errors in response to a QUIT command of an SMTP session
to be ignored. The default value is on (1). This is helpful
for SMTP servers like GMail's, which do a hard close on the socket
after sending the response to the QUIT command
and thus make it appear to have errors.
This Gmail SMTP behavior
is exactly what Bill Cole also directly observed and reported.
Since local ISPs provide their own SMTP servers,
it is never actually necessary to use Gmail's SMTP server,
just as you don't have to go to the specific Post Office
where you receive letters -- you can drop outgoing letters
in any drop box, anywhere that lets you use it,
and your local ISP lets all its customers use theirs,
even if you use Gmail for all your incoming email.
If you send outgoing mail through the local ISP,
Gmail normally doesn't receive a copy, and you thus
don't re-download a copy of what you've sent
when you POP from Gmail,
thus solving your other issue at the same time.
However, if you *want* Gmail to keep copies of your "sent" mail,
then you would have to "Bcc:" to yourself at Gmail,
which can even be automated via Eudora default stationery
(and then you *would* get those back via POP,
but of course you can filter those if you want);
experiment to see whatever impact this has on "conversations."
--
Daniel Cohen
> Since local ISPs provide their own SMTP servers,
> it is never actually necessary to use Gmail's SMTP server,
I have found that from time to time my ISP gets regarded as a spammer.
It's the nonsense overkill of some of the anti-spam programs used by
ISPs, which classify a whole ISP as a spammer if one of their users
sends spam. It gets cleared after a day or so, but is still
inconvenient.
That's one of the main reasons I have a gmail account, as I can send via
their SMTP server.
--
http://www.decohen.com
Send e-mail to the Reply-To address;
mail to the From address is never read
Bill Cole
"John H Meyers" <jhme...@nomail.invalid> wrote:
> On Fri, 04 May 2007 17:39:38 -0500, jemple wrote:
>
> > Two new ones. Again, Eudora 5.2 with OS 9.2.
> >
> > When I download messages using Eudora, because of the "conversation"
> > format of gmail, it downloads even message I've sent. I'd like
> > to only download incoming messages. Is this configurable?
>
> Not at Gmail's end, AFAIK.
>
> > I guess I could always set up a filter and toss downloaded messages
> > that were originally sent by me.
>
> Yep, but see below for another possibility.
>
> > When I'm sending from Eudora, I get a TCP/IP error after the gmail
> > messages (my "dominant" personality) are sent. The messages all go
> > okay, but immediately after the last message is sent, I get an error:
> > "TCP/IP error -3162. The server is not responding. (37:590). From
> > what I've read, this suggests an error on the gmail side.
> > The messages actually DO get sent, but the error I get is annoying.
> > Any suggestions on how to stop it.
>
> Run Windows on your Mac, and use Eudora 7.1 for Windows :)
Not an option for anyone currently running 9.2. Intel Macs will not even
run Classic, much less raw 9.2, and there is no such thing as Windows
for a PPC Mac.
[...]
>
> Since local ISPs provide their own SMTP servers,
> it is never actually necessary to use Gmail's SMTP server,
> just as you don't have to go to the specific Post Office
> where you receive letters -- you can drop outgoing letters
> in any drop box, anywhere that lets you use it,
> and your local ISP lets all its customers use theirs,
> even if you use Gmail for all your incoming email.
That's not quite true. There are edge cases.
There are ISP's who do not allow their customers to relay mail using
arbitrary addresses, but instead require that the SMTP envelope sender
and/or the From header are valid 'local' (i.e. belonging to that ISP)
addresses.
There are connection environments (e.g. motels, public wi-fi, etc.)
where the connection provider offers no mail relay service AND blocks
port 25 outbound. Sending mail in such environments requires either some
sort of VPN tunneling or the use of a submission-only (port 587) service
like GMail.
There are some mail systems which use dubious forgery detection
techniques in the name of spam control that will be highly suspicious of
mail with a gmail.com address arriving from somerandomisp.net. possibly
to the point of dropping or rejecting that mail which they might have
accepted and delivered if it came through the 'normal' GMail system.