Quote:
Originally posted by carverrn
Well if you filtered outgoing messages I don't think you'd ever be able to send something from "cv@mydomain.co.uk" because it would keep going to the "CVs Sent" folder. So I don't think that's what you had in mind.
You would be mostly right with regards to the BCC'd message counting towards your bandwidth usage. The would probably only be an issue for heavy bandwidth users but your point is valid.
However, there is an exception to that rule. Messages from one Runbox address to another Runbox address do not use up your bandwidth because it never actually leaves the Runbox servers.
Now I'm not sure if that exception works for domains hosted at Runbox. Since they would be hosted by the same server I would think that it would still be true. So if "mydomain.co.uk" is hosted by Runbox the BCC'd message should never leave the Runbox servers and therefore not count towards your bandwidth usage.
But even if it doesn't apply there is still a way. Just BCC the message to your Runbox address or an alias. The message would still have the "From" address of "cv@mydomain.co.uk"
Regards,
Rich
|
Hi Rich,
Thanks for that. Perhaps filter is the wrong word. As for the domain, it is hosted by 123reg. That way I can use three separate email services as back up. Runbox, Eumex and Gmail. Each address on the domain "filters" to a corosponding lable or folder in all three accounts. Thart way I can minimise the risk o losing any mail. I know that 123reg are the potential weak point but there is no perfect system and based on the last years performance of the big 4 email providers as far as this forum is concerned I have reservations about relying on just one provider. 123reg has been hosting my domains for both email and web hosting for the last 3 years and I have yet to catch them out!
I will try the system of BCC and see how much it affects the bandwidth. If it becomes a problem then I will just BCC to runbox and leave the "From" address the same. Infact why don't I just do that anyway? Alright , I will then!