Using dnslists - how can I tell the difference between a failed lookup
and a lookup that succeeded but returned no information?
Thanks in advance
--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this li
On Thu, 12 Mar 2009 12:09:29 -0700 Shane W wrote:
> Hello all,
>
> In attempting to setup SMTP auth against DoveCot, I am
> getting a protocol error from Exim and nothing from
> DoveCot. I've googled a couple posts on this but no
> solutions as yet. Exim is v4.69, DC is v1.1.11. Here is
> the t
Mike Cardwell wrote:
> Patrick Okui wrote:
>
>>> Interesting. It uses "touch" to create files on the filesystem to use as
>>> a "database". Reminds me of the "${touch{path}}" patch I submitted to
>>> exim-dev in August 2007.
>>>
>>> http://www.mail-archive.com/exim-...@exim.org/msg01975.html
>> I
Mike Cardwell wrote:
> Marc Perkel wrote:
>
>
Thanks - I have what I need for that step in the process.
parse_uri:
warn set acl_c_parse_lookup = ${sg{$acl_c_parse_uri}{\N .*\s\N}{}}
set acl_c_parse_lookup = ${sg{$acl_c_parse_lookup}{ }{}}
set acl
Marc Perkel wrote:
>>> Thanks - I have what I need for that step in the process.
>>>
>>> parse_uri:
>>>warn set acl_c_parse_lookup = ${sg{$acl_c_parse_uri}{\N .*\s\N}{}}
>>>set acl_c_parse_lookup = ${sg{$acl_c_parse_lookup}{ }{}}
>>> set acl_c_parse_uri = ${sg{$acl_c_parse_uri}
Mike Cardwell wrote:
> Marc Perkel wrote:
>
>
>> Thanks - I have what I need for that step in the process.
>>
>> parse_uri:
>>warn set acl_c_parse_lookup = ${sg{$acl_c_parse_uri}{\N .*\s\N}{}}
>>set acl_c_parse_lookup = ${sg{$acl_c_parse_lookup}{ }{}}
>> set acl_c_parse_uri
Patrick Okui wrote:
>> Interesting. It uses "touch" to create files on the filesystem to use as
>> a "database". Reminds me of the "${touch{path}}" patch I submitted to
>> exim-dev in August 2007.
>>
>> http://www.mail-archive.com/exim-...@exim.org/msg01975.html
>
> I get a 404 when I try to foll
On Mar 12, 2009, at 1:33 PM, Mike Cardwell wrote:
> Interesting. It uses "touch" to create files on the filesystem to
> use as
> a "database". Reminds me of the "${touch{path}}" patch I submitted to
> exim-dev in August 2007.
>
> http://www.mail-archive.com/exim-...@exim.org/msg01975.html
I g
>
> I have a script that cleans out any greylist files older then 6 hours.
> The greylist directory seems to peak at about 60k files. df -i says
> I am using 1 percent of my inodes. Also, since this is Maildir based
> system I may very well save inodes due to less mail volume.
>
> Matt
>
Our
> -Original Message-
> From: Mike Cardwell [mailto:exim-us...@lists.grepular.com]
> Sent: 12 March 2009 10:34
> To: Exim Mailing List
> Subject: Re: [exim] DbLessGreyListing
>
> Matt wrote:
> > Is anyone using this greylisting implementation?
> >
> > http://wiki.exim.org/DbLessGreyListi
Quoting Sander Smeenk (ssme...@freshdot.net):
> > >local_parts = ^[.] : ^...@%!/|]
> > How to read this?
> Starting with a single dot, or starting with @, %, !, / or |.
> The : is a delimiter in this 'list' of local_parts.
>
> > Am I right?
> No :-) Read 'man regexp' and 'man pcre'
Quoting Mihamina Rakotomandimby (R12y) (miham...@lab.vectoris.fr):
> >local_parts = ^[.] : ^...@%!/|]
> How to read this?
Starting with a single dot, or starting with @, %, !, / or |.
The : is a delimiter in this 'list' of local_parts.
> Am I right?
No :-) Read 'man regexp' and 'm
Matt wrote:
> Is anyone using this greylisting implementation?
>
> http://wiki.exim.org/DbLessGreyListingRun
>
> I am testing with it and after doing some tweaks to get it to work on
> my server all seems well. It seems to be super simple implementation
> and simple to implement. What I wonder
Marc Perkel wrote:
> Thanks - I have what I need for that step in the process.
>
> parse_uri:
>warn set acl_c_parse_lookup = ${sg{$acl_c_parse_uri}{\N .*\s\N}{}}
>set acl_c_parse_lookup = ${sg{$acl_c_parse_lookup}{ }{}}
> set acl_c_parse_uri = ${sg{$acl_c_parse_uri}{\N^.*?\s\N
Sorry,
Yes I am getting that line
2009-03-12 17:26:34 [23173] 1LhcUk-00061B-7k Completed QT=24s
This is an intermittent issue. It has only occurred with a few email.
I've added logging to dovecot for "deleted" and "moved" messages, so I
will have a better idea if the users client is deleting
Patrick Okui wrote:
>denymessage = Restricted characters in address
>domains = +local_domains
>local_parts = ^[.] : ^...@%!/|]
How to read this?
Deny messages where the localpart:
- begins with a ".", or
- contains ":", or
- contains "@" or "%" or "!"
Heiko Schlittermann (Do 12 Mär 2009 09:50:49 CET):
> *Iff* you have the "Completed" line, you shouldn't ask exim anymore
> about your mail :)
Better: you should inspect the transport, may be the mail is in some
place where you do not expect it. (And exim can't know what you're
expecting.)
Are yo
Space Ship Traveller (Do 12 Mär 2009 09:31:02
CET):
> Hi,
>
> I've received an email today according to the logs (I've xxx ed out
> sensitive data):
>
> 2009-03-12 17:26:34 [23137] 1LhcUk-00061B-7k <= l...@xxx.com H=xxx
> (mail.xxx.com) [x.x.x.x]:xxx I=[x.x.x.x]:25 P=esmtps
> X=TLS1.0:DHE
Hi,
I've received an email today according to the logs (I've xxx ed out
sensitive data):
2009-03-12 17:26:34 [23137] 1LhcUk-00061B-7k <= l...@xxx.com H=xxx
(mail.xxx.com) [x.x.x.x]:xxx I=[x.x.x.x]:25 P=esmtps
X=TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32 CV=no DN="" S=520859
id=h06a00052400.12
19 matches
Mail list logo
