[Tickets #12678] Incorrect sender address for e-mail notifications

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12678
------------------------------------------------------------------------------
  Ticket             | 12678
  Created By         | arjen+horde at de-korte.org
  Summary            | Incorrect sender address for e-mail notifications
  Queue              | Kronolith
  Version            | 4.1.3
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


arjen+horde at de-korte.org (2013-09-12 18:40) wrote:

When e-mail notifications are used, the sender address will be set to  
the same value as the recipient address. This is not a problem if the  
(optional) e-mail address to be used is left blank. But if one uses a  
different address, this fails if either the sending mailserver Horde  
uses verifies if a user is allowed to use an address or if the  
recipients mailserver does SPF checking for instance and the  
recipients domain is restrictive.

My mailserver checks if senders are allowed to use an address and the  
following shows up in the mailserver logs when I attempt to send  
notifications to 'whoever at example.com':

2013-09-12T15:20:00.821854+02:00 mail postfix/smtpd[7360]: Anonymous  
TLS connection established from localhost[127.0.0.1]: TLSv1 with  
cipher ECDHE-RSA-AES256-SHA (256/256 bits)
2013-09-12T15:20:00.858909+02:00 mail postfix/smtpd[7360]: NOQUEUE:  
reject: RCPT from localhost[127.0.0.1]: 553 5.7.1  
<whoever at example.com>: Sender address rejected: not owned by user  
arjen; from=<whoever at example.com> to=<whoever at example.com> proto=ESMTP  
helo=<mail.de-korte.org>
2013-09-12T15:20:00.907869+02:00 mail dovecot: imap-login: Login:  
user=<arjen>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=7445,  
secured, session=<1mJcmC/m6gB/AAAB>

A much better option for setting the sender address would be the  
default e-mail address of the owner of the calender.