Sponsored Content
Full Discussion: Drop mailer-daemon mails
Top Forums Shell Programming and Scripting Drop mailer-daemon mails Post 302883284 by Aditya_001 on Monday 13th of January 2014 05:12:30 AM
Old 01-13-2014
Try rediecting all those emails to trash /dev/null
 

5 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Drop Users

I know that this is a really simple and stupid question, but how do I drop / disconnect a user who is logged in? AIX 5.2 (2 Replies)
Discussion started by: trfrye
2 Replies

2. UNIX for Dummies Questions & Answers

Mailer Deamon Question

does somebody knows why when my IRIX system is booting it stop for more than 3 minutes in MAILER DEMOND.??? Thanks in advance for your help (1 Reply)
Discussion started by: michoacan2000
1 Replies

3. UNIX for Dummies Questions & Answers

UNIX command line mailer

What is the difference betweeen MAILX and SENDMAIL. I have SENDMAIL configured in my system, how is it different then MAILX, espicially in the syntax of sending mail from the command line. Thanks in advance (3 Replies)
Discussion started by: dctm_deve
3 Replies

4. UNIX for Dummies Questions & Answers

DNS Drop out

My boss use a MacBook and he encounter with DNS drop out and he cannot surf website for 1-2 mins. The DNS Service of my company is on UNIX server. I try to delete some unused IP of DNS Server in resolv.conf and dhcp.conf and I try to update root.hint file but The problem is not fixed. Please... (5 Replies)
Discussion started by: thsecmaniac
5 Replies

5. Shell Programming and Scripting

Automated e-mailer problem

I am trying to write a bash e-mailer script on a host that has a bunch of CPUs and makes use of all of them. It e-mails a huge list of people, so I wanna save time running this script if I can. for uid in `echo $members` do ( ... /usr/sbin/sendmail -t < $tmp ... ) & done waitWhat... (5 Replies)
Discussion started by: stevensw
5 Replies
Mail::SpamAssassin::PerMsgStatus(3)			User Contributed Perl Documentation		       Mail::SpamAssassin::PerMsgStatus(3)

NAME
Mail::SpamAssassin::PerMsgStatus - per-message status (spam or not-spam) SYNOPSIS
my $spamtest = new Mail::SpamAssassin ({ 'rules_filename' => '/etc/spamassassin.rules', 'userprefs_filename' => $ENV{HOME}.'/.spamassassin.cf' }); my $mail = Mail::SpamAssassin::NoMailAudit->new(); my $status = $spamtest->check ($mail); if ($status->is_spam()) { $status->rewrite_mail (); $mail->accept("caught_spam"); } ... DESCRIPTION
The Mail::SpamAssassin "check()" method returns an object of this class. This object encapsulates all the per-message state. METHODS
$isspam = $status->is_spam () After a mail message has been checked, this method can be called. It will return 1 for mail determined likely to be spam, 0 if it does not seem spam-like. $list = $status->get_names_of_tests_hit () After a mail message has been checked, this method can be called. It will return a comma-separated string, listing all the symbolic test names of the tests which were trigged by the mail. $num = $status->get_hits () After a mail message has been checked, this method can be called. It will return the number of hits this message incurred. $num = $status->get_required_hits () After a mail message has been checked, this method can be called. It will return the number of hits required for a mail to be consid- ered spam. $report = $status->get_report () Deliver a "spam report" on the checked mail message. This contains details of how many spam detection rules it triggered. The report is returned as a multi-line string, with the lines separated by " " characters. $status->rewrite_mail () Rewrite the mail message. This will add headers, and possibly body text, to reflect its spam or not-spam status. The modifications made are as follows: Subject: header for spam mails The string "*****SPAM*****" (changeable with "subject_tag" config option) is prepended to the subject, unless the "rewrite_subject 0" configuration option is given. X-Spam-Status: header for spam mails A string, "Yes, hits=nn required=nn tests=..." is set in this header to reflect the filter status. The keys in this string are as follows: X-Spam-Report: header for spam mails The SpamAssassin report is added to the mail header if the "report_header 1" configuration option is given. hits=nn The number of hits the message triggered. required=nn The threshold at which a mail is marked as spam. tests=... The symbolic names of tests which were triggered. X-Spam-Flag: header for spam mails Set to "YES". Content-Type: header for spam mails Set to "text/plain", in order to defang HTML mail or other active content that could "call back" to the spammer. X-Spam-Checker-Version: header for spam mails Set to the version number of the SpamAssassin checker which tested the mail. spam mail body text The SpamAssassin report is added to top of the mail message body, unless the "report_header 1" configuration option is given. X-Spam-Status: header for non-spam mails A string, "No, hits=nn required=nn tests=..." is set in this header to reflect the filter status. The keys in this string are the same as for spam mails (see above). $messagestring = $status->get_full_message_as_text () Returns the mail message as a string, including headers and raw body text. If the message has been rewritten using "rewrite_mail()", these changes will be reflected in the string. Note: this is simply a helper method which calls methods on the mail message object. It is provided because Mail::Audit uses an unusual (ie. not quite intuitive) interface to do this, and it has been a common stumbling block for authors of scripts which use Spa- mAssassin. $status->finish () Indicate that this $status object is finished with, and can be destroyed. If you are using SpamAssassin in a persistent environment, or checking many mail messages from one Mail::SpamAssassin factory, this method should be called to ensure Perl's garbage collection will clean up old status objects. SEE ALSO
"Mail::SpamAssassin" "spamassassin" perl v5.8.0 2002-09-26 Mail::SpamAssassin::PerMsgStatus(3)
All times are GMT -4. The time now is 09:09 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy