How to send invitation email using a default FROM

[daniele_piagges]

Hi!

I've installed a 3.4d version of Alfresco for a customer of mine. I need to configure Alfresco Share to use a default FROM when sends invitation emails. How can I set it? I googled a bit but I cannot found anything about it.
Could you help me?

Thanks in advance
Daniele Piaggesi

[cheffilet]

Have you tried to change in you alfresco-global.properties following line?

[email protected]
‍‍‍

[gozvakond]

Hi Cheffilet!

I've ran into some problems with e-mail invitations. I've managed to get it working with my gmail acount. But I'd like to use my department's own mailing system (porfix+policyd).

Let [email protected] be the dedicated alfresco outbound account, while the inviting user's mail is [email protected] and the invited user has  [email protected].

The outbound testmail arrives from [email protected], and it seems like it is working.
However when I try to send invitation with user ([email protected]) it fails.
I'll cite the postfix logs, but the same can be found in alfresco logs also:

postfix/smtpd[21859]: NOQUEUE: reject: RCPT from alfresco.mydept.tld[x.x.x.x]: 553 5.7.1 <[email protected]>: Sender address rejected: not owned by user  [email protected]; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<alfresco>

So it seems like Alfresco tries to send with [email protected] account authentication with [email protected] as sender. Which is rejected as [email protected] account should not send in the name of other accounts. (strict anti-spam rule but I won't change it).

setting is:

[email protected]‍

I would like to set this account to be the sender of all invitation e-mails. Perhaps daniela had similar problems.
I think Alfresco should not try to send in the name of other accounts. It has its own to do this.

Notice:
The source code of invitation emails from gmail do not show any sign of altered sender field, but I suppose the gmail SMTP server changes the whole header of the mail and replaces the from field to that of the authenticating user's, while accepting all type of senders after successful smtp auth. A few years ago I had some problems from this behaviour.

Regards,
Gőzvakond