Marco Gaiarin (Di 15 Sep 2015 22:20:05 CEST):
> Mandi! Jeremy Harris
> In chel di` si favelave...
>
> >> But, there's no way to set some variable 'acl_mX' in 'acl_check_rcpt:'
> >> based
> >> on recipient?
> > Certainly there is. Now, what will you do when there is a second
> > recipient?
>
Mandi! Jeremy Harris
In chel di` si favelave...
>> But, there's no way to set some variable 'acl_mX' in 'acl_check_rcpt:' based
>> on recipient?
> Certainly there is. Now, what will you do when there is a second
> recipient?
I can apply a worst case scenario, for example.
I've tried with:
Mandi! Marco Gaiarin
In chel di` si favelave...
> I have to add 'add_header' line to exim acl?
Answer found. Yes:
http://www.gossamer-threads.com/lists/exim/users/70448
Sorry.
--
La differenza tra una dittatura e una democrazia e' che in democrazia poi
si vedono le foto.
2015-09-15 19:59 GMT+02:00 Jeremy Harris :
> On 15/09/15 18:27, Bjørnar Ness wrote:
>> [snip]
>>
>> If the original rcpt is instead an "alias", that is in my case a alias with a
>> single recipient, then only send autoreply from the final account if no
>> autoreply was sent from the alias...
>>
>>
On 15/09/15 18:27, Bjørnar Ness wrote:
> Yes. This is the intended. If original rcpt was a "list", that is an alias
> with
> multiple recipients (real accounts only, no recursive aliases), then never
> send autoreplies from the backend "account", only from the "list" if it has
> a autoreply config
2015-09-15 13:53 GMT+02:00 Mike Brudenell :
> [snip]
> I can see why this might be useful — eg, an alias-based address <
> sa...@example.com> that fans email out to *N* recipients, but only returns
> an auto-reply ("Thank you for your enquiry…") from the
> front-end address, and not from a Sales T
2015-09-15 16:21 GMT+02:00 Chris Siebenmann :
>> 1) When a bounce/autoreply is generated, is the acl_[cm] variables
>> from the original message available to the routers? If not, could it
>> be (devs?)
Ok, I could do that, but it would actually be very useful (for my,
rather complex setup) if boun
> 1) When a bounce/autoreply is generated, is the acl_[cm] variables
> from the original message available to the routers? If not, could it
> be (devs?)
One workaround for this is to embed any acl_[cm] values you want in
internal X-... headers in the bounce message[*], use them from the headers
i
On Tue, Sep 15, 2015 at 01:54:22PM +0100, Graeme Fowler wrote:
> If you want whistles, buzzers & bells, start here:
>
> https://graemef.wordpress.com/tech-stuff/exim-logstash/
this.
Matthew
--
Matthew Newton, Ph.D.
Systems Specialist, Infrastructure Services,
I.T. Services, Univer
Howdy
On 11 Sep 2015, at 10:35, John wrote:
> Is there an easy way of measuring the number of emails handled by the server
> per unit time? Per day, week, month, ever.
Many, as others have pointed out.
If you want whistles, buzzers & bells, start here:
https://graemef.wordpress.com/tech-stuff/e
I think the request is for…
if (recipient address is an alias) {
if (the alias expands to multiple recipients) {
if (the alias-based address has an auto-reply set up) {
Generate auto-reply from the alias-based address, but not from each of the
recipients expanded from the alias
}
} else {
/*
On 14/09/15 15:33, Bjørnar Ness wrote:
> 1) When a bounce/autoreply is generated, is the acl_[cm] variables
> from the original
> message available to the routers? If not, could it be (devs?)
The routers running the new message? No. It's a new message
and totally independent, in both the bounce
I have a couple questions that I have not been able to find a good
answer to from the documentation.
1) When a bounce/autoreply is generated, is the acl_[cm] variables
from the original
message available to the routers? If not, could it be (devs?)
2) When expanding aliases (in redirect router), I
13 matches
Mail list logo
