Bowie Bailey wrote:
> Sam Varshavchik wrote:
> > Bowie Bailey writes:
> > 
> > > Sam Varshavchik wrote:
> > > > Bowie Bailey writes:
> > > > 
> > > > > I just set up a new server and it is accepting mail to
> > > > > over-quota accounts and letting it sit in the mailq.  I think
> > > > > this is a permissions problem. What do I need to do so that
> > > > > Courier can reject mail with a 4xx if the account is over
> > > > > quota? 
> > > > 
> > > > The current version of Courier, under its default settings, will
> > > > accept one message to an overquota account, which will sit in
> > > > the mailq, but all further messages to this address will get
> > > > turned away with a 4xx, until such time that the message in the
> > > > mail queue gets delivered.
> > > 
> > > That's not what I'm seeing.  I have not seen a single quota
> > > rejection in my maillog.  One of my over-quota users has six
> > > messages in the queue right now.
> > 
> > That's why wrote "under its default settings".
> > 
> > > All I see in the log is repeated "maildir over quota" and "status:
> > > deferred" messages coming from courierlocal.
> > > 
> > > Are there any permissions issues that could be involved?  Where
> > > are the settings that control this behavior?
> > 
> > The BOFHSUPPRESSBACKSCATTER setting in the bofh configuraton file,
> > and the ESMTP_BLOCKBACKSCATTER in the courierd configuration file.
> 
> Ok, I did have this disabled in the courierd configuration.  I had
> forgotten about that.
> 
> I'm still not sure why this affects quota checking.  The description
> of the ESMTP_BLOCKBACKSCATTER setting only mentions dropping DSNs.  It
> says nothing about accepting or rejecting other messages.
> 
> I changed that setting back to default and did a "courier restart".
> I was still able to drop three more messages into the queue for my
> user (via non-auth smtp).  What am I missing?

After quite a bit of digging and poking, I think I figured out what's
going on.

I do see the "456 Address temporarily unavailable" rejections from the
backscatter suppression routines.  My testing was flawed because my
test emails came from within our network.  Since our network is
flagged as "allow,RELAYCLIENT" in smtpaccess, it apparently bypasses
the backscatter suppression.  When I tested from an outside address,
it worked as expected.

The user who has several emails in the queue was someone who had a
second account forwarding to him via maildrop.  I switched this one to
an alias which should avoid this problem in the future.  I guess I'm
going to need to modify my administration program to handle creating
and modifying aliases as well as maildrop forwards.  The one thing I
really like about forwarding via maildrop is that I can tell who was
the real recipient of the messages.  If I use an alias, the recipient
address is rewritten and it can be impossible to tell which address
the message was actually sent to.

I'm still not sure what I think of the backscatter suppression logic.
The idea of dropping DSNs just bugs me for some reason.  Unless the
rejection is due to virus or spam blocking, a DSN needs to be sent.

I'm also not too fond of the "456 Address temporarily unavailable"
message from an over-quota account.  I would much rather have the
message specifically state that the user is over quota.  This way the
sender and recipient can figure out (and maybe solve) the problem
without having to call me to ask why they are getting this error
message.  I would also really prefer that Courier simply not accept
mail if the account is over quota.  There is no need to involve the
backscatter logic, just reject it at the door.

Sorry if I'm sounding a bit negative today.  The backscatter/quota
thing was something that came up when I made my new server live.  I
didn't run into it in testing.  Right now, I'm just trying to
understand exactly what it is doing and figure out the best way to
configure it.  I have read all of the documentation I can find on this
topic and I would appreciate hearing your thoughts on these issues.

Thanks!

-- 
Bowie


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to