Author Topic: Multi relayhost MTA  (Read 3996 times)

ichat

  • Zen Hero
  • *****
  • Posts: 795
  • Karma: +28/-16
  • RTFM!
    • View Profile
Re: Multi relayhost MTA
« Reply #15 on: November 09, 2012, 01:40:45 pm »
once again im going on a wild gues, but im assuming that your implementation is tricky.. runing your own mailserver this way   seams to me like your trying to implement  a 'pop proxy / imap  proxy'   (just google it)..

while your current setup in fact is just an authorative mailserver  on a domain that it doesn't own),  witch obviously is mutch like what you expect from a 'spammer'  (not that you are one obviously).


solving this on the client side, (configuering your groupware to use these acounts over imaps://  )..  would probaly be the easiest...    even if that client is a webbased one.
All tips hints and advices are based on my personal experience.
As I try my best to be as accurate as possible, following my advice is always at your own risk,
I claim absolutely NO responsibility in any way!

christian

  • Guest
Re: Multi relayhost MTA
« Reply #16 on: November 09, 2012, 01:44:03 pm »
Why "groupware"  :o why Zarafa  :o   ???

Handling multiple identity is simple mail client configuration. Even roundcube can do it if you don't want to use plain mail client.

Krisztián Czakó

  • Zen Apprentice
  • *
  • Posts: 25
  • Karma: +5/-0
    • View Profile
    • Zentyal Gold Partner in Hungary
Re: Multi relayhost MTA
« Reply #17 on: November 10, 2012, 11:24:30 am »
Hi,

In my understanding mappy wants some mail routing in Zentyal, something like this:
- if mail goes to istruzione.it, route mail to smtp.istruzione.it (or an other smtp server, this is just an example)
- if mail goes to scuola.it, route mail to smtp.scuola.it
- in other case route all mails to some other relay server

This can be set up in Postfix, but Zentyal has no interface for this function at this moment.

Regards,
Krisztián

christian

  • Guest
Re: Multi relayhost MTA
« Reply #18 on: November 10, 2012, 11:38:48 am »
I "almost" share this understand but wonder why such requirement especially for public MTA.
What I mean if that you may want to achieve this kind of specific routing internally but when sending mails outisde, why would you want to replace what MX DNS record is supposed to do?

I wrote "almost" because I think is goal is slightly different, rather something like this:
- if sender mail address is istruzione.it, relay mail to smtp.istruzione.it
- if sender mail address is scuola.it, relay mail to smtp.scuola.it

Mappy, could you please confirm what you exactly want to achieve ?