BODY { font-family:Arial, Helvetica, sans-serif;font-size:12px; }
Dear Friends,
I am receiving too many spams to lists so that i need to allow only
mydomain users should send mail to lists.
How can i restrict.
Kindly Advice.
Regards,
Jagan.
-------------------------
Msg sent via @Mail - http://atmail.com/From leo@??? Sun Dec 23 14:50:41 2007
Envelope-to: exim-users@???
Received: from student.dicea.unifi.it ([150.217.9.14]:57619)
by tahini.csx.cam.ac.uk with esmtp (Exim 4.69)
(envelope-from <leo@???>) id 1J6S9y-0001eI-Ay
for exim-users@???; Sun, 23 Dec 2007 14:50:41 +0000
Received: from leo by student.dicea.unifi.it with local-esmtp (Exim 4.63 #1
(Debian)) id 1J6S9x-0001Ea-Cq; Sun, 23 Dec 2007 15:50:33 +0100
Date: Sun, 23 Dec 2007 15:50:33 +0100 (CET)
From: Leonardo Boselli <leo@???>
To: Phil Pennock <exim-users@???>
In-Reply-To: <20071223052041.GA79908@???>
Message-ID: <Pine.LNX.4.21.0712231539050.3424-100000@???>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset?-ASCII
X-ASMTP: leo
X-Spam-Score: -1.7 (-)
X-Spam-Status: No, score?.7 required~0 tests?L?.187,
BAYES_00?.5 autolearnO version^1.8
Cc: exim-users@???
Subject: Re: [exim] bouncing message, improper configuration of server.
X-BeenThere: exim-users@???
X-Mailman-Version: 2.1.7
Precedence: list
List-Id: A user list for the exim MTA <exim-users.exim.org>
List-Unsubscribe: <http://lists.exim.org/mailman/listinfo/exim-users>,
<mailto:exim-users-request@exim.org?subject?subscribe>
List-Archive: <http://lists.exim.org/lurker/list/exim-users.html>
List-Post: <mailto:exim-users@exim.org>
List-Help: <mailto:exim-users-request@exim.org?subject?lp>
List-Subscribe: <http://lists.exim.org/mailman/listinfo/exim-users>,
<mailto:exim-users-request@exim.org?subject?bscribe>
X-List-Received-Date: Sun, 23 Dec 2007 14:50:41 -0000
On Sat, 22 Dec 2007, Phil Pennock wrote:
> So you can rotate all you like; provided that you retry from the same IP
> at least once, more than 10 minutes after the first attempt from that
> IP, then it will go through.
I just had this section in each of the server;s configration, of course
the fallback host is the next in the line.
Of course this is useful if one server cannot connect, usally for network
congestion, to a determinate remoe server, and rathere than waith and
retry would immediately pass the burden to another (physical or virtual)
server that uses a different routing (and so a different IP).
In this case the arrangement speed thing up, also because the last server
in the chain is an olt machine whose purpose is only to retry (but only
after the third try).
In the case of a 4xx error the rule is "try later, will be more luky", not
the dreaded "Please hold to maintain your priority" neither "try later,
but from the same IP".
Am i wrong ?
what is the ratio between messages delayed due a network/server overload
(in wich case my way usually speed up things) and message delayed due to
greylisting (that anyway would create an "istititional" delay) ??
lookuphost:
driver nslookup
domains ! +local_domains
pass_on_timeout
self ?ail
fallback_hosts mx3.domai.in
transport remote_smtp
no_more
>
> --
> ## List details at http://lists.exim.org/mailman/listinfo/exim-users
> ## Exim details at http://www.exim.org/
> ## Please use the Wiki with this list - http://wiki.exim.org/
>
>
