How to sendemail from the command line using a Gmail account and others

  16 Responses to “How to sendemail from the command line using a Gmail account and others”

1. 

   Luca Bruno says:

   March 27, 2009 at 9:46 am

   Also see esmtp, it’s compatible with sendmail.
2. 

   Ridgeland says:

   March 27, 2009 at 3:54 pm

   Thank You.
   I had tried this a year or two ago and gave up easily. I am using Ubuntu 8.10, synaptics for sendemail then a hybrid of your “Simple Email using Gmail account” and “Simple Email”. I’m not using gmail but for a simple email I used fields -f -t -s -xu -xp -u -m
   -s mail.mydomain.net
3. 

   rossdub says:

   May 29, 2009 at 1:20 am

   I have an Etch server up and running, and followed the instructions here. They worked perfectly, and the script executed successfully, but I am not receiving the email. Perhaps there is a server or router configuration I am missing? Here is the verbose output from my test email.

   
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]

4. 

   Andrew says:

   October 19, 2009 at 4:15 am

   ERROR => Timeout while connecting to smtp.gmail.com:25 There was no response after 60 seconds.
5. 

   scott says:

   November 26, 2009 at 6:26 am

   I just started getting the ERROR => Timeout while connecting to smtp.gmail.com:25 There was no response after 60 seconds.

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

   Dundee says:

   December 14, 2009 at 3:02 pm

   Hi guys,
   please a have same trouble like a Scott :-/

   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
7. 

   Paul says:

   March 22, 2010 at 4:34 pm

   Re: Gmail, try: smtp.gmail.com:587. My ISP blocks port 25, but 587 works for Gmail.
8. 

   sacad says:

   August 5, 2010 at 12:54 pm

   I tried
   sendEmail -v -v -f sacad@seznam.cz -t +420xxxxxxxxx@sms.cz.o2.com -m "test" -u "test:)" -o tls=auto -s smtp.seznam.cz -xu sacad -xp ****************

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

   AUTH was successful… so what is wrong?
9. 

   helloworld says:

   October 23, 2010 at 1:30 am

   I tried with seznam too, but every time I receive EXITING: SIGINT

   but everything is set correctly…………….

   so what is wrong? thanx:)
10. 

    priyanka says:

    November 19, 2010 at 7:39 am

    how to send mail from website to webadmin account by smtp server in html code
11. 

    Larry says:

    January 19, 2011 at 2:22 am

    I’m on Ubuntu 10.04 LTS and sending to port 25 (587) works as expected. Sending to port 465 with tls give me a seg fault. Verbose output consists of:

    $ 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
12. 

    Panas says:

    February 7, 2011 at 11:10 am

    Error When Crontab Run

    grep CRON /var/log/syslog

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

    Dani says:

    November 3, 2011 at 3:33 pm

    I’m facing the same error than 11 (Larry) using gmail smtp server through port 25. Anybody have solved it?

    Thanks in advance
14. 

    Mike O'Connor says:

    November 22, 2011 at 7:55 am

    I’m with Larry and Dani--- segmentation fault when using port 465 in sendemail. I got exactly the same printout as Larry except for the last byte of the IP address--- perchance because he too is a CenturyLink customer and thus likewise bought a Qwest-configured DSL modem of the ActionTec make which comes preset to 192.168.0.1, with a DHCP server inside and a bitmask of 255.255.255.0 (though that’s a common setup).

    [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.
15. 

    Sergey says:

    December 16, 2011 at 9:48 am

    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:465 \
    -xu myusername[WITHOUTthe@myveryowndomainname.com] -xp mypassword \
    -v -v

    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
16. 

    TIMEOUT says:

    December 23, 2011 at 10:05 am

    TIMEOUT: If you are getting time’d out, you should specify gmail’s smtp server’s port:
    smtp.gmail.com:587

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