Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.
Solved
Email Subject Not Showing
Posted on 2011-09-12
Trying to put together a script to send out email. I have a SUBJECT=, but the email always arrives saying 'no subject'. What am I missing?
#!/bin/bash
# script to send simple email
# email subject
SUBJECT="DELETED TODAY"
# Email To ?
EMAIL="cornelius.taylor@cs
# Email text/message
awk '/deleted/' score_provider_delete.lst > /tmp/emailmessage.txt
EMAILMESSAGE="/tmp/emailme
/bin/mail -s "$SUBJECT" "$EMAIL" < $EMAILMESSAGE
~
~
#!/bin/bash
# script to send simple email
# email subject
SUBJECT="DELETED TODAY"
# Email To ?
EMAIL="cornelius.taylor@cs
# Email text/message
awk '/deleted/' score_provider_delete.lst > /tmp/emailmessage.txt
EMAILMESSAGE="/tmp/emailme
/bin/mail -s "$SUBJECT" "$EMAIL" < $EMAILMESSAGE
~
~
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
17
16
11
44 Comments
change
/bin/mail -s "$SUBJECT" "$EMAIL" < $EMAILMESSAGE
/bin/mail -s "${SUBJECT}" "${EMAIL}" < $EMAILMESSAGE
#!/bin/bash
# script to send simple email
# email subject
SUBJECT='DELETED TODAY'
# Email To ?
EMAIL="cornelius.taylor@cs
# Email text/message
awk '/deleted/' score_provider_delete.lst > /tmp/emailmessage.txt
EMAILMESSAGE="/tmp/emailme
echo "Testing email"
/bin/mail -s "${SUBJECT}" "${EMAIL}" < $EMAILMESSAGE
Still saying (no subject) :-(
# script to send simple email
# email subject
SUBJECT='DELETED TODAY'
# Email To ?
EMAIL="cornelius.taylor@cs
# Email text/message
awk '/deleted/' score_provider_delete.lst > /tmp/emailmessage.txt
EMAILMESSAGE="/tmp/emailme
echo "Testing email"
/bin/mail -s "${SUBJECT}" "${EMAIL}" < $EMAILMESSAGE
Still saying (no subject) :-(
Active 3 days ago
Well,
I can't see any mistake in your script.
Maybe we should try to approach step by step.
What do you get with
/bin/mail -s "DELETED TODAY" "${EMAIL}" < $EMAILMESSAGE
Does it work?
If this doesn't work either - could it be that some server inbetween doesn't like "DELETED"?
Does this work then:
/bin/mail -s "XXXXXXX TODAY" "${EMAIL}" < $EMAILMESSAGE
?
wmp
I can't see any mistake in your script.
Maybe we should try to approach step by step.
What do you get with
/bin/mail -s "DELETED TODAY" "${EMAIL}" < $EMAILMESSAGE
Does it work?
If this doesn't work either - could it be that some server inbetween doesn't like "DELETED"?
Does this work then:
/bin/mail -s "XXXXXXX TODAY" "${EMAIL}" < $EMAILMESSAGE
?
wmp
Active 3 days ago
I heard some people don't like "XXX..." either.
So try something like "EXPERIMENTAL SUBJECT" or the like.
So try something like "EXPERIMENTAL SUBJECT" or the like.
I tested the updated syntax, with DELETED in the subject, and it worked just fine as I expected.
wmp might be on to something about the contents of the subject... I've never ran across that but it wouldn't surprise me if something like that was indeed happening.
Curious what happens when you change subject per wmp's recommendation.
wmp might be on to something about the contents of the subject... I've never ran across that but it wouldn't surprise me if something like that was indeed happening.
Curious what happens when you change subject per wmp's recommendation.
Thanks but same thing :-(
#!/bin/bash
# script to send simple email
# email subject
SUBJECT='DELETED TODAY'
# Email To ?
EMAIL="cornelius.taylor@cs
# Email text/message
awk '/deleted/' score_provider_delete.lst > /tmp/emailmessage.txt
EMAILMESSAGE="/tmp/emailme
echo "Testing email"
#/bin/mail -s "${SUBJECT}" "${EMAIL}" < $EMAILMESSAGE
/bin/mail -s "TODAY" "${EMAIL}" < $EMAILMESSAGE
~
#!/bin/bash
# script to send simple email
# email subject
SUBJECT="EXPERIMENTAL SUBJECT"
# Email To ?
EMAIL="cornelius.taylor@cs
# Email text/message
awk '/deleted/' score_provider_delete.lst > /tmp/emailmessage.txt
EMAILMESSAGE="/tmp/emailme
#/bin/mail -s "${SUBJECT}" "${EMAIL}" < $EMAILMESSAGE
/bin/mail -s "${SUBJECT}" "${EMAIL}" < $EMAILMESSAGE
~
#!/bin/bash
# script to send simple email
# email subject
SUBJECT='DELETED TODAY'
# Email To ?
EMAIL="cornelius.taylor@cs
# Email text/message
awk '/deleted/' score_provider_delete.lst > /tmp/emailmessage.txt
EMAILMESSAGE="/tmp/emailme
echo "Testing email"
#/bin/mail -s "${SUBJECT}" "${EMAIL}" < $EMAILMESSAGE
/bin/mail -s "TODAY" "${EMAIL}" < $EMAILMESSAGE
~
#!/bin/bash
# script to send simple email
# email subject
SUBJECT="EXPERIMENTAL SUBJECT"
# Email To ?
EMAIL="cornelius.taylor@cs
# Email text/message
awk '/deleted/' score_provider_delete.lst > /tmp/emailmessage.txt
EMAILMESSAGE="/tmp/emailme
#/bin/mail -s "${SUBJECT}" "${EMAIL}" < $EMAILMESSAGE
/bin/mail -s "${SUBJECT}" "${EMAIL}" < $EMAILMESSAGE
~
OK so. These mails you are sending are being received, correct? Check the headers and look for the "Subject" line -- I'm curious if the header is non-existant, a null value, or if it says "(no subject)" like you posted earlier.
I understand that the "(no subject)" is probably just something displayed by your email client, but look for it in the headers anyways.
Bottom line here is the script works in general.
I understand that the "(no subject)" is probably just something displayed by your email client, but look for it in the headers anyways.
Bottom line here is the script works in general.
Active 3 days ago
So we have some general problem with the script as a whole.
Could it be that you wrote the script under e.g. Windows and transferred it
(maybe even with copy and paste) to Unix?
Could you try just from the command line (outside any script, that is):
mail -s "MYSUBJECT" cornelius.taylor@csueastba
?
Could it be that you wrote the script under e.g. Windows and transferred it
(maybe even with copy and paste) to Unix?
Could you try just from the command line (outside any script, that is):
mail -s "MYSUBJECT" cornelius.taylor@csueastba
?
Bottom line here is the script works in general.
So we have some general problem with the script as a whole.
Haha!
Ok let me rephrase mine -- Bottom line here is the script is syntactically correct :)
Active 3 days ago
Syntactically - yes!
I'm rather emphasizing some invisible characters or the like.
I'm rather emphasizing some invisible characters or the like.
Nothing much header wise
Reply
from oracle@bb7b.csueastbay.edu
to
date Mon, Sep 12, 2011 at 2:10 PM
mailed-by bb7b.csueastbay.edu
hide details 2:10 PM (39 minutes ago)
0 rows deleted.
Reply
Forward
Reply
from oracle@bb7b.csueastbay.edu
to
date Mon, Sep 12, 2011 at 2:10 PM
mailed-by bb7b.csueastbay.edu
hide details 2:10 PM (39 minutes ago)
0 rows deleted.
Reply
Forward
Yes i did put it on notepad and copied it to unix but when i set list, it looks ok.
#!/bin/bash$
# script to send simple email$
# email subject$
SUBJECT="EXPERIMENTAL SUBJECT"$
# Email To ?$
EMAIL="cornelius.taylor@cs
# Email text/message$
awk '/deleted/' score_provider_delete.lst > /tmp/emailmessage.txt $
EMAILMESSAGE="/tmp/emailme
#/bin/mail -s "${SUBJECT}" "${EMAIL}" < $EMAILMESSAGE$
/bin/mail -s "${SUBJECT}" "${EMAIL}" < $EMAILMESSAGE$
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
:set list
#!/bin/bash$
# script to send simple email$
# email subject$
SUBJECT="EXPERIMENTAL SUBJECT"$
# Email To ?$
EMAIL="cornelius.taylor@cs
# Email text/message$
awk '/deleted/' score_provider_delete.lst > /tmp/emailmessage.txt $
EMAILMESSAGE="/tmp/emailme
#/bin/mail -s "${SUBJECT}" "${EMAIL}" < $EMAILMESSAGE$
/bin/mail -s "${SUBJECT}" "${EMAIL}" < $EMAILMESSAGE$
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
:set list
that's not the actual header.
Do these things to find hidden characters:
vi the script, and type :set list
cat -v scriptname
Do these things to find hidden characters:
vi the script, and type :set list
cat -v scriptname
Ah my bad I spoke too soon, was writing 1 reply then saw your other but didn't pay enough attention to it.
Still would like to see the real headers if possible.
Still would like to see the real headers if possible.
oracle@bb7b:~/scripts$ cat -v email_results.sh
#!/bin/bash
# script to send simple email
# email subject
SUBJECT="EXPERIMENTAL SUBJECT"
# Email To ?
EMAIL="cornelius.taylor@cs
# Email text/message
awk '/deleted/' score_provider_delete.lst > /tmp/emailmessage.txt
EMAILMESSAGE="/tmp/emailme
#/bin/mail -s "${SUBJECT}" "${EMAIL}" < $EMAILMESSAGE
/bin/mail -s "${SUBJECT}" "${EMAIL}" < $EMAILMESSAGE
oracle@bb7b:~/scripts$
./email_results.sh
#!/bin/bash
# script to send simple email
# email subject
SUBJECT="EXPERIMENTAL SUBJECT"
# Email To ?
EMAIL="cornelius.taylor@cs
# Email text/message
awk '/deleted/' score_provider_delete.lst > /tmp/emailmessage.txt
EMAILMESSAGE="/tmp/emailme
#/bin/mail -s "${SUBJECT}" "${EMAIL}" < $EMAILMESSAGE
/bin/mail -s "${SUBJECT}" "${EMAIL}" < $EMAILMESSAGE
oracle@bb7b:~/scripts$
./email_results.sh
Active 3 days ago
>> i did put it on notepad and copied it to unix <<
I'd suggest rewriting the script from scratch under UNIX using vi!
I saw the weirdest things with copy and paste from Windows to Unix.
And with command line I meant what I posted above:
mail -s "MYSUBJECT" cornelius.taylor@csueastba
I'd suggest rewriting the script from scratch under UNIX using vi!
I saw the weirdest things with copy and paste from Windows to Unix.
And with command line I meant what I posted above:
mail -s "MYSUBJECT" cornelius.taylor@csueastba
#!/bin/bash
SUBJECT="Experimental Subject"
EMAIL="cornelius.taylor@cs
awk '/deleted/' score_provider_delete.lst > /tmp/emailmessage.txt
EMAILMESSAGE="/tmp/emailme
/bin/mail -s "${SUBJECT}" "${EMAIL}" < $EMAILMESSAGE
or
"email_result.sh" 6 lines, 239 characters
#!/bin/bash
SUBJECT="Experimental Subject"
EMAIL="cornelius.taylor@cs
awk '/deleted/' score_provider_delete.lst > /tmp/emailmessage.txt
EMAILMESSAGE="/tmp/emailme
/bin/mail -s "SHOW SUBJECT" "${EMAIL}" < $EMAILMESSAGE
~
Same thing either way :-(
SUBJECT="Experimental Subject"
EMAIL="cornelius.taylor@cs
awk '/deleted/' score_provider_delete.lst > /tmp/emailmessage.txt
EMAILMESSAGE="/tmp/emailme
/bin/mail -s "${SUBJECT}" "${EMAIL}" < $EMAILMESSAGE
or
"email_result.sh" 6 lines, 239 characters
#!/bin/bash
SUBJECT="Experimental Subject"
EMAIL="cornelius.taylor@cs
awk '/deleted/' score_provider_delete.lst > /tmp/emailmessage.txt
EMAILMESSAGE="/tmp/emailme
/bin/mail -s "SHOW SUBJECT" "${EMAIL}" < $EMAILMESSAGE
~
Same thing either way :-(
Active 3 days ago
So the script seems indeed OK.
Could you finally run the command line thing?
If this doesn't work either it must indeed have to do with Gmail.
Do you have an account with some other provider to check?
Could you finally run the command line thing?
If this doesn't work either it must indeed have to do with Gmail.
Do you have an account with some other provider to check?
Yes, the same when sent to a different client
#!/bin/bash
SUBJECT="Experimental Subject"
EMAIL="zozimos@gmx.com"
awk '/deleted/' score_provider_delete.lst > /tmp/emailmessage.txt
EMAILMESSAGE="/tmp/emailme
/bin/mail -s "SHOW SUBJECT" "${EMAIL}" < $EMAILMESSAGE
~
~
~
#!/bin/bash
SUBJECT="Experimental Subject"
EMAIL="zozimos@gmx.com"
awk '/deleted/' score_provider_delete.lst > /tmp/emailmessage.txt
EMAILMESSAGE="/tmp/emailme
/bin/mail -s "SHOW SUBJECT" "${EMAIL}" < $EMAILMESSAGE
~
~
~
Active 3 days ago
Last call for the command line test.
mail -s "MYSUBJECT" cornelius.taylor@csueastba
mail -s "MYSUBJECT" cornelius.taylor@csueastba
Sorry
oracle@bb7b:~/scripts$
oracle@bb7b:~/scripts$ mail -s "MYSUBJECT" cornelius.taylor@csueastba
/export/home/oracle/dead.l
oracle@bb7b:~/scripts$
oracle@bb7b:~/scripts$
oracle@bb7b:~/scripts$ mail -s "MYSUBJECT" cornelius.taylor@csueastba
/export/home/oracle/dead.l
oracle@bb7b:~/scripts$
From oracle Mon Sep 12 12:20:03 2011
Return-Path: <oracle>
Received: (from oracle@localhost)
by bb7b.csueastbay.edu (8.14.4+Sun/8.14.4/Submit)
Mon, 12 Sep 2011 12:20:03 -0700 (PDT)
Date: Mon, 12 Sep 2011 12:20:03 -0700 (PDT)
From: oracle
Message-Id: <201109121920.p8CJK3150114
MIME-Version: 1.0
Content-Type: text/plain
0 rows deleted.
Like this??
Delivered-To: cornelius.taylor@csueastba
Received: by 10.231.103.74 with SMTP id j10cs13830ibo;
Mon, 12 Sep 2011 15:11:24 -0700 (PDT)
Received: by 10.204.132.68 with SMTP id a4mr225358bkt.154.13158654
Mon, 12 Sep 2011 15:11:23 -0700 (PDT)
Return-Path: <noreply@experts-exchange.
Received: from slean2.csueastbay.edu (slean2.csueastbay.edu [134.154.192.27])
by mx.google.com with ESMTP id i3si479914bke.79.2011.09.1
Mon, 12 Sep 2011 15:11:21 -0700 (PDT)
Received-SPF: pass (google.com: domain of noreply@experts-exchange.c
Authentication-Results: mx.google.com; spf=pass (google.com: domain of noreply@experts-exchange.c
X-IronPort-Anti-Spam-Filte
X-IronPort-Anti-Spam-Resul
X-IronPort-AV: E=Sophos;i="4.68,370,13121
d="scan'208";a="36181651"
Received: from www1.experts-exchange.com ([64.156.132.141])
by slean2.csueastbay.edu with ESMTP/TLS/DHE-RSA-AES256-S
Received: from www1.experts-exchange.com (localhost [127.0.0.1])
by www1.experts-exchange.com (8.14.4/8.14.4) with ESMTP id p8CMBJvE007704
for <cornelius.taylor@csueastb
(envelope-from noreply@experts-exchange.c
Date: Mon, 12 Sep 2011 15:11:19 -0700 (PDT)
From: Experts Exchange <noreply@experts-exchange.
To: cornelius.taylor@csueastba
Message-ID: <1399811084.654.1315865479
Subject: Comment Added: Email Subject Not Showing
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding:
X-Mailer: Experts Exchange
Delivered-To: cornelius.taylor@csueastba
Received: by 10.231.103.74 with SMTP id j10cs14393ibo;
Mon, 12 Sep 2011 15:50:38 -0700 (PDT)
Received: by 10.42.132.10 with SMTP id b10mr1024286ict.76.1315867
Mon, 12 Sep 2011 15:50:38 -0700 (PDT)
Return-Path: <oracle@bb7b.csueastbay.ed
Received: from slean2.csueastbay.edu (slean2.csueastbay.edu [154.174.192.27])
by mx.google.com with ESMTP id ve2si5695517icb.7.2011.09.
Mon, 12 Sep 2011 15:50:36 -0700 (PDT)
Received-SPF: pass (google.com: best guess record for domain of oracle@bb7b.csueastbay.edu
Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of oracle@bb7b.csueastbay.edu
X-IronPort-AV: E=Sophos;i="4.68,370,13121
d="scan'208";a="36183863"
Received: from bb7b.csueastbay.edu ([154.174.192.26])
by iclean2.csueastbay.edu with ESMTP; 12 Sep 2011 15:50:36 -0700
Received: from bb7b.csueastbay.edu (localhost [127.0.0.1])
by bb7b.csueastbay.edu (8.14.4+Sun/8.14.4) with ESMTP id p8CMoaPc016524;
Mon, 12 Sep 2011 15:50:36 -0700 (PDT)
Received: (from oracle@localhost)
by bb7b.csueastbay.edu (8.14.4+Sun/8.14.4/Submit)
Mon, 12 Sep 2011 15:50:36 -0700 (PDT)
Date: Mon, 12 Sep 2011 15:50:36 -0700 (PDT)
From: oracle@bb7b.csueastbay.edu
Message-Id: <201109122250.p8CMoaXd0165
MIME-Version: 1.0
Content-Type: text/plain
Received: by 10.231.103.74 with SMTP id j10cs14393ibo;
Mon, 12 Sep 2011 15:50:38 -0700 (PDT)
Received: by 10.42.132.10 with SMTP id b10mr1024286ict.76.1315867
Mon, 12 Sep 2011 15:50:38 -0700 (PDT)
Return-Path: <oracle@bb7b.csueastbay.ed
Received: from slean2.csueastbay.edu (slean2.csueastbay.edu [154.174.192.27])
by mx.google.com with ESMTP id ve2si5695517icb.7.2011.09.
Mon, 12 Sep 2011 15:50:36 -0700 (PDT)
Received-SPF: pass (google.com: best guess record for domain of oracle@bb7b.csueastbay.edu
Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of oracle@bb7b.csueastbay.edu
X-IronPort-AV: E=Sophos;i="4.68,370,13121
d="scan'208";a="36183863"
Received: from bb7b.csueastbay.edu ([154.174.192.26])
by iclean2.csueastbay.edu with ESMTP; 12 Sep 2011 15:50:36 -0700
Received: from bb7b.csueastbay.edu (localhost [127.0.0.1])
by bb7b.csueastbay.edu (8.14.4+Sun/8.14.4) with ESMTP id p8CMoaPc016524;
Mon, 12 Sep 2011 15:50:36 -0700 (PDT)
Received: (from oracle@localhost)
by bb7b.csueastbay.edu (8.14.4+Sun/8.14.4/Submit)
Mon, 12 Sep 2011 15:50:36 -0700 (PDT)
Date: Mon, 12 Sep 2011 15:50:36 -0700 (PDT)
From: oracle@bb7b.csueastbay.edu
Message-Id: <201109122250.p8CMoaXd0165
MIME-Version: 1.0
Content-Type: text/plain
Ah yes, finally.
OK so the Subject header is non-existent, but so is the body To, so that whole thing looks abnormal.
I have an idea...
OK so the Subject header is non-existent, but so is the body To, so that whole thing looks abnormal.
I have an idea...
which mail
ls -l `!!`
racle@bb7b:/u05/datapump_d
/usr/bin/mail
oracle@bb7b:/u05/datapump_
oracle@bb7b:/u05/datapump_
ls -l `which mail`
-r-x--s--x 1 root mail 67932 Aug 10 2010 /usr/bin/mail
/usr/bin/mail
oracle@bb7b:/u05/datapump_
oracle@bb7b:/u05/datapump_
ls -l `which mail`
-r-x--s--x 1 root mail 67932 Aug 10 2010 /usr/bin/mail
OK. The administrator said i should actually be using sendmail where i would need to feed all that information myself.
Thanks
Thanks
Not sure why you gave the Accepted Solution to http:#36525987
wmp and I both spent a lot of time on this, both had great ideas, agreed on pretty much everything, but I still don't understand why you assigned points the way you did.
Is it possible to distribute the full amount of points split equally between wmp and I? If you object wmp or have comments, please speak up.
wmp and I both spent a lot of time on this, both had great ideas, agreed on pretty much everything, but I still don't understand why you assigned points the way you did.
Is it possible to distribute the full amount of points split equally between wmp and I? If you object wmp or have comments, please speak up.
I may be confused about how points work with questions since I haven't submitted one. I got a base value of 250 for this, and I assume wmp got 500. I don't want to take away any points from wmp, so is it possible for both of us to get 500?
Hah ok.
Wasn't trying to start any drama, just was a bit confused, only been on here for like a week :)
And yes thanks for the points! haha
Good luck.
Wasn't trying to start any drama, just was a bit confused, only been on here for like a week :)
And yes thanks for the points! haha
Good luck.
From what i see, 500 is the maximum possible on any question. One of you noted there was nothing wrong with the script, you tested the script and concluded it work. That is why i upped from 250 to 500, the maximum in order to give the original value to each. No wmp got 250 also. I know there used to be a way to work around the 500 point limit by putting out another question with a title like Points For Papertrip, but I think EE now discourages if not outright forbids that.
Featured Post
Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
If you have a server on collocation with the super-fast CPU, that doesn't mean that you get it running at full power.
Here is a preamble. When doing inventory of Linux servers, that I'm administering, I've found that some of them are running on l…
Join Greg Farro and Ethan Banks from Packet Pushers (http://packetpushers.net/podcast/podcasts/pq-show-93-smart-network-monitoring-paessler-sponsored/) and Greg Ross from Paessler (https://www.paessler.com/prtg) for a discussion about smart network …
Learn how to get help with Linux/Unix bash shell commands.
Use help to read help documents for built in bash shell commands.: Use man to interface with the online reference manuals for shell commands.: Use man to search man pages for unknown command…
Learn how to find files with the shell using the find and locate commands.
Use locate to find a needle in a haystack.: With locate, check if the file still exists.: Use find to get the actual location of the file.:
Suggested Courses
Course of the Month13 days, 6 hours left to enroll
656 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.