03-20-2017
Hi,
The best thing then would be to check your mail server's log, and see if it actually did send it and what response it got if it did. If you're on a Solaris 10 system that's using a default Sendmail configuration, then this will most likely be writing its log entries to /var/adm/messages.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
h I would like to know the differnce (both working and how) between at command and crontab..
Thanks in advance
Satish D (2 Replies)
Discussion started by: doddas
2 Replies
2. Shell Programming and Scripting
Hi all,
I am a newbie currently trying to execute shell commands from ruby instead of a shell script.(This method is conceived only for solaris so no issues with porting to other OS and all)
Eg:
Consider the command 'ls"
with a shell script ,I would use it like this
bash# ls
<all the... (4 Replies)
Discussion started by: wrapster
4 Replies
3. UNIX for Advanced & Expert Users
Hi ,
I have modified .profile and after that i ran it as .profile. Now no command i working even ls is not working
When i type ls , it is showing that -ksh not found
I tried to run as . $home/.profile , it is saying as permission denied .
How can we do that .. any idea..
Thanks... (2 Replies)
Discussion started by: arunkumar_mca
2 Replies
4. UNIX for Advanced & Expert Users
Hi,
I have an application where if it runs indivisually could able to execute commands (like system("ls")) and could able to execute tcl script.
Same application if started from health monitor process (From health monitor process my application will be forked), it could not execute the... (1 Reply)
Discussion started by: chandrutiptur
1 Replies
5. Fedora
hi friends
i am using fedora linux operating system on the server and two clients(with windows os) are connected to it(server ).but here wall and write cmds are not working to send messages from one system to another system .
pls help me (4 Replies)
Discussion started by: sankar_vitam
4 Replies
6. Shell Programming and Scripting
Hi All,
I have created a shell script having some general copying and moving commands. Commands are working fine in Shell but while executing the shell script it is showing an error
mv: cannot stat `/apps/orarpt/in/*': No such file or directory
command is
mv $IN_DIR* $ARCHIVE_DIR
where... (5 Replies)
Discussion started by: maindola.amit
5 Replies
7. Shell Programming and Scripting
I am using SED to edit a file (called file)
the file contains the word "ERROR"
and I want to use SED to:
1. Search for text "ERROR"
If found,
2. Append new line with text "hoi"
I tried:
sed 's/ERROR/ a\hoi' file
sed 's/ERROR/ a\ hoi' file
I get all the time the error
sed:... (7 Replies)
Discussion started by: Alex400
7 Replies
8. UNIX and Linux Applications
About 8-12 months ago I wrote a script that pulled together several mplayer commands to perform various activities. One allowed me to press the s-key to take snapshots with my webcam. Useful for recording the sensors I build.
Now it:
vd=0
bash-4.1$ TV1="-tv... (2 Replies)
Discussion started by: slak0
2 Replies
9. Shell Programming and Scripting
Hi Friends,
I am unable to run our application commands on remote server using ssh (passwordless login enabled). But the same command running with telent perl script. please suggest.
SSH:
C:/bin>ssh -l monitor tl04cp01 exec "/home/monitor/123"
/home/monitor/123: viewlog: not found.
... (7 Replies)
Discussion started by: suresh3566
7 Replies
10. Shell Programming and Scripting
(Using Bash 4.4)
When I write something like dir="~/dox"
ls $dir then I get the message that the directory '~/docs' does not exist. I understand that the tilde is not expanded at the time of the above assignment because of the quotes. But why is it not expanded at the time when the ls command is... (2 Replies)
Discussion started by: Ralph
2 Replies
LEARN ABOUT DEBIAN
jifty::notification
Jifty::Notification(3pm) User Contributed Perl Documentation Jifty::Notification(3pm)
NAME
Jifty::Notification - Send emails from Jifty
USAGE
It is recommended that you subclass Jifty::Notification and override "body", "html_body", "subject", "recipients", and "from" for each
message. (You may want a base class to provide "from", "preface" and "footer" for example.) This lets you keep all of your notifications
in the same place.
However, if you really want to make a notification type in code without subclassing, you can create a "Jifty::Notification" and call the
"set_body", "set_subject", and so on methods on it.
METHODS
new [KEY1 => VAL1, ...]
Creates a new Jifty::Notification. Any keyword args given are used to call set accessors of the same name.
Then it calls "setup".
setup
Your subclass should override this to set the various field values.
send_one_message
Delivers the notification, using the Email::Send mailer defined in the "Mailer" and "MailerArgs" configuration arguments. Returns true if
mail was actually sent. Note errors are not the only cause of mail not being sent -- for example, the recipients list could be empty.
If you wish to send HTML mail, set "html_body". If this is not set (for backwards compatibility) a plain-text email is sent. If
"html_body" and "body" are both set, a multipart mail is sent. See Email::MIME::CreateHTML for how this is done.
Be aware that if you haven't set "recipients", this will fail silently and return without doing anything useful.
set_headers MESSAGE
Takes a Email::MIME object "MESSAGE", and modifies it as necessary before sending it out. As the method name implies, this is usually used
to add or modify headers. By default, does nothing; this method is meant to be overridden.
body [BODY]
Gets or sets the body of the notification, as a string.
subject [SUBJECT]
Gets or sets the subject of the notification, as a string.
from [FROM]
Gets or sets the from address of the notification, as a string.
recipients [RECIPIENT, ...]
Gets or sets the addresses of the recipients of the notification, as a list of strings (not a reference).
email_from OBJECT
Returns the email address from the given object. This defaults to calling an 'email' method on the object. This method will be called by
"send" to get email addresses (for "to") out of the list of "recipients".
to_list [OBJECT, OBJECT...]
Gets or sets the list of objects that the message will be sent to. Each one is sent a separate copy of the email. If passed no
parameters, returns the objects that have been set. This also suppresses duplicates.
send
Sends an individual email to every user in "to_list"; it does this by setting "to" and "recipient" to the first user in "to_list" calling
Jifty::Notification's "send" method, and progressing down the list.
Additionally, if "to" was set elsewhere, sends an email to that person, as well.
to
Of the list of users that "to" provided, returns the one which mail is currently being sent to. This is set by the "send" method, such
that it is available to all of the methods that Jifty::Notification's "send" method calls.
preface
Print a header for the message. You want to override this to print a message.
Returns the message as a scalar.
footer
Print a footer for the message. You want to override this to print a message.
Returns the message as a scalar.
full_body
The main, plain-text part of the message. This is the preface, body, and footer joined by newlines.
full_html
Same as full_body, but with HTML.
parts
The parts of the message. You want to override this if you want to send multi-part mail. By default, this method returns a single part
consisting of the result of calling "$self->full_body".
Returns the parts as an array reference.
magic_letme_token_for PATH
Returns a Jifty::LetMe token which allows the current user to access a path on the site.
perl v5.14.2 2011-01-26 Jifty::Notification(3pm)