Thanks for idea but it won't work for me as 'internal domains' can be anything, including gmail.com (and i don't know which of them are really internal/local, this is decided by sending SMTP everytime something is sent, based on MX records). Problem is that Dovecot/Sieve is using wrong SMTP server (one used for receiving e-mails which should NEVER be used for sending [and is never is, except sieve]). Cit?t "KOCIK Fabien (Acoss)" <fabien.kocik at acoss.fr>:> Hi, > > I had the same problem and solved it at architectural design level. > > Instead of forcing Sieve to use a different SMTP server, I declared > some transports in the sending SMTP server to force it to route > internal domains directly to receiving SMTP server without going to > the Internet. > So, internal mails remains on internal network and there is only one > SMTP server for all mail traffic. > > Sorry, I know that I don't answer directly to the original question. > But in the context, may be an idea ? > > Regards. > Fabien > > -----Message d'origine----- > De?: dovecot <dovecot-bounces at dovecot.org> De la part de azurit at pobox.sk > Envoy??: vendredi 24 janvier 2020 12:39 > ??: Dovecot Mailing List <dovecot at dovecot.org> > Objet?: Vacation use different SMTP server > > Hi, > > in our setup, we have two SMTP servers: > - one for receiving messages (this one is using Dovecot's LMTP for > delivery) > - one for sending messages (this one is used by our users as > outgoing SMTP server) > > Only the first one has list of local domains, local e-mail accoutns > etc. so the second one will ALWAYS use MX records for delivery - > with this setup, we can allow to our users to add any domain to > their accounts (for example, if someone will add gmail.com and > create e-mail accounts on it, it's complete safe because we will > never deliver mail for gmail.com locally). The only problem seems to > be vacation messages (maybe other messages send by sieve), as > Dovecot is using the first SMTP server for sending. > > My questions: Can i set different SMTP server for sieve messages? > How exactly is Dovecot/Sieve choosing which SMTP server will be used? > > Thanks. > > azur
Really no more info? Cit?t azurit at pobox.sk:> Thanks for idea but it won't work for me as 'internal domains' can > be anything, including gmail.com (and i don't know which of them are > really internal/local, this is decided by sending SMTP everytime > something is sent, based on MX records). Problem is that > Dovecot/Sieve is using wrong SMTP server (one used for receiving > e-mails which should NEVER be used for sending [and is never is, > except sieve]). > > > > > > Cit?t "KOCIK Fabien (Acoss)" <fabien.kocik at acoss.fr>: > >> Hi, >> >> I had the same problem and solved it at architectural design level. >> >> Instead of forcing Sieve to use a different SMTP server, I declared >> some transports in the sending SMTP server to force it to route >> internal domains directly to receiving SMTP server without going to >> the Internet. >> So, internal mails remains on internal network and there is only >> one SMTP server for all mail traffic. >> >> Sorry, I know that I don't answer directly to the original >> question. But in the context, may be an idea ? >> >> Regards. >> Fabien >> >> -----Message d'origine----- >> De?: dovecot <dovecot-bounces at dovecot.org> De la part de azurit at pobox.sk >> Envoy??: vendredi 24 janvier 2020 12:39 >> ??: Dovecot Mailing List <dovecot at dovecot.org> >> Objet?: Vacation use different SMTP server >> >> Hi, >> >> in our setup, we have two SMTP servers: >> - one for receiving messages (this one is using Dovecot's LMTP for >> delivery) >> - one for sending messages (this one is used by our users as >> outgoing SMTP server) >> >> Only the first one has list of local domains, local e-mail accoutns >> etc. so the second one will ALWAYS use MX records for delivery - >> with this setup, we can allow to our users to add any domain to >> their accounts (for example, if someone will add gmail.com and >> create e-mail accounts on it, it's complete safe because we will >> never deliver mail for gmail.com locally). The only problem seems >> to be vacation messages (maybe other messages send by sieve), as >> Dovecot is using the first SMTP server for sending. >> >> My questions: Can i set different SMTP server for sieve messages? >> How exactly is Dovecot/Sieve choosing which SMTP server will be used? >> >> Thanks. >> >> azur
Op 28-1-2020 om 19:20 schreef azurit at pobox.sk:> Really no more info?You could do something with the sendmail_path or submission_host settings. Regards, Stephan.> > > > > Cit?t azurit at pobox.sk: > >> Thanks for idea but it won't work for me as 'internal domains' can be >> anything, including gmail.com (and i don't know which of them are >> really internal/local, this is decided by sending SMTP everytime >> something is sent, based on MX records). Problem is that >> Dovecot/Sieve is using wrong SMTP server (one used for receiving >> e-mails which should NEVER be used for sending [and is never is, >> except sieve]). >> >> >> >> >> >> Cit?t "KOCIK Fabien (Acoss)" <fabien.kocik at acoss.fr>: >> >>> Hi, >>> >>> I had the same problem and solved it at architectural design level. >>> >>> Instead of forcing Sieve to use a different SMTP server, I declared >>> some transports in the sending SMTP server to force it to route >>> internal domains directly to receiving SMTP server without going to >>> the Internet. >>> So, internal mails remains on internal network and there is only one >>> SMTP server for all mail traffic. >>> >>> Sorry, I know that I don't answer directly to the original question. >>> But in the context, may be an idea ? >>> >>> Regards. >>> Fabien >>> >>> -----Message d'origine----- >>> De?: dovecot <dovecot-bounces at dovecot.org> De la part de >>> azurit at pobox.sk >>> Envoy??: vendredi 24 janvier 2020 12:39 >>> ??: Dovecot Mailing List <dovecot at dovecot.org> >>> Objet?: Vacation use different SMTP server >>> >>> Hi, >>> >>> in our setup, we have two SMTP servers: >>> ?- one for receiving messages (this one is using Dovecot's LMTP for >>> delivery) >>> ?- one for sending messages (this one is used by our users as >>> outgoing SMTP server) >>> >>> Only the first one has list of local domains, local e-mail accoutns >>> etc. so the second one will ALWAYS use MX records for delivery - >>> with this setup, we can allow to our users to add any domain to >>> their accounts (for example, if someone will add gmail.com and >>> create e-mail accounts on it, it's complete safe because we will >>> never deliver mail for gmail.com locally). The only problem seems to >>> be vacation messages (maybe other messages send by sieve), as >>> Dovecot is using the first SMTP server for sending. >>> >>> My questions: Can i set different SMTP server for sieve messages? >>> How exactly is Dovecot/Sieve choosing which SMTP server will be used? >>> >>> Thanks. >>> >>> azur > > >