Emmanuel Salinas wrote:
> Hi there.. I'm still can't startup my exim..
>
> I found this script and I have some question about it...
>
> source /etc/init.d/functions
> on slackware.. Which is my "source"???
Slackware doesn't have function library hanging around (I had to
restrict myself from s
Hi there.. I'm still can't startup my exim..
I found this script and I have some question about it...
source /etc/init.d/functions
on slackware.. Which is my "source"???
#!/bin/sh
# Begin /etc/init.d/exim
#
# Include the functions declared in the /etc/init.d/functions file
#
source /etc/ini
It also looks like I can use:
bash-2.03# exim -be '${if
match_domain{foo.abc.com}{abc.com:*.abc.com}{true}{false}}'
true
bash-2.03# exim -be '${if
match_domain{abc.com}{abc.com:*.abc.com}{true}{false}}'
true
To: [EMAIL PROTECTED]
cc:
Subject:Re: [exim] match_domain question
On Sat, Oct 06, 2007 at 01:48:45AM +1000, Ted Cooper wrote:
> Graeme Fowler wrote:
> > On Fri, 2007-10-05 at 08:15 +0200, Magnus Holmgren wrote:
> >> Errm. ? 40.8 says (about the QUIT ACL) that "You do not need to have a
> >> final
> >> accept", and logically the same should apply to the not-QUIT
On Fri, Oct 05, 2007 at 08:38:12AM -0700, [EMAIL PROTECTED] wrote:
> exim -be '${if match_domain{foo.abc.com}{abc.com}{true}{false}}'
>
> return:
> false
That is the correct result.
Now, this may be what you are looking for:
exim -be '${if match_domain{foo.abc.com}{*.abc.com}{true}{false}}'
>
> Why does:
>
> exim -be '${if match_domain{foo.abc.com}{abc.com}{true}{false}}'
>
> return:
>
> false
>
Probably down to a little confusion in what a "domain" is. In your example both
foo.abc.com and abc.com are domains and they're not equivalent. If what you
want is a test
to determine wh
[EMAIL PROTECTED] wrote:
> Why does:
>
> exim -be '${if match_domain{foo.abc.com}{abc.com}{true}{false}}'
>
> return:
>
> false
>
> ???
Because "foo.abc.com" != "abc.com".
Try
${if match_domain{foo.abc.com}{*.abc.com}{true}{false}}
--
The Exim Manual
http://www.exim.org/docs.html
http://www
On 10/5/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Why does:
>
> exim -be '${if match_domain{foo.abc.com}{abc.com}{true}{false}}'
>
> return:
>
> false
>
> ???
because domain IS foo.abc.com !!!
or did you mean "[EMAIL PROTECTED]" ?
--
Daniele Santi.o.
[EMAIL PROTECTED]..o
Graeme Fowler wrote:
> On Fri, 2007-10-05 at 08:15 +0200, Magnus Holmgren wrote:
>> Errm. § 40.8 says (about the QUIT ACL) that "You do not need to have a final
>> accept", and logically the same should apply to the not-QUIT ACL. It's only
>> explicit denys that are forbidden (at least by the imp
Why does:
exim -be '${if match_domain{foo.abc.com}{abc.com}{true}{false}}'
return:
false
???
--
## 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/
I have this basically in one of my filter files:
nano nano /etc/virtual/domainname.com/filter
if
$h_X-Spam-Status: contains "Yes,"
then
if
$local_part is "username"
then
save /home/username/Maildir/.INBOX.spam/new/ 660
else
save /home/username/imap/$domain
--On 4 October 2007 08:48:05 -0400 Jeff Boehlke <[EMAIL PROTECTED]>
wrote:
> Since then, I have changed again and gone with the method listed below.
> Now my queue lengths are usually under 200 messages which is much better.
> Perhaps this is the best I can do, I suppose I should let it run for
On Fri, 2007-10-05 at 08:15 +0200, Magnus Holmgren wrote:
> Errm. § 40.8 says (about the QUIT ACL) that "You do not need to have a final
> accept", and logically the same should apply to the not-QUIT ACL. It's only
> explicit denys that are forbidden (at least by the implementation). And by
> th
Magnus Holmgren wrote:
> On tisdagen den 18 september 2007, Marcin Krol wrote:
>> I'm not sure this the right place for this proposal, but here it goes:
>>
>> Searching specifically docs only on exim.org is rather inconvenient. The
>> same site hosts this mailing list, which often is not what the u
Jørgen Giversen skrev:
> Tony Finch skrev:
>
>> On Thu, 4 Oct 2007, sysadm wrote:
>>
>>
>>> The problem is the "for [EMAIL PROTECTED]; ons, 03 okt 2007 17:01:28
>>> +0200" line As you can see it should have been Wed, 03 Oct 2007 instead
>>> of ons, 03 okt 2007 which is a Danish date stam
15 matches
Mail list logo