Now this is a bit tricky, but works great if you can decide which Top Level Domains or TLDs you want to receive mail We are getting so much spam from countries we never receive useful mail, I've been experimenting with blocking entire TLDs using sendmail access_db as an antispam technique.
Here is my current list, working great... yes I might miss a good one, but it blocks SO MUCH junk :
Combining this TLD blocking with Procmail charset filters has cut my spam down to fraction of what it was.......
Hi,
I have created an access file using makemap and write in user email address that wish to be rejected by the mail server but it doesn't work. I still can receive the emails from the domains that are supposed to be REJECTED. Please help.
Sendmail version 8.9.1
Solaris 2.6
TQ (3 Replies)
hi
i edited the /etc/mail/access files with the line "yahoo.com REJECT", afterwhich i cannot send out files to the yahoo.com domain. :mad: can someone advise on how to go about configuring such that i am able to
send mail out to yahoo.com BUT block INCOMING mail from yahoo.com :confused:
i... (0 Replies)
Hi,
I need to install a program on my Centos 5.3 server that will block unauthorized ssh/ftp access attempts. The two features I require is that I should be able to configure the program to block the IP of the intruder after a a certain amount of access attempts and that it should display a... (3 Replies)
I am trying to configure access file of sendmail to relay on certain domain.
I noticed that it does not work if I put domain name but it works when I put the IP address of that domain.
for example:
zgoldz.com RELAY (does not work)
RELAY (works fine)
... (1 Reply)
Hello,
So here's what I am trying to accomplish. We have a sendmail server and we are trying to stop backscattering. One idea that we came up with to prevent this is to utilize sendmail's access database.
Basically we'd have the first line bounce all mail coming in to our mail server to users... (9 Replies)
Hey All,
Problem:
I have a application which runs on port 8153 (http) and on 8154 (https). For design reasons i can not block tcp connections to 8153.
How do i forward all requests from http 8153 to https 8154( this would be the ideal solution)
Or
redirect all requests that come to... (2 Replies)
Discussion started by: Arun Kumar
2 Replies
8. Post Here to Contact Site Administrators and Moderators
For some reason Google Chrome sees unix.com as dangerous and has start to block it. I need to select advanced and continue on own risk.
Can you make an effort to remove unix.com form the list of dangerous site from Google.
IE has not this problem. (5 Replies)
Discussion started by: Jotne
5 Replies
LEARN ABOUT REDHAT
regexp_table
REGEXP_TABLE(5) File Formats Manual REGEXP_TABLE(5)NAME
regexp_table - format of Postfix regular expression tables
SYNOPSIS
regexp:/etc/postfix/filename
DESCRIPTION
The Postfix mail system uses optional tables for address rewriting or mail routing. These tables are usually in dbm or db format. Alterna-
tively, lookup tables can be specified in POSIX regular expression form.
To find out what types of lookup tables your Postfix system supports use the postconf -m command.
The general form of a Postfix regular expression table is:
pattern result
When pattern matches a search string, use the corresponding result.
blank lines and comments
Empty lines and whitespace-only lines are ignored, as are lines whose first non-whitespace character is a `#'.
multi-line text
A logical line starts with non-whitespace text. A line that starts with whitespace continues a logical line.
pattern1!pattern2 result
Matches pattern1 but not pattern2.
Each pattern is a regular expression enclosed by a pair of delimiters. The regular expression syntax is described in re_format(7). The
expression delimiter can be any character, except whitespace or characters that have special meaning (traditionally the forward slash is
used). The regular expression can contain whitespace.
By default, matching is case-insensitive, although following the second slash with an `i' flag will reverse this. Other flags are `x' (dis-
able extended expression syntax), and `m' (enable multi-line mode).
Each pattern is applied to the entire lookup key string. Depending on the application, that string is an entire client hostname, an entire
client IP address, or an entire mail address. Thus, no parent domain or parent network search is done, and user@domain mail addresses are
not broken up into their user and domain constituent parts, nor is user+foo broken up into user and foo.
Patterns are applied in the order as specified in the table, until a pattern is found that matches the search string.
Substitution of substrings from the matched expression into the result string is possible using $1, $2, etc.. The macros in the result
string may need to be written as ${n} or $(n) if they aren't followed by whitespace.
EXAMPLE SMTPD ACCESS MAP
# Disallow sender-specified routing. This is a must if you relay mail
# for other domains.
/[%!@].*[%!@]/ 550 Sender-specified routing rejected
# Postmaster is OK, that way they can talk to us about how to fix
# their problem.
/^postmaster@/ OK
# Protect your outgoing majordomo exploders
/^(.*)-outgoing@(.*)$/!/^owner-/ 550 Use ${1}@${2} instead
EXAMPLE HEADER FILTER MAP
# These were once common in junk mail.
/^Subject: make money fast/ REJECT
/^To: friend@public.com/ REJECT
SEE ALSO pcre_table(5) format of PCRE tables
AUTHOR(S)
The regexp table lookup code was originally written by:
LaMont Jones
lamont@hp.com
That code was based on the PCRE dictionary contributed by:
Andrew McNamara
andrewm@connect.com.au
connect.com.au Pty. Ltd.
Level 3, 213 Miller St
North Sydney, NSW, Australia
Adopted and adapted by:
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
REGEXP_TABLE(5)