Problem sending attachment w/ pm32 4.31/4.41
Hakubi
resolve... It seems that whenever I send an email with an attachment,
Pegasus will fail to send it. I don't send attachments often so I don't
know exactly when this problem began. I've had it with 4.31 and 4.41 and
also tested with Comcast's and my own email server running Mercury.
I've verified my settings, and sent test mails to my various other email
accounts. Any email I send with no attachment goes through. If I add an
attachment, Pegasus will authenticate with the email server but then
send no data. This happens whether I have my firewall (Kerio 2.1.5)
running or disabled.
I tried uninstalling/reinstalling Pegasus. No dice with that.
I tried uninstalling, and deleting the old Pmail folder before
reinstalling (backing up first of course). No dice.
I couldn't find anything in the knowledge base about it.
I tested sending with/without attachments in Mozilla mailnews, and it
works fine there.
Anyone have an idea? I can make screenshots available, if need be.
Bernard Mercier
It would help if you described more precisely what happens and also publish a
tcp trace.
--
<a href="http://users.kbc.skynet.be/fi001005">Belgische Ardennen Belges</a>
Hakubi
> It would help if you described more precisely what happens and also publish a
> tcp trace.
>
Pegasus will sit at Sending mail 0% until the timeout period elapses,
then gives me this:
[*] Connection established to 204.127.192.17
>> 0060 220 comcast.net - Maillennium ESMTP/MULTIBOX rwcrmhc15 #30
<< 0020 EHLO [192.168.1.5]
>> 0017 250-comcast.net
>> 0010 250-7BIT
>> 0014 250-8BITMIME
>> 0031 250-AUTH CRAM-MD5 LOGIN PLAIN
>> 0009 250-DSN
>> 0010 250-HELP
>> 0010 250-NOOP
>> 0016 250-PIPELINING
>> 0019 250-SIZE 15728640
>> 0014 250-STARTTLS
>> 0020 250-VERS V05.00c++
>> 0012 250 XMVP 2
<< 0045 MAIL FROM:<[obscured]@comcast.net> SIZE=30914
>> 0008 250 ok
<< 0028 RCPT TO:<[obscured]@gmail.com>
>> 0048 250 ok; [simple] forward to <[obscured]@gmail.com>
<< 0006 DATA
>> 0008 354 ok
The problem seems to be isolated to this particular computer. I have
Pegasus installed on one of my other computers, and it sends attachments
just fine.
Being that Pegasus is portable and the drive letters match, I deleted
the \PMAIL directory on my computer, and copied over the working one. It
failed as well, pointing the finger at something on this computer
breaking it.
I enabled session logs and found this at the end of the attachment block:
17:25:58.515 9: Socket write error 2746.
17:26:07.718 << 0006 QUIT\0D\0A
17:26:07.718 9: Socket write error 2746
Nil
news:i42dnRov0bCJ3VTZ...@comcast.com:
> Pegasus will sit at Sending mail 0% until the timeout period
> elapses, then gives me this:
This sounds like a problem I've heard of running Pegasus on computers
that use certain motherboards. Here's a description of one such
situation:
"In particular, it was an Gigabyte motherboard which used an NVidia
NForce 4 chipset which has a built in NIC (i.e. netword interface
card). This particular ethernet card has a series of "advanced"
optimizations which are turned on in the driver.
In my case, disabling the advanced optimization capability called
"checksum offload" made all my problems of sending smtp mail via
Pegasus disappear. I can reproduce them at will by re-enabling this
capability."
The setting should be found in the computer BIOS setup.
There's another possible solution having to do with changing the MTU
for the network interface, accomplished by editing the registry. But
consider the first solution first.
Hakubi
AH! That did it! The setting looked familiar, and I checked in the
driver settings - sure enough it was there, and enabled. Disabled it,
and now sending works just fine. I have an ECS mobo, with an NForce
chipset. Mine is an NForce 3 250, according to the manual.
Thanks, I knew I'd find someone here who'd seen this before.
Nil
> AH! That did it! The setting looked familiar, and I checked in the
> driver settings - sure enough it was there, and enabled. Disabled
> it, and now sending works just fine. I have an ECS mobo, with an
> NForce chipset. Mine is an NForce 3 250, according to the manual.
Great! I guess there are lots of that chipset out there, because this
problem crops up fairly often. I can't imagine how anyone was ever able
to discover the workaround.
Bernard Mercier
Glad you found a solution.
So you see it's important to give precise info when a problem arises.
Adolph B. Amster
I have the same problem but I wouldn't know how to find our what
motherboard I have, nor how to disable the "checksum offload". Any
suggestions woulld be most helpful. I'm using Windows XP with 1 gb of
memory.
Thank you.
Greg R. Broderick
$.1obrtzfs3sxpj$.d...@40tude.net:
> I have the same problem but I wouldn't know how to find our what
> motherboard I have, nor how to disable the "checksum offload". Any
> suggestions woulld be most helpful. I'm using Windows XP with 1 gb of
> memory.
>
It will be on the properties page for either your network adapter or your
system board in WinXP's device manager administrative tool.
Cheers
GRB
--
---------------------------------------------------------------------
Greg R. Broderick gregb.use...@blackholio.dyndns.org
A. Top posters.
Q. What is the most annoying thing on Usenet?
---------------------------------------------------------------------
Adolph B. Amster
> "Adolph B. Amster" <do...@mchsi.com> wrote in news:11bx2mr5l4svu
> $.1obrtzfs3sxpj$.d...@40tude.net:
>
>> I have the same problem but I wouldn't know how to find our what
>> motherboard I have, nor how to disable the "checksum offload". Any
>> suggestions woulld be most helpful. I'm using Windows XP with 1 gb of
>> memory.
>>
>
> It will be on the properties page for either your network adapter or your
> system board in WinXP's device manager administrative tool.
>
> Cheers
> GRB
Thank you.