Source: http://support.google.com/mail/bin/answer.py?hl=en&answer=13287
Enjoy.

Use windows version, system say, and after this no reply from window…

Dec 16 13:46:42 osipov sendEmail[728]: DEBUG => Connecting to smtp.gmail.com:

Dec 16 13:46:42 osipov sendEmail[728]: DEBUG => My IP address is: 127.0.0.1

[Editorial note: I'm new to Linux/Ubuntu and hardly know what I'm doing. Back to my narrative...]

I was simply trying to send email to myself, such as to notify me of successful backups. It was my out-of-state ISP (the ISP that hosts my website and provides an email account for me and not the ISP for my DSL line, CenturyLink, whose smtp server didn’t work for me with port 465 and SSL either) that advised me to use port 465 for SSL. Strangely, I had no trouble at all with Thunderbird, the Mozilla email client, on the very same computer. It set up easily on port 465 with SSL/TLS and it works without any problems.

Throughout this struggle with sendemail I had ignored my out-of-state ISP’s advice for non-SSL transmissions, which was to get around the spam-avoidance practice of some ISPs (evidently Century Link too) of blocking port 25… by using port 2525 instead. So I tried it, without setting tls=yes.

Voila (and I hope that my French teachers--- may the ones that are gone rest in peace--- will forgive me for not knowing how to put the accent on the last letter)! Success.

Here’s what worked:

Sample:
sendEmail -f myusername@myveryowndomainname.com -t myusername@myveryowndomainname.com \
-u “this is the test email” -m “this is a test message” \
-s mail.myoutofstateISP.net:2525 \
-xu myusername[WITHOUTthe@myveryowndomainname.com] -xp mypassword \
-v -v

Somehow that averts the segmentation fault problem for me, but of course I have no idea why. Note that some ISPs, quite possibly gmail but I’m not sure, would have you put your entire email address with the @domain.com or whatever on the end of the -xu parameter. Not so at my particular out-of-state ISP.

Strangely the mail comes through with some hair on it, some vestiges of the quotes are draped around the body… but none around the subject. But I can live with that.

Thanks all, for your help.

Thanks in advance

grep CRON /var/log/syslog

CRON[6341]: (root) CMD (bash /usr/local/bin/backup.sh)
CRON[6340]: (CRON) info (No MTA installed, discarding output)

$ sendemail -f me -t them -m “message” -o tls=auto -s smtp.gmail.com:465 -xu myid -xp mypass -v
Jan 18 18:19:40 sendemail[10458]: DEBUG => Connecting to smtp.gmail.com:465
Jan 18 18:19:41 sendemail[10458]: DEBUG => My IP address is: 192.168.0.100
Segmentation fault

but everything is set correctly…………….

so what is wrong? thanx:)

but result was this error
sendEmail[2662]: ERROR => Received: 501 Command too short.

AUTH was successful… so what is wrong?

ERROR => Timeout while connecting to smtpa.fopsi.com:25 There was no response after 60 seconds.

my firewall is open [iptables -P OUTPUT ACCEPT], and smtpa.forpsi.com server is pingable without problems..

Any idea what can be wrong about it? Or about my hand..?

THX a lot

Seems AT&T just started blocking port 25 without allowing an open port!


May 28 16:11:43 myprivateserver sendEmail[29676]: DEBUG => Connecting to localhost:25
May 28 16:11:43 myprivateserver sendEmail[29676]: DEBUG => My IP address is: 127.0.0.1
May 28 16:11:43 myprivateserver sendEmail[29676]: DEBUG => evalSMTPresponse() - Found SMTP success code: 220
May 28 16:11:43 myprivateserver sendEmail[29676]: SUCCESS => Received: 220 myprivateserver.launchmodem.com ESMTP Exim 4.63 Thu, 28 May 2009 16:11:43 -0400
May 28 16:11:43 myprivateserver sendEmail[29676]: INFO => Sending: EHLO myprivateserver.launchmodem.com
May 28 16:11:43 myprivateserver sendEmail[29676]: DEBUG => evalSMTPresponse() - Found SMTP success code: 250
May 28 16:11:43 myprivateserver sendEmail[29676]: SUCCESS => Received: 250-myprivateserver.launchmodem.com Hello root at localhost [127.0.0.1], 250-SIZE 52428800, 250-PIPELINING, 250 HELP
May 28 16:11:43 myprivateserver sendEmail[29676]: DEBUG => The remote SMTP server does NOT support TLS
May 28 16:11:43 myprivateserver sendEmail[29676]: NOTICE => Authentication not supported by the remote SMTP server!
May 28 16:11:43 myprivateserver sendEmail[29676]: INFO => Sending: MAIL FROM:
May 28 16:11:43 myprivateserver sendEmail[29676]: DEBUG => evalSMTPresponse() - Found SMTP success code: 250
May 28 16:11:43 myprivateserver sendEmail[29676]: SUCCESS => Received: 250 OK
May 28 16:11:43 myprivateserver sendEmail[29676]: INFO => Sending: RCPT TO:
May 28 16:11:43 myprivateserver sendEmail[29676]: DEBUG => evalSMTPresponse() - Found SMTP success code: 250
May 28 16:11:43 myprivateserver sendEmail[29676]: SUCCESS => Received: 250 Accepted
May 28 16:11:43 myprivateserver sendEmail[29676]: INFO => Sending: DATA
May 28 16:11:43 myprivateserver sendEmail[29676]: DEBUG => evalSMTPresponse() - Found SMTP success code: 354
May 28 16:11:43 myprivateserver sendEmail[29676]: SUCCESS => Received: 354 Enter message, ending with "." on a line by itself
May 28 16:11:43 myprivateserver sendEmail[29676]: INFO => Sending message body
May 28 16:11:43 myprivateserver sendEmail[29676]: DEBUG => Sending the attachment [webFileCheckLog.txt]
May 28 16:11:43 myprivateserver sendEmail[29676]: DEBUG => evalSMTPresponse() - Found SMTP success code: 250
May 28 16:11:43 myprivateserver sendEmail[29676]: SUCCESS => Received: 250 OK id=1M9lx1-0007if-EM
May 28 16:11:43 myprivateserver sendEmail[29676]: Email was sent successfully! From: To: Subject: [test] Attachment(s): [webFileCheckLog.txt] Server: [localhost:25]