I have a mail server specifically for sending email from Koha and other
services I host, but I'm just one email domain.
My point is that some of your customers may already have an email server /
service you could use for sending email.
On Mon, Feb 13, 2017 at 10:56 AM, SUZUKI Arthur
Erratum :
At least SPF is indeed needed so as to be able to send mail for a domain and
being recognized as legitimate user.
Otherwise mail is accepted by Gmail/Hotmail/etc but thrown to the Spam folder.
Sorry for my mistake and good luck to you.
Arthur
Le 13 février 2017 16:50:30 UTC+01:00,
It has nothing to do with SPF, DKIM and such gadget (though it may help).
Google wants your mail host to have consistent reverse-dns records (ptr).
Which means :
host [your ip address]
should gives such results :
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases:
[your ip
> My server is available at something like myserver.libriotech.no.
> Should KohaAdminEmailAddress (which is used for From by default) be
> libr...@myserver.libriotech.no or just libr...@libriotech.no?
Depends on your exact configuration. Both domains may go the same ip address.
Also check your
Hi Magnus,
We had this issue too and the way to solve it is that your customer's
server must "announced" that your Koha server can send email it their
behalf.
There is usually 2 ways to do so (you must do both)
*SPF - Sender Policy Framework*
*DKIM - DomainKeys Identified Mail*
Digital
Thanks Marcel!
I'll definitely give this a try!
On 13 February 2017 at 11:44, Marcel de Rooy wrote:
> As a workaround: Use real library email address in ReplyToDefault and
> ReturnpathDefault.
> Use the real server domain in the From address like library@[yourserver]
As a workaround: Use real library email address in ReplyToDefault and
ReturnpathDefault.
Use the real server domain in the From address like library@[yourserver]
Should cover most cases. As a fallback, autoforward eventual replies at the
From address to the library. (Now you are only "in
Hi!
I run Koha for several customers, and a number of them have email
enabled. The sender of these emails is set to be the email of the
library in question, e.g. libr...@example.org.
Now, the problem is that services like GMail and Hotmail are not
accepting these emails, because they see them as