I'm trying to monitor queues for specific tickets and email the user only when a new ticket is created.
But to complicate things, I need to think how I'm going to deal with repeat emails on the same ticket until it is closed.
Meaning, script runs every 15 minutes, if it finds a ticket and report on it, then the next 15 minutes it will report the same ticket and I don't want that.
The script itself is functioning , as in ... sqlplus query finds tickets and the script emails them however, it emails all the tickets and only want to see the ticket that was create in the last 15 mins.
really confused ... or I'm going about this wrong way .....
I need to write a script that can find a bad record (for example: there is date field colom but value provided in the file for this field is N/A) then script shoud searches this pattern and then insert the whole record into the bad file.
Example:
File1
Name designation dateOfJoining... (1 Reply)
I need to write a script that can find a bad record (for example: there is date field colom but value provided in the file for this field is N/A) then script shoud searches this pattern and then insert the whole record into the bad file.
Example:
File1
Name designation dateOfJoining... (2 Replies)
Hi guys,
i have a big file with the following format.This includes header(H),detail(D) and trailer(T) information in the file.My problem is i have to search for the character "6h" at 14 th and 15 th position in all the records .if it is there i have to write all those records into a... (1 Reply)
Hello ,
I am trying to write a unix shell script to compare folder permission to say drwxr-x-wx and then send an email to my id in case the folders don't have the drwxr-x-wx permissions set for them .
I have been trying to come up with a script for few days now , pls help me:( (2 Replies)
Hi,
I have a large file with huge number of records which are of following pattern:
TYPE1
{
originNodeType : "IVR"
originHostName : "AAIVR"
originTransactionID : "01310559"
originTimeStamp : "20110620192440+0530"
hostName : "hhhh"
voucher : '0'D
rProfileID : "ZZZZ"
Before
{
Flags :... (1 Reply)
Hi,
I have a input file with the following entries:
1one
2two
3three
1four
2five
3six
1seven
1eight
1nine
2ten
The output should be
1one
2two
3three
1four
2five
3six (2 Replies)
Hi,
I have a input file with the following entries:
1one
2two
3three
1four
2five
3six
1seven
1eight
1nine
2ten
2eleven
2twelve
1thirteen
2fourteen
The output should be: (5 Replies)
Hi! all
can any one tell me how to compare current record of column with next and previous record in awk without using array
my case is like this
input.txt
0 32
1 26
2 27
3 34
4 26
5 25
6 24
9 23
0 32
1 28
2 15
3 26
4 24 (7 Replies)
Hi,,
I have requirement that i need to get DISTINCT values from a table and if there are two records i need to update it to one record and then need to submit INSERT statements by using the updated value as a parameter. Here is the example follows..
SELECT DISTINCT ID FROM OFFER_GROUP WHERE... (1 Reply)
Discussion started by: Samah
1 Replies
LEARN ABOUT DEBIAN
email::send::test
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)