On Wed, Aug 21, 2013 at 08:48:43PM +0200, Denis Fondras wrote: > Hi Eric ! > > > Your problem is that there is no rule that handles [email protected], so > > the whole expansion fails. You might want to add a catch-all relay > > rule. > > > > Ok, I thought "accept from { 127.0.0.0/8 192.168.20.254/32 ::1/128 > 2001:7A8:B5AD:20::1000/128 } for any relay" was that catch-all rule.
I didn't see that in your config. All you need is an "accept for any ..." rule at the end of your config file. This matches all mails originating from this machine, including forwarded mails (aliases and .forward). It also matches mails enqueued on authenticated sessions. So if you also want to relay for other networks or addresses, I advise you to make it another rule explicitely. It is a lot more cleaner and less error-prone. > Won't a more open rule change my server into an open-relay ? Not as long as you don't specify "accept from any for any", or "accept from any_publically_reachable_iface_or_address for any". Eric. -- You received this email because you are subscribed to the "[email protected]" list To unsubscribe, send mail with subject: [[email protected]] unregister
