Chris Purves wrote:
Thank you for your reply. When I first started the post I hadn't
considered that the cause of the problem was firewalling or interception
of my messages, but that is what it appears to be, so it is not a
problem with exim.
One tends to forget what is not 'in your face'.
On Tue, 4 Apr 2006 22:05:09 +0100, Tony Finch <[EMAIL PROTECTED]> wrote:
>On Tue, 4 Apr 2006, Marc Haber wrote:
>> May I ask for the patch?
>
>http://www.exim.org/mail-archives/exim-cvs/2006-April/msg8.html
Thanks, applied to Debian's 4.61-1.
Too bad that pipermail insists on mangling patches
Thank you for your reply. When I first started the post I hadn't
considered that the cause of the problem was firewalling or interception
of my messages, but that is what it appears to be, so it is not a
problem with exim.
W B Hacker wrote:
Chris Purves wrote:
*trimmed*
My server (as wel
Stanislaw Halik wrote:
hello,
exiscan-acl works really well, except for one thing i'm not able to
figure out. $spam_report contains a large, verbose message with excerpts
from bodies and individual rule scoring.
is there a way to only fetch the rule scoring part or is matching it by
a regexp t
hello,
exiscan-acl works really well, except for one thing i'm not able to
figure out. $spam_report contains a large, verbose message with excerpts
from bodies and individual rule scoring.
is there a way to only fetch the rule scoring part or is matching it by
a regexp the only method?
-- sh
p
On Tue, 4 Apr 2006, Jeremy Harris wrote:
Jason Keltz wrote:
How can retry timeout be exceeded?
Exim replied to the original sender with a message
SMTP error from remote mail server after RCPT TO:<[EMAIL PROTECTED]>:
host x.x.x [#.#.#.#]: 450 <[EMAIL PROTECTED]>:
Recipient address
Phil Pennock wrote:
> Did you run "make makefile" in Exim's top-level directory after changing
> the OS makefile?
Stupid of me, I should have thought about that earlier. Works perfectly.
Thanks.
Regards,
Oliver
--
## List details at http://www.exim.org/mailman/listinfo/exim-users
##
On 2006-04-04 at 18:25 +0200, Oliver Heesakkers wrote:
> In the dev-mailinglist I found mention of such an error at the release
> of the RC-1 for Exim-4.61. One solution offered was to add "-lutil" to
> "LIBS=" in OS/Makefile-FreeBSD. This did not solve my problem.
-lutil should be correct.
Did y
On Tue, 4 Apr 2006, Dermot Paikkos wrote:
>
> So my aliases router returns an address without the server part
> (fine) and then sends it off to the primary MX to resolve.
>
> What I had hoped for was for it to return joe and use $home (or
> similar) for the maildrop.
The usual setup is to do the m
Jason Keltz wrote:
How can retry timeout be exceeded?
Exim replied to the original sender with a message
SMTP error from remote mail server after RCPT TO:<[EMAIL PROTECTED]>:
host x.x.x [#.#.#.#]: 450 <[EMAIL PROTECTED]>:
Recipient address rejected: Greylisted: retry timeout exceed
On Tue, 4 Apr 2006, Marc Haber wrote:
>
> May I ask for the patch?
http://www.exim.org/mail-archives/exim-cvs/2006-April/msg8.html
Tony.
--
<[EMAIL PROTECTED]> <[EMAIL PROTECTED]> http://dotat.at/ ${sg{\N${sg{\
N\}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}\
\N}{([^N
Hi.
We're running exim 4.52.
One of our users sent a message to a site that is configured with
greylisting, and I'm not sure that I understand the log details:
The message went out:
2006-04-03 15:45:26 1FQUzO-0006Jo-4J <= [EMAIL PROTECTED] H=([8.9.10.11])
[8.9.10.11] P=esmtpsa X=TLSv1:AES25
Marc Haber wrote:
On Wed, 29 Mar 2006 11:14:03 +0100, "Jason Meers"
<[EMAIL PROTECTED]> wrote:
Usual Permissions required on Exim Binaries
owner: root, group: root, permissions: 4755 (suid root)
Correct for /usr/sbin/exim4. The other exim related binaries are
root:root 755 as usual.
Usua
Hi
Exim version 4.50 with maildir support.
I am trying to set-up a mail system using Exim/pop3 but am having
trouble figuring out how to make set up the /etc/aliases.
For the pop3 auth all the users will be added to /etc/passwd and so
might be considered local users.
I thought that I could u
On Tue, 4 Apr 2006 18:10:25 +0100, Tony Finch <[EMAIL PROTECTED]> wrote:
>On Tue, 4 Apr 2006, Dean Brooks wrote:
>> 2006-04-04 11:42:25 Exim configuration error in line 590 of
>> /usr/local/exim/config: error in ACL: ACL error: negation is not allowed
>> with "acl"
>
>This is a bug in the impleme
On Wed, 29 Mar 2006 11:14:03 +0100, "Jason Meers"
<[EMAIL PROTECTED]> wrote:
>Usual Permissions required on Exim Binaries
>owner: root, group: root, permissions: 4755 (suid root)
Correct for /usr/sbin/exim4. The other exim related binaries are
root:root 755 as usual.
>Usual Permissions required o
On Tue, Apr 04, 2006 at 06:10:25PM +0100, Tony Finch wrote:
> On Tue, 4 Apr 2006, Dean Brooks wrote:
> > 2006-04-04 11:42:25 Exim configuration error in line 590 of
> > /usr/local/exim/config: error in ACL: ACL error: negation is not allowed
> > with "acl"
>
> This is a bug in the implementation
On Wed, 29 Mar 2006 10:49:58 +0200, "Remco Zwaan" <[EMAIL PROTECTED]>
wrote:
>I have installed exim4 on my debian-distroand I want to use exim4 to
>forward all mail to a exchange 2003 server.
The Debian config has a hubbed_hosts router that can be used to do
this. The documentation is right ab
On Tue, 4 Apr 2006, Dean Brooks wrote:
>
> 2006-04-04 11:42:25 Exim configuration error in line 590 of
> /usr/local/exim/config: error in ACL: ACL error: negation is not allowed with
> "acl"
This is a bug in the implementation of the new add_header feature - some
of the tables are not in alphabe
Marc Haber wrote:
Debian uses a sub-ACL to exclude sender e-mail addresses and sender IP
addresses from a number of ACL checks, and the notation of "!acl" has
been a convenient and intuitive way of specifying this behavior.
Wasn't aware of that capability. Do see the value.
If it were my
Hi,
I downloaded the new Exim-4.61.tar.gz to three of my FreeBSD-systems
(5.3, 5.4 and 6.0, all RELEASE and up to date).
All three of them fail the build at this point:
[code]
gcc -o exim
transports/transports.a(pipe.o)(.text+0x33): In function
`pipe_transport_setup':
: undefined reference to `l
On Tue, 4 Apr 2006 15:28:39 +0100 (BST), Philip Hazel
<[EMAIL PROTECTED]> wrote:
>I have just put Exim release 4.61 on the primary ftp site:
>
> ftp://ftp.csx.cam.ac.uk/pub/software/email/exim/exim4/exim-4.61.tar.gz
> ftp://ftp.csx.cam.ac.uk/pub/software/email/exim/exim4/exim-4.61.tar.bz2
>
>-
>
Hi,
Just compiled Exim 4.61 and received the following error on our existing
configuration:
2006-04-04 11:42:25 Exim configuration error in line 590 of
/usr/local/exim/config: error in ACL: ACL error: negation is not allowed with
"acl"
The relevant line of configuration is:
warn ! acl = sen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have just put Exim release 4.61 on the primary ftp site:
ftp://ftp.csx.cam.ac.uk/pub/software/email/exim/exim4/exim-4.61.tar.gz
ftp://ftp.csx.cam.ac.uk/pub/software/email/exim/exim4/exim-4.61.tar.bz2
-
-
On Tue, 4 Apr 2006, David Saez Padros wrote:
> yes, but in this particular case this does not matter as the acl is
> only used for informational purposes. Maybe having something like
> control = no_defer or +ignore_defer could be useful in that situations
> where is more important to accept messa
Hi !!
But +ignore_unknown on its own won't stop a defer because when a DNS
lookup gives a temporary error, you don't know if the host is unknown or
not. Consider a major network failure that causes lots of nameservers
are unreachable...
yes, but in this particular case this does not matter as
On Tue, 4 Apr 2006, David Saez Padros wrote:
> ok, but what about +ignore_unknown ? dns_again_means_nonexist is ok
> for a workaround but not for every day use (as i have to detect which
> domains have problems and manually add them to that list). It's
> +ignore_unknown suposed to make the conditi
hi
In order to enable smtp authentification via cyrus-sasl we have compile
exim-4.60 with this specifications
AUTH_CYRUS_SASL=yes
AUTH_CRAM_MD5=yes
AUTH_LIBS= -lsasl2
CYRUS_SASLAUTHD_SOCKET= /var/state/saslauthd/mux
After our install, we add the following line to exim configure file in order
On Tue, 4 Apr 2006, Chris Thompson wrote:
> W B Hacker <[EMAIL PROTECTED]> writes:
> > But TWX and Telex are no longer a factor, and X.400 not far
> > behind - outside of a few specialty organizations.
>
> Indeed, I was interested to see that RFC 4450 ("Getting Rid of the
> Cruft: Report from an E
Hi !!
I think I have now discovered what the problem is. The option
dns_again_means_nonexist was applying to direct DNS lookups, but not
when Exim was using gethostbyname() (or equivalent). Thinking about
this, I've decided that in fact it *should* apply in that case because
temporary errors
W B Hacker <[EMAIL PROTECTED]> writes:
[...]
> But TWX and Telex are no longer a factor, and X.400 not far
> behind - outside of a few specialty organizations.
Indeed, I was interested to see that RFC 4450 ("Getting Rid of the
Cruft: Report from an Experiment in Identifying and Reclassifying
O
A short while ago, On Tue, 4 Apr 2006, I wrote:
> Is that the complete debug output? I cannot reproduce this effect when
> testing.
I think I have now discovered what the problem is. The option
dns_again_means_nonexist was applying to direct DNS lookups, but not
when Exim was using gethostbyn
I'm not positive this will help you, but it seems to address your issue.
My company has issues resolving some dns names as well. What they asked me
to do is have a static name -> ip table for typically problem domains. You
may want to do this, but in opposite order, so if dns fails, a backup
stati
On Mon, 3 Apr 2006, Ian Eiloart wrote:
> You can't whitelist a mail domain because anyone can use it.
> However, if you could tie down the legitimate servers for a domain
> that you trust, then you could whitelist those servers (at least for
> mail from that domain). That's what SPF lets you do
On Thu, 30 Mar 2006, David Saez Padros wrote:
> It also looks like dns_again_means_nonexist has little effect
> and does not solve the problem:
>
> > > > check hosts = +ignore_unknown : *.$sender_address_domain
> :$sender_address_domain : ${lookup dnsdb{>:
> defer_never,mxh=$sender_address_doma
On 2006-04-03T08:05+0100 Peter Bowyer wrote:
> You could ask the owner of the server, perhaps - its their error
> message after all.
It turned out that my host was limited me to 100 messages an hour. If I
exceeded that my account was disabled and under review. They've bumped
it up to 500 messages
36 matches
Mail list logo