On Mon, Sep 05, 2011 at 21:45:00 +0100, Nigel Metheringham wrote:
I have just made 2 changes to the list configurations on exim.org:-
1. Monthly list reminders have been switched off.
It has been a long time since these were considered best
practice, and routinely sending out
exim doesn't have any builtin way to count number of elements.
Recently there are spams with From like this:
From: a...@1.pl, b...@2.pl, c...@3.pl
To: a...@1.pl, b...@2.pl, c...@3.pl
so few addresses in From list.
Looking for something like:
deny message = you are bad
condition = ${if
On 5 Sep 2011, at 22:04, Moritz Wilhelmy wrote:
Is VERP really such a big issue? I thought it's a lot cheaper if you let
exim do it, rather than mailman?
Its a lot cheaper on (queue) disk space, but still costs you bandwidth and
transmission time. I have not tested our lists recently to see
Hello *,
my exim get`s the message
421 4.3.2 The maximum number of concurrent connections has exceeded a limit,
closing transmission channel
when delivering to an exchange system.
Can I do something or must the exchange admin increase the limit
on his Receive Connector?
On Tue, Sep 6, 2011 at 1:11 AM, Arkadiusz Miskiewicz ar...@maven.pl wrote:
exim doesn't have any builtin way to count number of elements.
Yeah, would be nice. For your particular query, there is a recipient
count, but not a sender count, which is what you want.
Looking for something like:
I keep receiving this on my log and i am not sure how to stop it. is
this something i should worry about ?
2011-09-06 18:43:03 1R0d9I-0002kV-7k ** zkoquh12...@yahoo.com.br
R=dnslookup T=remote_smtp: SMTP error from remote mail server after
end of data: host mta5.am0.yahoodns.net [66.94.237.64]:
On 2011-09-06 17:24, Face wrote:
I keep receiving this on my log and i am not sure how to stop it. is
this something i should worry about ?
That depends. Why are you mailing these nonexistent addresses?
--
Jeremy
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
##
Face wrote:
I keep receiving this on my log and i am not sure how to stop it. is
this something i should worry about ?
Probably.
Digging out the root cause, and setting aside the more innocent ones, it
appears that you have more going on than just the odd expired
destination address and
Today, OpenSSL issued a security advisory:
http://www.openssl.org/news/secadv_20110906.txt
OpenSSL is one of the two available implementations of the TLS protocol
in Exim. The other is GnuTLS. In the output of { exim -bV } is a line
Support for:; if it does not include OpenSSL then you are
http://www.exim.org/exim-html-current/doc/html/spec_html/filter_ch03.html
the bottom RIGHT link (Next) has:-
http://www.exim.org/exim-html-current/doc/html/spec_html/filter_ch04.html
but I continually get a 404 error.
The requested URL was not found on this server. The link on the
referring
On 2011-09-07 at 00:58 +0100, Always Learning wrote:
http://www.exim.org/exim-html-current/doc/html/spec_html/filter_ch03.html
the bottom RIGHT link (Next) has:-
http://www.exim.org/exim-html-current/doc/html/spec_html/filter_ch04.html
but I continually get a 404 error.
There is no
Mailing list emails sent to me show a 30 minute delay at Tahini.
---
Phil's email about OpenSSL (Tue, 6 Sep 2011 16:55:55 -0400):-
Received: from tahini.csx.cam.ac.uk ([131.111.8.192]:50541) by
m2.u226.com
with esmtp (Exim 4.63) (envelope-from
My originating email in this thread took 38 minutes and 25 seconds.
Received: from tahini.csx.cam.ac.uk ([131.111.8.192]:33649) by
m2.u226.com
with esmtp (Exim 4.63) (envelope-from
exim-users-bounces+exim=u61.u22@exim.org) id
1R17FD-0001Cw-Ah for
e...@u61.u22.net;
Phil's email about a 404 error (Tue, 6 Sep 2011 21:11:04 -0400) took 40
minutes and 6 seconds to be processed by tired and exhausted Tahini.
Received: from tahini.csx.cam.ac.uk ([131.111.8.192]:51027) by
m2.u226.com
with esmtp (Exim 4.63) (envelope-from
On Wed, 2011-09-07 at 03:04 +0100, Always Learning wrote:
Phil's email about a 404 error (Tue, 6 Sep 2011 21:11:04 -0400) took 40
minutes and 6 seconds to be processed by tired and exhausted Tahini.
Wow ! That took just 9 seconds to be processed by Tahini - the fastest
time ever observed.
On 07/09/11 12:09, Always Learning wrote:
On Wed, 2011-09-07 at 03:04 +0100, Always Learning wrote:
Phil's email about a 404 error (Tue, 6 Sep 2011 21:11:04 -0400) took 40
minutes and 6 seconds to be processed by tired and exhausted Tahini.
Wow ! That took just 9 seconds to be processed
16 matches
Mail list logo
