public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: kashani <kashani-list@badapple.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Setting up SMTP relay
Date: Sun, 23 Jan 2011 17:22:09 -0800	[thread overview]
Message-ID: <4D3CD441.6010206@badapple.net> (raw)
In-Reply-To: <201101240226.24738.alan.mckinnon@gmail.com>

On 1/23/2011 4:26 PM, Alan McKinnon wrote:
> Apparently, though unproven, at 02:02 on Monday 24 January 2011, kashani did
> opine thusly:
>
>> On 1/23/2011 12:20 PM, Alan McKinnon wrote:
>>> It manages it's own queues beautifully. But, and this makes me sad, it
>>> doesn't really want *me* to manage it's queues. Border controls are
>>> hard, and finding the 1,000 mails some idiot with a Windows bot just
>>> sent, and deleting them, is really hard.
>>>
>>> I'm redesigning our mail setup at work,a nd I'm going to do it with exim
>>> *and* Postfix. Exim is the front end I can see, work with, and manage.
>>> Exim sends on to Postfix as fast as it can, and Postfix transparently
>>> relays to recipient. I get best of both worlds :-)
>>
>> 	I can't say I've ever needed anything more than mailq | grep |awk  |
>> postsuper -d - in order to delete mail from the Postfix queues. What
>> sort of things are your trying to do other than delete a lot of spam or
>> bounces?
>
> First, our internal mail system deals with about 3,000,000 mails a day Mon-Thu
> so grep | postsuper is a tad inadequate, even if just on the basis of volume
>
> The basic tools are fine as long as you understand what they are dealing with
> - raw text. As soon as you run mailq you have text, you no longer have
> intelligence about what that text means. So you need lots of grep-fu.
>
> I can't control what the users mail out, sometimes they have automated systems
> that do silly things like send 10,000 notifications an hour to an SMS gateway
> when they cocked up Nagios. Finding the dodgy ones is no fun when there's a
> lot of perfectly valid ones in the mix too, and grep doesn't help much other
> than blindly selecting text matches.
>
> There's lots more examples, but they all follow a similar theme.
>

	Thanks for the extra detail, I found what you're describing very 
interesting. I've never dealt with Postfix with more than a couple 
hundred internal users and more often as spam our customers system. 
Other than the occasional Nagios blasts I haven't had to deal with much 
of this.
	In regards to controlling what users send is it feasible to use a 
policy server for rate limiting them? The ability to use an extra lookup 
service to decide whether to access main, filter it, allow relay, etc is 
one of the things I think Postfix does well. However I suspect the 
management and hand holding of a rate limit system would create more 
overhead than cleaning out the queue periodically.

kashani



  reply	other threads:[~2011-01-24  1:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-22 21:34 [gentoo-user] Setting up SMTP relay Alex Schuster
2011-01-22 22:01 ` kashani
2011-01-23 19:23   ` Alex Schuster
2011-01-23 19:56     ` kashani
2011-01-23 20:20       ` Alan McKinnon
2011-01-23 20:48         ` [gentoo-user] " walt
2011-01-23 21:04           ` Alan McKinnon
2011-01-24  0:02         ` [gentoo-user] " kashani
2011-01-24  0:26           ` Alan McKinnon
2011-01-24  1:22             ` kashani [this message]
2011-01-24  7:00               ` Mick
2011-01-24  7:24                 ` Alan McKinnon
2011-01-24  7:06               ` Alan McKinnon
2011-02-05 14:37     ` Alex Schuster
2011-01-26  4:04 ` Walter Dnes
2011-01-26  6:46   ` Mick
2011-01-26  9:07     ` Stroller
2011-01-26 16:52       ` kashani
2011-01-28 23:48         ` Stroller

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=4D3CD441.6010206@badapple.net \
    --to=kashani-list@badapple.net \
    --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