I have a problem of getting multiple LogWatch mails from my box. I have a cron setup to send me (and some other users) Logwatch report mail form our server. I end up getting multiple mails from all the boxes (other users have not complained of this). I cannot figure out why. I have checked the mailllog and it shows only 1 mail being transmitted. I also checked the cron files (did not find any)... and it also has only 1 cron for Logwatch.
Can someone please advice on the reason I am getting these multiple mails?
I am running the server on RH Linux 8.0 and 7.3. ON the client side I am using MS Outlook 2000 (on Windows 98) to down load the mails.
getting error as below while executing script in linux.
OS version:
Linux VGP-3GPSDB-LX 3.10.0-514.el7.x86_64 #1 SMP Wed Oct 19 11:24:13 EDT 2016 x86_64 x86_64 x86_64 GNU/Linux
./imxtract.sh: line 395: unexpected EOF while looking for matching ``'
./imxtract.sh: line 402: syntax error:... (1 Reply)
Hi All,
I am pretty new to the mail service in Sun Solaris 5.10. If anybody help me in writing a script for the multiple recipient with subject and the body would be a helpful.
Kindly help...
Thanks in advance. :)
Warm Regards,
Pramod (5 Replies)
All,
Trying to ftp to a remote ftp server.
See following output:
ftp -dv xx.xx.xx.xx
Connected to xx.xx.xx.xx (xx.xx.xx.xx).
220 Microsoft FTP Service
Name (xx.xx.xx.xx:username): ftpuser
---> USER ftpuser
331 Password required for ftpuser.
Password:
---> PASS XXXX
230 User logged... (1 Reply)
Guys
I have not much idea on suse or any other linux flavour.
This is what i have:
cat /etc/issue
Welcome to SUSE LINUX Enterprise Server 9 (i586) - Kernel \r (\l).
ps -ef |grep postfix |grep -v grep
root 18620 1 0 Mar17 ? 00:00:00 /usr/lib/postfix/master
postfix ... (0 Replies)
Hi-I want to create a shell script which should read a file line by line (file having email address and transaction id of each user)and send email on email ids with the transaction id of the user respectively.
Please help - I think a while loop should help but I am very new too UNIX Shell... (1 Reply)
HI,
In unix we can get profile on a c program like this ::
cc -g -p -o cpp_sw_gsmconverter_shailesh5 cpp_sw_gsmconverter_shailesh5.c
prof cpp_sw_gsmconverter_shailesh5
In the same manner how can I collect statistics in linux using gcc command.
Thanks in advance. (1 Reply)
Hi all, can someone tell me the easiest was to get disk info from a console.
I manage headless servers, and would like to collect the specs on hard drives installed without looking it up through Sun.
The boot messages only tell me the size/name e.g. 'Sun36G'
I want to know the rotation... (1 Reply)
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)