Hi,
On Wed, 22 Sep 1999, Philip Hazel wrote:
> On Wed, 22 Sep 1999, Sven Callender wrote:
>
> > Now the Management has had a new idea: Exim shall send a Message to
> > the original recipent telling him/her that a message was "blocked" due
> > to the size.
>
> That shouldn't be necessary. If Exim has refused a message because of
> the size, whatever was trying to send the message to Exim should be the
> thing that constructs the error message and sends it back.
Exim blocks it here in our machine. So the mail isn't refused on the
smtp-level but later in the procesing.
(This is ok, as local users shall be able to get big mails.
Only Users on the other hosts to wich we send on shall have a max message
size.)
Here a bit of logfile:
---
1999-09-21 21:46:37 11TOVS-0006FP-00 <= Lucy@???
H=somedomain.co.uk [200.128.26.58] P=esmtp S=26221931
id=61782B2F1BB5D111985800A0248A513A9547D8@???
1999-09-21 21:46:37 11TOVS-0006FP-00 ** user@???
R=hub_route T=hub_route_transport: message is too big (transport limit =
20000000)
1999-09-21 21:46:38 11TVs5-00054z-00 <= <> R=11TOVS-0006FP-00 U=root
P=local S=107344
1999-09-21 21:46:38 11TOVS-0006FP-00 Error message sent to
Lucy@???
1999-09-21 21:46:38 11TOVS-0006FP-00 Completed
---
Now Lucy@??? has gotten a errormessage.
The task now is that user@??? gets one too,
telling him that s.b. has send him big mail wich wasn't
transported further.
Background:
This is not for the Bandwith reasons, but for the Users
exeding their Disk-quota (no, unfortunatly I can't check that
on the Mailhost) when reading their Mail etc. This gives
some ugly Problems.
Cu,
sven
