9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
When invoking unix commands from other third party tools (IBM ETL), we run the rm / mv commands with the folder as argument been passed. Eg
rm -rf {folder}/*
when the parameter {folder} did not pass rightly or becomes blank, the command becomes dangerous to execute rm -rf /*
How to prevent... (9 Replies)
Discussion started by: deepakwins
9 Replies
2. Solaris
Dear all,
I am facing an issue in my data Center environment related to mails being generated by users on my machines.
Let me walk you through the issue one by one.
Each system (100+ servers in my DC) has a user sysmon on it that sends mails to a specific Email ID. The user runs scripts... (8 Replies)
Discussion started by: Junaid Subhani
8 Replies
3. UNIX for Dummies Questions & Answers
hi guys
I need to send emails to some accounts
1. I need sendmail up and running right?
2. I need my local sendmail to use an existing SMTP server to send emails (10.x.x.x)? in that case what I need to configure to send emails?
since using mail myaccount@companyame.com is not sending emails... (3 Replies)
Discussion started by: karlochacon
3 Replies
4. Shell Programming and Scripting
Hi All,
Im using bash on a sloaris box.
I am using mailx to send emails from the unix box to internal email accounts. Does anyone have an example of how I can generate a hyperlink within the email body so that when the recipeint recieves the email, they can click on the link and the link... (1 Reply)
Discussion started by: satnamx
1 Replies
5. UNIX for Dummies Questions & Answers
Hey Guys,
I've done some research however I got stuck. My goal is to create a cron job that runs every hour and goes through all web accounts on my server and deletes spam emails that are older than 3 days. This is what I came up with:
0 * * * * find /home/*/mail/*/*/.spam/cur/* -type f... (0 Replies)
Discussion started by: plxkarl
0 Replies
6. UNIX for Dummies Questions & Answers
Hi Guys
I am running Oracle database on HP-UX, every now and then I get emails that are sent to me by root. When check with the sysadmin know one have a clue as to where does the emails come from.
I need to stop this emails...how do I check which script is sending me the emails.
Thanks
... (0 Replies)
Discussion started by: Phuti
0 Replies
7. UNIX for Dummies Questions & Answers
Hi all new here.
Question.
My mail server is sending out duplicate emails but its not system wide. We have several virtual host that use our email server and some are having the duplicate emails issue and some are not. For example in the office some people are getting duplicate emails but i am... (1 Reply)
Discussion started by: mcraul
1 Replies
8. UNIX for Dummies Questions & Answers
Hi, I posted here 2 months ago, saying I wanted to learn UNIX for my work running a small ISP. I had the problem of practically no technical support for our system. Many courses later, I can just about do everything I need to do.
The server is a FreeBSD i386. I can now create email accounts for... (4 Replies)
Discussion started by: ferret495
4 Replies
9. Programming
I am using linux termios structure to configure serial port and read the port by read function. For some reason, if I read the whole buffer, almost every time the buffer does not contain the correct reply message sequence from a device sending reply to my linux PC. So I use... (5 Replies)
Discussion started by: yimab
5 Replies
Email::Send::Test(3pm) User Contributed Perl Documentation Email::Send::Test(3pm)
NAME
Email::Send::Test - Captures emails sent via Email::Send for testing
SYNOPSIS
# Load as normal
use Email::Send;
use Email::Send::Test;
# Always clear the email trap before each test to prevent unexpected
# results, and thus spurious test results.
Email::Send::Test->clear;
### BEGIN YOUR CODE TO BE TESTED (example follows)
my $sender = Email::Send->new({ mailer => 'Test' });
$sender->send( $message );
### END YOUR CODE TO BE TESTED
# Check that the number and type (and content) of mails
# matched what you expect.
my @emails = Email::Send::Test->emails;
is( scalar(@emails), 1, 'Sent 1 email' );
isa_ok( $emails[0], 'Email::MIME' ); # Email::Simple subclasses pass through
DESCRIPTION
Email::Send::Test is a driver for use in testing applications that use Email::Send to send email.
To be able to use it in testing, you will need some sort of configuration mechanism to specify the delivery method to be used, or some
other way that in your testing scripts you can convince your code to use "Test" as the mailer, rather than "Sendmail" or another real
mailer.
How does it Work
Email::Send::Test is a trap for emails. When an email is sent, it adds the emails to an internal array without doing anything at all to
them, and returns success to the caller.
If your application sends one email, there will be one in the trap. If you send 20, there will be 20, and so on.
A typical test will involve doing running some code that should result in an email being sent, and then checking in the trap to see if the
code did actually send out the email.
If you want you can get the emails out the trap and examine them. If you only care that something got sent you can simply clear the trap
and move on to your next test.
The Email Trap
The email trap is a simple array fills with whatever is sent.
When you send an email, it is pushed onto the end of the array. You can access the array directly if you wish, or use the methods provided.
METHODS
send $message
As for every other Email::Send mailer, "send" takes the message to be sent.
However, in our case there are no arguments of any value to us, and so they are ignored.
It is worth nothing that we do NOTHING to check or alter the email. For example, if we are passed "undef" it ends up as is in the trap. In
this manner, you can see exactly what was sent without any possible tampering on the part of the testing mailer.
Of course, this doesn't prevent any tampering by Email::Send itself :)
Always returns true.
emails
The "emails" method is the preferred and recommended method of getting access to the email trap.
In list context, returns the content of the trap array as a list.
In scalar context, returns the number of items in the trap.
clear
The "clear" method resets the trap, emptying it.
It is recommended you always clear the trap before each test to ensure any existing emails are removed and don't create a spurious test
result.
Always returns true.
deliveries
This method returns a list of arrayrefs, one for each call to "send" that has been made. Each arrayref is in the form:
[ $mailer, $email, @rest ]
The first element is the invocant on which "send" was called. The second is the email that was given to "send". The third is the rest of
the arguments given to "send".
SUPPORT
All bugs should be filed via the CPAN bug tracker at
http://rt.cpan.org/NoAuth/ReportBug.html?Queue=Email-Send-Test <http://rt.cpan.org/NoAuth/ReportBug.html?Queue=Email-Send-Test>
For other issues, or commercial enhancement or support, contact the author.
AUTHORS
Current maintainer: Ricardo SIGNES, <rjbs@cpan.org>.
Original author: Adam Kennedy <cpan@ali.as>, <http://ali.as/>
COPYRIGHT
Copyright (c) 2004 - 2005 Adam Kennedy. All rights reserved. This program is free software; you can redistribute it and/or modify it under
the same terms as Perl itself.
The full text of the license can be found in the LICENSE file included with this module.
perl v5.12.4 2011-08-31 Email::Send::Test(3pm)
