Russell Nelson <nelson@crynwr.com> writes:
>Greg Andrews writes:
> > Russell Nelson <nelson@crynwr.com> writes:
> > >Patrick Michael Kane writes:
> > > >
> > > > I'm interested in disabling remote deliveries in qmail. Anything not
> > > > destined for the localhost should bounce. Is there an easy way to do
> > > > this?
> > >
> > >Hmmm... You could do it by setting control/concurrencyremote to 0,
> > >and control/queuelifetime to 3600. Remote mail would bounce within
> > >the hour.
> >
> > Where would it bounce to if you can't run any concurrent remote
> > deliveries? Wouldn't it simply double-bounce to postmaster after
> > five days?
>
>Hmmm.... That would only happen to mail arriving from off-system
>(presumably via SMTP) that bounced. The bounce would never get out.
>No, local bounces would simply be returned to the sender, who has a
>local address, and whose deliveries are controlled by
>concurrencylocal.
>
Under the circumstances, I wonder if it wouldn't be better to
replace qmail-rspawn or qmail-remote with a script that would
trigger a bounce. It's a more direct (and more immediate)
path to the solution than zeroing concurrencyremote.
A non-qmail-specific solution would be to put the host behind a
firewall that blocked outgoing SMTP connections via a packet
filter (yet still allowed other traffic, including incoming
SMTP connections). That would also block local users who try
to bypass the ban on outgoing mail.
-Greg
--
Greg Andrews West Coast Online
Unix System Administrator 5800 Redwood Drive
gerg@wco.com Rohnert Park CA 94928
(yes, 'greg' backwards) 1-800-WCO-INTERNET
>Greg Andrews writes:
> > Russell Nelson <nelson@crynwr.com> writes:
> > >Patrick Michael Kane writes:
> > > >
> > > > I'm interested in disabling remote deliveries in qmail. Anything not
> > > > destined for the localhost should bounce. Is there an easy way to do
> > > > this?
> > >
> > >Hmmm... You could do it by setting control/concurrencyremote to 0,
> > >and control/queuelifetime to 3600. Remote mail would bounce within
> > >the hour.
> >
> > Where would it bounce to if you can't run any concurrent remote
> > deliveries? Wouldn't it simply double-bounce to postmaster after
> > five days?
>
>Hmmm.... That would only happen to mail arriving from off-system
>(presumably via SMTP) that bounced. The bounce would never get out.
>No, local bounces would simply be returned to the sender, who has a
>local address, and whose deliveries are controlled by
>concurrencylocal.
>
Under the circumstances, I wonder if it wouldn't be better to
replace qmail-rspawn or qmail-remote with a script that would
trigger a bounce. It's a more direct (and more immediate)
path to the solution than zeroing concurrencyremote.
A non-qmail-specific solution would be to put the host behind a
firewall that blocked outgoing SMTP connections via a packet
filter (yet still allowed other traffic, including incoming
SMTP connections). That would also block local users who try
to bypass the ban on outgoing mail.
-Greg
--
Greg Andrews West Coast Online
Unix System Administrator 5800 Redwood Drive
gerg@wco.com Rohnert Park CA 94928
(yes, 'greg' backwards) 1-800-WCO-INTERNET