If you are not spamming it should be go to directly to inbox. Gmail has very smart filters, I guess they do check on how many similar emails are there, minor differences like adding random numbers or text will confirm it as spam.
Other things you should look at if your domain or any IP's are blacklisted.
If you have registered users for specific email subscription; Have then add to white list. Else if you are spamming on random emails, then it will be reported and your product and company can also get banned.
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)
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)
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)
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)
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)
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)
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)
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)
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)
MAILINSPECT(1)MAILINSPECT(1)NAME
mailinspect - sort an mbox by category and pipe emails to a command.
SYNOPSIS
mailinspect [-zjiI] -c category FILE [-gG regex]... [-s command] [-p style] [-o scoring]
mailinspect -V
DESCRIPTION
mailinspect reads the single mbox folder named FILE and sorts it in order of similarity to the category, which must have been created by
dbacl(1). It can be used as a command line tool or interactively, when given the -I switch.
When used as a command line tool, mailinspect prints the sorted list of emails on STDOUT. Each line consists of a seek position for the
given email within FILE, followed by the score and a description string in one of several styles chosen via the -p option.
When supplying a command string in conjunction with the -s option, mailinspect spawns a shell and executes command for every email in FILE
(possibly selected via the -g or-G options), in the sorted order. This is similar to the formail(1) functionality, except the latter
doesn't order the emails.
In interactive mode, all the command line functionality is available via keypresses. The sorted list of emails is displayed in a scrollable
format, and can be viewed, searched, tagged, resorted and sent to shell commands. Predefined shell commands can be associated with function
keys. See the usage section below.
The sorting heuristics are currently (and may always be) experimental, so there is no guarantee that the orderings are particularly well
suited for anything.
EXIT STATUS
mailinspect returns 1 on success, 0 if some error occurred.
OPTIONS -c Use category to compute the scores and sort the emails, which should be the file name of a dbacl(1) category.
-g Only emails matching the regular expression regex are sorted. All other emails are ignored. When several -g and -G options are
present on the command line, earlier regular expressions are overridden by later ones where applicable.
-i Force internationalized mode.
-j Force regular expression searches to be case sensitive.
-o Determines the scoring formula to be used. The parameter scoring must be an integer greater than or equal to zero. By default, scor-
ing equals zero.
-p Prints the email index in the given style. The parameter style must be an integer greater than or equal to zero. By default, style
equals zero.
-s For each email in the list, execute the shell command, with the email body on STDIN. Emails are processed in sorted order.
-z Reverse sort order. Normally, emails are sorted in order of closest to furthest relative to category, but in this case, the opposite
is true.
-I Interactive mode. Instead of printing the sorted list of emails on STDOUT, emails are displayed and can be scrolled, viewed,
searched and piped interactively at the terminal.
-G Only emails not matching the regular expression regex are sorted. Opposite of -g switch.
-V Print the program version number and exit.
USAGE
mailinspect needs to read a prelearned category before it can sort the emails in FILE. See dbacl(1).
Suppose you have two mail folders named good.mbox and bad.mbox respectively. You can create appropriate categories by typing the commands
% dbacl -l good good.mbox -T email
% dbacl -l bad bad.mbox -T email
Next, you can type the following command to view interactively the bad.mbox file with the emails whose score is closest to the category
good listed first:
% mailinspect -I -c good bad.mbox
Alternatively, you might be interested only in the five emails in the folder bad.mbox whose score marks them as the furthest away from the
category bad, completely independently from any other category such as good (ie you want outliers in the scoring sense).
% mailinspect -z -c bad bad.mbox | head -5
In interactive mode, the following keys are defined:
o toggles another scoring formula.
p toggles another display style.
q exits mailinspect.
s sends the currently highlighted email to a shell command.
S sends all currently tagged emails to a shell command, in sorted order. Every email executes the shell command independently.
t tags the currently highlighted email.
T tags all listed emails.
v sends the currently highlighted email to $PAGER for viewing. If the environment variable PAGER is not defined, sends the email to
less(1).
u untags the highlighted email.
U untags all listed emails.
z reverses the sort order of displayed emails.
/ searches for a regular expression (see regex(7)) anywhere within the contents of all listed emails. Hides all emails which don't
match.
? like /, but hides all emails which match, keeping all those which don't match.
As a convenience, the function keys F1-F10 can each be associated with a shell command string. In this case, typing a function key has the
same effect as the S key, but the command is already typed and ready to be edited/accepted. The function key associations are read from
the configuration file .mailinspectrc if it exits.
FILES
$HOME/.mailinspectrc
mailinspect reads the file .mailinspectrc in the $HOME directory, if it exists. This is a plain text file which contains entries of
the form
# this is a comment
F2 cat >> interesting.mbox
F5 mail zarniwoop@megadodo.com
ENVIRONMENT
DBACL_PATH
When this variable is set, its value is prepended to every category filename which doesn't start with a '/'.
SOURCE
The source code for the latest version of this program is available at the following locations:
http://www.lbreyer.com/gpl.html
http://dbacl.sourceforge.net
AUTHOR
Laird A. Breyer <laird@lbreyer.com>
SEE ALSO bayesol(1), dbacl(1), less(1), mailcross(1), regex(7)Version 1.12 Bayesian Text Classification Tools MAILINSPECT(1)
