Don't send undeliverable mail from forward address?

[Richard G]

I don't know how I best could setup the title of this question, so I hope it's oke.

This is the case.
Somebody has email address [email protected] and for this email address there is a forwarder present to [email protected] that's all oke and working.

Now the following happens.
A persone with address [email protected] sends an email to [email protected] which is ofcourse forwarded to [email protected] due to the forwarder he made. But at this point, the mailbox of linda is full.

Now [email protected] gets a return mail with an undeliverable notice, which mentions that mail can't be delivered because the mailbox of [email protected] is full.

As far as I know, this is normal behaviour of a mailserver and it's OK.

Now the customer doesn't like the [email protected] address to be known to another person, so he doesn't want the undeliverable mail from [email protected] to be send to [email protected] (because he only mailed to [email protected] and this is the only email address "somebody" should know). I understand the customer's thoughts, but not all thoughts are possible to create.

Is there a possibility to do this? So that undeliverable mails coming from [email protected] will be send (when that mailbox is full for example) but the undeliverable mail from the forwarded address is not send?

If even possible, this should not be a server wide solution, but only for this customer/domain.

I doubt if it's even possible because it's normal mailserver behaviour, but I promised the customer to ask around, just to be of service to him.

Any thoughts about this?

 

[zEitEr]

Hello Richard,

I hope somebody could help with the issue, but as the most users of the forums might be on holidays (Marry Christmas to you and the others), I would suggest asking it on Exim mailing lists (though they also might be on holidays), as I think this could be done with extra ACL rules only. For now I have no a ready made solution, so you might need to read about ACLs, and check the path of the email before sending out a bounce.

 

[Richard G]

Hello Alex.

Also a Merry Christmas to you an everybody else too!
I know most users will be on holidays or busy with Christmas meals etc. but this question is not really an issue or problem, there is no hurry at all to solve this.
Thank you though for pointing me to ACL's, I didn't think of that and will go and read about it, although I didn't understand much of it last time I tried.

But if the only solution is to make adjustments to the exim.conf then I probably won't do it, because it's only 1 customer asking and it's normal mailserver behaviour.

Thank you for the answer and have nice Christmas days!

 

[nobaloney]

I don't think it could be done without major rewrite of exim.conf, and I don't even know if it's possible then. As you point out, it's the final destination mailbox which is full.

I believe that at best it would require all email go through an exim perl filter sophisticated enough to check all headers to look for evidence of a forward, and then to rewrite headers. Rewriting headers is frowned upon (it's probably against some RFCs) because it makes it impossible to troubleshoot.

Jeff

 

[Richard G]

Thank you Jeff.

I was already afraid of something like that. So in this case I will notify the customer that it's not possible, I already warned him it would probably be impossible.