Has anyone experience problems with sending mail through gmail account (through smtp)?
When I try to send, I get an error trace: "2: Bad address "smtp.gmail.com "."
I have set-up the pop and smtp servers correctly (to the best of my knowledge). There are no issues with ports being disabled, since I can send and receive mail from the same computer and same address via outlook express.
It seems that it is the Pegasus settings that I got wrong, or, perhaps Pegasus cannot work with Google servers?
Here are the settings I tried in Pegasus:
server: smtp.gmail.com
TCP/IP port: 465 (I tried 567 too)
"Log in to SMTP server using POP3 settings" and "Via direct SSL connect" settings are on.
Any help is greatly appreciated.
Thanks in advance!
Here's the GMail setting and they work for me with both MercuryC and WinPMail. Your error though looks like a timeout and I do use a timeout of 300 seconds when going to GMail. You might also check to ensure that your firewall or anything else like anti-virus/spam crud that you are running between WinPmail and the GMail server is not blocking.
(a) -POP3-
Server host name: pop.gmail.com
User name: <your_user_name>@gmail.com
Password: <your_password>
Server TCP/IP port: 995
SSL/TLS: via direct SSL connect
Enable server certificate fingerprint tracking: checked
(b) -SMTP STARTTLS -
Server host name: smtp.gmail.com
Server TCP/IP port: 587
SSL/TLS: via STARTTLS
Enable server certificate fingerprint tracking: checked
SMTP Authentication: Login to the SMTP server using POP3
username/password (the GMAIL-POP3-definition has been chosen)
(c) - SMTP via SSL -
Server host name: smtp.gmail.com
Server TCP/IP port: 465
SSL/TLS: via direct ssl connection
Enable server certificate fingerprint tracking: unchecked
SMTP Authentication: Login to the SMTP server using POP3
username/password (the GMAIL-POP3-definition has been chosen)
(d) - IMAP4 via SSL -
Server host name: imap.gmail.com
User name: <your_user_name>@gmail.com
Password: <your_password>
Server TCP/IP port: 993
SSL/TLS: via direct SSL connect
Hello Thomas, thanks for quick reply. I tried these settings, but it doesn't help, unfortunatelly.
THere is no firewall running except the hardware one on the router :-) But if it would be a problem I expect it would also block access to smtp.gmail.com from OE.
The error happens very quickly, within a 2-3 seconds of hitting 'Send mail in queue', I doubt it's the timeout issue. I have tried increasing the timeout, but it doesn't make any difference.
I have found a posting on Gmail's forums where people could not send mail out, and one of the suggestions (which I actually needed to use, before I could send via my Gmail account from OE) was to check the 'My server requires authentication' for the outgoing server.
THere is no firewall running except the hardware one on the router :-)
But if it would be a problem I expect it would also block access to
smtp.gmail.com from OE.
Not necessarily is it can block by application.
The error happens very quickly, within a 2-3 seconds of hitting 'Send
mail in queue', I doubt it's the timeout issue. I have tried increasing
the timeout, but it doesn't make any difference.
Very quickly might mean that GMail is blocking but I doubt it since it's not even getting a response. When you cannot connect that means something between you and the server is blocking. Since OE can connect, that something is blocking WinPMail specifically. This is not a WinPMail problem. Remove the blocking and it works just fine.
I have found a posting on Gmail's forums where people could not send
mail out, and one of the suggestions (which I actually needed to use,
before I could send via my Gmail account from OE) was to check the 'My
server requires authentication' for the outgoing server.
You are not even getting that far. WinPMail is saying it cannot even make initial contact with the smtp.gmail.com host on the specified port. There is something you have not yet told us about your setup since this really looks like there is something running between WinPMail and the GMail host.
I confirmed with our sysadmin, there is no by application blocking at the router.
I tried setting up two other addresses: one on yandex.ru and one on bizmail.yahoo.com and there is same behaviour: can receive, cannot send. yandex.ru give a more detailed trace, and bizmail.yahoo.com returns the "bad address" error immidiatelly.
What could possibly be blocking PMail if I do not have firewall or antivirus running?
Here is the trace from yandex.ru:
[*] Connection established to 213.180.204.38
>> 0083 220 Yandex ESMTP (NO UCE)(NO UBE) server ready at Wed, 10 Sep 2008 01:48:17 +0400
<< 0021 EHLO [10.10.10.198]
>> 0079 250-smtp5.yandex.ru expected "EHLO cmr-208-97-89-163.cr.net.cable.rogers.com"
>> 0019 250-SIZE 20971520
>> 0014 250-8BITMIME
>> 0016 250-PIPELINING
>> 0014 250-CHUNKING
>> 0025 250-ENHANCEDSTATUSCODES
>> 0009 250-DSN
>> 0021 250-X-RCPTLIMIT 100
>> 0016 250-AUTH=LOGIN
>> 0016 250-AUTH LOGIN
>> 0014 250-STARTTLS
>> 0010 250 HELP
<< 0050 MAIL FROM:<*****@yandex.ru> SIZE=396
>> 0058 530 5.3.0 Sorry [208.97.89.163]; Authentication required
What could possibly be blocking PMail if I do not have firewall or antivirus running?
I have no idea but it not WinPMail. WinPMail just calls the winsock to do TCP/IP and if there is nothing between WinPmail and the server it will work. Do use use any anti-virus or anti-spam software?
>> 0016 250-AUTH=LOGIN
>> 0016 250-AUTH LOGIN
>> 0014 250-STARTTLS
>> 0010 250 HELP
<< 0050 MAIL FROM:<*****@yandex.ru> SIZE=396
>> 0058 530 5.3.0 Sorry [208.97.89.163]; Authentication required
This server requires ESMTP authorization using either LOGIN or AUTH=LOGIN. David Harris has implemented ESMTP AUTH CRAM-MD5 for WinPMail, Mercury and Mercury/32. They do a SMTP authentication in accordance with RFCs 2554 and 2195. They also do the LOGIN and the strange MS AUTH=LOGIN.
Go to File | Network configuration | (Sending) SMTP, edit the SMTP setup, select the "Security" tab and select one of the 3 options for doing SMTP Authorization.
This is an old thread, but I faced the same problem.
I'd made a change in my SMTP settings (server host name and port) following an update from my ISP, but following that I kept getting the 'bad address' error message.
I checked my Kaspersky firewall, and Pegasus had permissions. I checked too that the Port being sent to was in the list of ones that were monitored.
Still no further forward.
Then I >completely< overwrote the whole SMTP settings, checking each box again, and re-writing the boxes even though the original username and password etc. were still displayed and still correct.
Seems to have sorted the problem.
I am having the same issue on a Win10 laptop. Not a gmail account, though.
I will try re-entering all the addresses. And hope.
Lydia Hedge
Canada
