Greetings.
I am trying to find out if it is possible to support wildcard after
local_part email addresses in Exim4. I.E. <[EMAIL PROTECTED]>. Section 9
of the Exim 4.50 spec seems to indicate that this is not supported for
various types of lookups.
Any help would be apprecaited.
On 19 Jan 2006, at 20:21, Chris Knadle wrote:
On Thursday 19 January 2006 13:55, Tony Finch wrote:
On Thu, 19 Jan 2006, Chris Knadle wrote:
Well, I just became a backup MX for an admin that is using
Postfix
that is making extensive use of these addresses with wildcards
after the
local
On 1/19/06 11:21 AM, "Chris Knadle" <[EMAIL PROTECTED]> wrote:
> On Thursday 19 January 2006 13:55, Tony Finch wrote:
>> On Thu, 19 Jan 2006, Chris Knadle wrote:
>>> Well, I just became a backup MX for an admin that is using Postfix
>>> that is making extensive use of these addresses with wild
On Thursday 19 January 2006 17:41, Giuliano Gavazzi wrote:
> >> Do you mean something like local_part_suffix?
> >
> >Unfortunately I'm not sure what you mean, either. ;-)
>
> do you mean you have not taken the time to lookup your-exim-source-
> dir/doc/spec.txt?
How smug. ;-)
I looked
On Thursday 19 January 2006 18:26, John W. Baxter wrote:
> I'm not sure recipient callout verification is really appropriate here.
> Aside from spammers trying to sneak in (lots of activity), the reason a
> message is presented to the backup MX is that the primary MX is
> unavailable.
Shucks.
On Thu, Jan 19, 2006 at 07:55:23PM -0500, Chris Knadle said:
> On Thursday 19 January 2006 17:41, Giuliano Gavazzi wrote:
> > local_part_suffix = -*
> > local_part_suffix_optional
> >
> > will do what you want for determining what a local_part is, then you
> > can do what lookup you find more suita
On Thursday 19 January 2006 17:41, Giuliano Gavazzi wrote:
> >Then I considered doing email routing with ldap, but that has a
> > similar problem because the time in which wildcards can be used
> > is in the address used for the lookup and not a wildcard in an
> > address that's stored in the d
Chris Knadle wrote:
On Thursday 19 January 2006 17:41, Giuliano Gavazzi wrote:
Then I considered doing email routing with ldap, but that has a
similar problem because the time in which wildcards can be used
is in the address used for the lookup and not a wildcard in an
address that's stored
Consolidating two replies here.
On Thursday 19 January 2006 20:09, Stephen Gran wrote:
> local_part_suffix != local_part_prefix, but both exist.
I believe local_part_prefix is what I mainly need. This plus the example
shown in 46.7 should give me enough information to build a suitable redire
hi!
On Thursday 19 January 2006 19:28, Chris Knadle wrote:
>I am trying to find out if it is possible to support wildcard after
> local_part email addresses in Exim4. I.E. <[EMAIL PROTECTED]>. Section 9
> of the Exim 4.50 spec seems to indicate that this is not supported for
> various types
Chris Knadle wrote:
> I am trying to find out if it is possible to support wildcard after
> local_part email addresses in Exim4. I.E. <[EMAIL PROTECTED]>. Section
> 9 of the Exim 4.50 spec seems to indicate that this is not supported for
> various types of lookups.
Some examples would be nice.
On 20 Jan 2006, at 01:55, Chris Knadle wrote:
Anyway, in a router:
local_part_suffix = -*
local_part_suffix_optional
will do what you want for determining what a local_part is, then you
can do what lookup you find more suitable to determine if a
local_part is valid.
I note that your loca
On Thu, 19 Jan 2006, John W. Baxter wrote:
> On 1/19/06 11:21 AM, "Chris Knadle" <[EMAIL PROTECTED]> wrote:
> > On Thursday 19 January 2006 13:55, Tony Finch wrote:
> >
> >> Alternatively, you could just not bother to maintain a copy of the
> >> userlist and use recipient callout verification inste
On 20 Jan 2006, at 12:19, Tony Finch wrote:
There is a callout cache which should minimize this effect.
I was going to remark that too, but is it going to cache negative
results? I would not say so. Then, what is the use of the cache since
most, if not all, genuine attempts, will happen w
On Fri, 20 Jan 2006, Giuliano Gavazzi wrote:
>
> I was going to remark that too, but is it going to cache negative results? I
> would not say so.
Perhaps you should read the documentation, because it does indeed cache
negative results.
> In other words, how to populate the cache?
Traffic from sp
I'm again pasting several replies together here.
On Friday 20 January 2006 03:21, Klaus Maria Pfeiffer wrote:
> could it be, that the following is helping you?
>
> http://www.exim.org/mail-archives/exim-users/Week-of-Mon-20051212/msg00148.
>html
Before posting to the list I had found this mess
On 20 Jan 2006, at 15:14, Tony Finch wrote:
On Fri, 20 Jan 2006, Giuliano Gavazzi wrote:
I was going to remark that too, but is it going to cache negative
results? I
would not say so.
Perhaps you should read the documentation, because it does indeed
cache
negative results.
well, you
On Thu, 19 Jan 2006, Chris Knadle wrote:
>
>I am trying to find out if it is possible to support wildcard after
> local_part email addresses in Exim4.
In what context? There are probably several ways of achieving what you
want.
Tony.
--
<[EMAIL PROTECTED]> <[EMAIL PROTECTED]> http://dota
On Thursday 19 January 2006 13:36, Tony Finch wrote:
> >I am trying to find out if it is possible to support wildcard after
> > local_part email addresses in Exim4.
>
> In what context? There are probably several ways of achieving what you
> want.
Well, I just became a backup MX for an adm
On Thu, 19 Jan 2006, Chris Knadle wrote:
>
> Well, I just became a backup MX for an admin that is using Postfix that is
> making extensive use of these addresses with wildcards after the local_part.
Do you mean something like local_part_suffix?
Alternatively, you could just not bother to main
On Thursday 19 January 2006 13:55, Tony Finch wrote:
> On Thu, 19 Jan 2006, Chris Knadle wrote:
> > Well, I just became a backup MX for an admin that is using Postfix
> > that is making extensive use of these addresses with wildcards after the
> > local_part.
>
> Do you mean something like loca
21 matches
Mail list logo
