From: "Preston Hagar" <prestonh@gmail.com>
To: gentoo-user@lists.gentoo.org, emailgrant@gmail.com
Subject: Re: [gentoo-user] Filtering spam for a business address
Date: Thu, 20 Jul 2006 14:08:08 -0500 [thread overview]
Message-ID: <8f5897560607201208t54e63592mb776a8a3082e028a@mail.gmail.com> (raw)
In-Reply-To: <49bf44f10607181704kb335c6bu41dfd3d604d58c7c@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2073 bytes --]
>
> > http://www.freesoftwaremagazine.com/articles/focus_spam_postfix/
> >
>
> That's a great article. Where do you implement the changes he
> suggests on the first page? I searched /etc/postfix/main.cf for the
> configuration options but they aren't there.
>
> - Grant
> -
Just add them to main.cf and do a /etc/init.d/postfix reload (make sure not
to include the line numbers in his examples)
For the lines that reference external files, you will have to create the
files and the content and the issue the command:
postmap <filename>
The guide puts all of the files in /usr/local/etc/postifx, but I just put
the files in /etc/postfix (If you put the files in /etc/postfix instead of
/usr/local/etc/postfix, make sure to change the path main.cf). I left off
the spf filter since it seems that many people still have not adopted spf.
Postgrey is great and I use it on my person email server, but I left that
off of the business system I manage. I work for a real estate company and
postgrey can delay email by 4 hours or more depending on the sending server
configuration. Although no one should depend on email for speedy delivery,
it is my experience that most users expect it. All of the other options
have really helped a lot and cut down on spam.
A couple of things to remember, each time you change main.cf or any other
postfix configuration file, you need to issue the command:
/etc/init.d/postfix reload
to get postfix to take the new configuration changes.
Also, if you change any of the external files that main.cf refrences, you
need to do a :
postmap <filename>
and then
/etc/init.d/postfix reload
It is probably a good idea to tail your mail logs for a while after you make
the changes just to make sure you are not blocking anything you didn't
intend
to.
tail -f /var/log/mail/current
or
tail -f /var/log/mail.info
depending on your logger.
Also, I would recommend sending email to an account on your new system from
any and all external email accounts you may have such as yahoo or gmail just
for extra testing.
Good Luck,
Preston
[-- Attachment #2: Type: text/html, Size: 2720 bytes --]
prev parent reply other threads:[~2006-07-20 19:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 16:10 [gentoo-user] Filtering spam for a business address Grant
[not found] ` <44BD1CFF.2070306@badapple.net>
2006-07-18 18:03 ` Grant
2006-07-18 18:36 ` kashani
[not found] ` <44BD3CC2.2000501@mid.email-server.info>
2006-07-18 21:42 ` Preston Hagar
2006-07-19 0:04 ` Grant
2006-07-19 0:35 ` kashani
2006-07-20 19:08 ` Preston Hagar [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8f5897560607201208t54e63592mb776a8a3082e028a@mail.gmail.com \
--to=prestonh@gmail.com \
--cc=emailgrant@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox