Hello Am 24.03.25 um 15:06 schrieb Felix Oberst ([email protected]):
Hello everybody,one of my clients got the following problem (SOGo 5.11.2) * Appointment from <external [email protected]> * <[email protected]> delegates this appointment to <[email protected]> * SOGo tries to send an email with the appointment to <userB> with th sender address <external [email protected]> postfix.log:Mar 24 12:39:25 localhost xxxxxxxx[847]: Mar 24 12:39:25 xxxxxxxx postfix/sogo/smtpd[xxxxxxx]: NOQUEUE: reject: RCPT frommailcowdockerized-sogo-mailcow-1.mailcowdockerized_mailcow- network[172.22.1.248]:553 5.7.1 <external [email protected]>: Sender address rejected: not owned by user <[email protected]>; from= <external [email protected]> to= <[email protected]> proto=ESMTP helo=<xxxxxx> * -> userA is not allowed to send mails from <external [email protected]>. The appointment is still added to userBs calendar. But he does not get informed via mail. * Expected Behavior: SOGo sends/forwards emails for delegated appointments from the current logged in account email adress. Any suggestions?
Sorry, but SOGo can do nothing about that.The Standard states, that the FROM: address of such messages has to be the events owner address.
This "problem" can only be fixed in your SMTP server postfix.Postfix does not accept the email, because its FROM: address does not match a valid address of userA.
You can use a dedicated SMTP account for automated messages like email alarms.
See SOGoSMTPMasterUserUsername and SOGoSMTPMasterUserPassword in sogo.conf. And allow only that account to send as whoever it likes.But this will not help in your case, as delegation is done manually by the user.
Kind regards, Christian Mack -- Christian Mack Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre, Infrastruktur 78457 Konstanz +49 7531 88-4416
smime.p7s
Description: Kryptografische S/MIME-Signatur
