Sponsored Content
Homework and Emergencies Emergency UNIX and Linux Support How to prevent emails as spam? Post 302961173 by Swathe on Tuesday 24th of November 2015 07:42:27 PM
Old 11-24-2015
Gmail marks anything that fails a reverse DNS check as spam
 

9 More Discussions You Might Find Interesting

1. Programming

how to prevent deadlock on this...

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

2. UNIX for Dummies Questions & Answers

Creating emails

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

3. UNIX for Dummies Questions & Answers

duplicate emails

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

4. UNIX for Dummies Questions & Answers

Emails on HP-UX

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

5. UNIX for Dummies Questions & Answers

Delete Old Spam Emails Custom Cron

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. Shell Programming and Scripting

examples of hyperlinks in emails

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

7. UNIX for Dummies Questions & Answers

send emails

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

8. Solaris

Emails issue

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

9. UNIX for Advanced & Expert Users

How to prevent Accidents 'rm -rf *'?

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
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 07:59 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy