Re: Problem with mail queue
- From: "jmaimon@xxxxxxxx" <jmaimon@xxxxxxxx>
- Date: 22 Mar 2007 06:58:02 -0700
On Mar 22, 6:15 am, Res <r...@xxxxxxxxxx> wrote:
On Thu, 22 Mar 2007, Chuck Rock wrote:
Since the largest single cause of chocked outgoing queues is fates
punishment for generating email blowback, please ensure you have done
everything to limit that.
Blowback is defined as mail sent in response to abuse/spam email, with
the vast majority going to forged and/or unreachable destinations. To
eliminate this, all effort should be focused on moving rejections into
the smtp protocol conversation.
I'm thinking this is very common in my setup. The three servers are
pre-scanners for my destination servers. The problem is there is no way to
communicate whether or not an address is valid or not at this point. I don't
If these servers scan mail and pass onto another mail server that actually
delivers mail into /var/spool/mail for the users, use milter-ahead
backchatter/blowback whatever you want to call it, will not only
cause backlogs, but also result in blacklistings.
--
Cheers
Res
Let Novell known what you think of their back door deal with the devil.
Sign the petition today: http://techp.org/p/1/
milter-ahead is only one possible solution of many.
Here is my full list.
There is many more than one way to skin this cat, in lieu of a
published FAQ entry , here is my oft posted list.
----------
"How do I let my mx gateway server recognize which recipients are
valid
on the final destionation/next hop server and which are not?"
Which has hit the newsgroup so frequently it really needs to be a faq
entry.
The short answers are:
*
Use ldap routing
see cf/README section titled LDAP ROUTING
http://www.sendmail.org/m4/ldap_routing.html
(LDAP routing doesnt actually require LDAP, it will work with
predumped and precompiled maps, perhaps created by cron job)
*
Use virtusertable with undocumented feature and an entry for each
valid user and a catchall entry that @domain.com error:nouser
_VIRTUSER_STOP_ONE_LEVEL_RECURSION_
*
Use virtusertable with a RHS of "!" for each valid user and a
catchall entry that @domain.com error:nouser
*
Use access db with undocumented feature (pre sendmail 8.14.0)
define(`_RELAY_FULL_ADDR_', `1')
And put all your users in there
To:u...@xxxxxxxxxxx RELAY
Ensure that all other relaying is denied for that domain.
*
Use access db with documented feature "relaytofulladdress" (post
sendmail 8.14.0)
FEATURE(`access_db', `hash -T<TMPF> /etc/mail/
access_map',`relaytofulladdress')
And put all your users in there
To:u...@xxxxxxxxxxx RELAY
Ensure that all other relaying is denied for that domain.
*
use a milter of which there are several.
milter-ahead
j-chkmail
mimedefang
dnsbl
callahead-milter
milter-sav
A list of milters is available at
http://www.jmaimon.com/sendmail/milters
.
- Follow-Ups:
- Re: Problem with mail queue
- From: Chuck Rock
- Re: Problem with mail queue
- From: Res
- Re: Problem with mail queue
- References:
- Re: Problem with mail queue
- From: Chuck Rock
- Problem with mail queue
- From: Chuck Rock
- Re: Problem with mail queue
- From: Grant Taylor
- Re: Problem with mail queue
- From: Chuck Rock
- Re: Problem with mail queue
- From: jmaimon@xxxxxxxx
- Re: Problem with mail queue
- From: Res
- Re: Problem with mail queue
- Prev by Date: Re: FEATURE(`require_rdns') : 451 reaction to FORGED [WHY?]
- Next by Date: TLS by Domain
- Previous by thread: Re: Problem with mail queue
- Next by thread: Re: Problem with mail queue
- Index(es):
Relevant Pages
|