On 02/13/2013 03:24 PM, Noel Jones wrote:
[snip]
A few choices...
- Don't use a relayhost, deliver mail directly. This requires you have a
static IP address with proper FCrDNS entries, which will require
cooperation from your ISP and may cost some extra, depending on your
current service agreement.
- If you only have a handful of addresses, you can sign up for a free
google apps account with your own domain name. That will allow you to
relay through google. You are not required to use google as your MX; you
can continue to use your own server. If you have too many for the free
service, you might consider paying.
- Use some third-party relayhost service, such as dyndns. This will not
be free, but shouldn't cost very much. If you have more than a couple
dozen email addresses, this will be cheaper than a google apps account.
-- Noel Jones
[snip]
I finally went with dyndns. Low cost for the volume we have and easy to
setup.
But since the price is volume based I was thinking of splitting the
outgoing trafficbetween my ISP and dym.com
I thought of using relayhost to my ISP by default and use fallback_relay
when the ISP failed. However the documentation of fallback_relay
mentions only that it kicks in when then main relay fails. In my case I
want to use it when it bounces the mail for the wrong reason (reason why
I went with dyn.com in the first place):
Feb 4 14:20:57 www postfix/smtp[6592]: 6CF7EA41F89:
to=<servic...@dominio.com>, relay=smtp.movistar.es[213.4.149.228]:25,
delay=3.4, delays=0.15/0.01/0.26/3, dsn=5.2.0, status=bounced (host
smtp.movistar.es[213.4.149.228] said: 552 5.2.0 wDHP1k00B3cN3cx1hDHPt5
internal error ??. 6007 (in reply to end of DATA command))
Would it work ?
Dominique
