Marc Perkel <[EMAIL PROTECTED]> writes: > Yes it does break email forwarding because if you have restrictive SPF and it > gets forwarded then the forwarding server > isn't a valid server. Thus if the receiving server enforces SPF rules then it > bounces the forwared message.
No. Once it has been accepted by the MX MTA for the addressee domain it has been delivered to the address "on the envelope". What the addressee, or his organisation, does to get it into the final recipient's mailbox should be a purely internal matter for the addressee's domain. It should not be of any concern to the original sender who has delivered the mail to the address 'advertised' by the recipient. It is the recipient who wants the mail forwarded to a different mailbox, so the recipient should take responsibility for ensuring that it is delivered, which should include handling any delivery problems. If the sender sends a mail to [EMAIL PROTECTED] who forwards it to [EMAIL PROTECTED] and the forwarding fails, the original sender does not want to receive an NDR from example.net saying that joe is over quota as (s)he did not send a mail to [EMAIL PROTECTED] and may not be able to tell that it is the mail which was sent to [EMAIL PROTECTED] which has not be delivered.
