I thought about that, then realized that I could just use the sendmail transport and my "local" postfix could just relay it to the one requiring authentication. I obviously also needed to have the SOGo host in mynetworks there with some permit_mynetworks in smtpd_sender_restrictions and smtpd_recipient_restrictions etc.
Just having this with the SMTP transport didn't work because authing in the webinterface of SOGo started failing. Also, sending mail in Outlook with OpenChange didn't work with it just giving up after "EHLO" for some reason... might have been a different issue, last week is a total blur, but using the sendmail transport solved all my mail-sending issues at least. // Mattias * Marcel Waldvogel (mar...@wanda.ch) wrote: > Mattias, > > can you make Postfix listen on another port for SOGo, where only SOGo is > allowed to login and where reject_sender_login_mismatch is not active? > > -Marcel > > > Am 10.11.2014 um 10:42 schrieb Mattias Fliesberg > > <mattias.fliesb...@chas.se>: > > > > Hi, > > > > We have a postfix server with... > > > > smtpd_sender_restrictions = reject_sender_login_mismatch > > > > This means that the user we use for the sogo-ealarms-notify cronjob can't > > send > > as all the other users. Is there a way to make SOGo not try to send "From" > > the > > organizer? > > > > If not, how have other people with this kind of setup solved this issue? > > > > Thanks, > > // Mattias > > -- > > users@sogo.nu > > https://inverse.ca/sogo/lists > -- users@sogo.nu https://inverse.ca/sogo/lists
