[Koha] Koha Emails

[Paul A]

On 2018-07-31 08:22 AM, vinod mishra wrote:
> There is chances of attack/spam through your Koha server, however gmail
> always block such automated emails after some time as per my observation.
[snip]
> On Tue, Jul 31, 2018 at 5:45 PM, Hira Akram <hira.akram at almusnet.com> wrote:
>> I Checked and it is showing too many login attempts in log that’s why
>> google server has blocked emails from this account. In Gmail account, it is
>> showing too many random emails on invalid accounts. But I haven’t sent
>> these through Koha or anything. Is it possible that koha sent these emails
>> automatically??

This is not a Koha problem. Do you use DKIM and SPF? If so you can 
*perhaps* contact gmail for a solution. See 
<https://support.google.com/mail/answer/6227174>, specifically 
"authentication domain".

In a nutshell, email deliverability to gmail is getting very complicated 
-- they handle billions of pieces of email/day, and (since at least 
2015) have radical protection/rejection practices after even the most 
minor "sniff" of UBE -- and this could well not be *you* but some other 
user in a bigger block of IP space that has a bad reputation.

Your logs show "(delivery temporarily suspended: connect to 
smtp.gmail.com[74.125.24.109]:587: Connection timed out)" which looks 
like tar-pitting. Unless you have an experienced email technician on 
staff, you could have problems. Once your (or whoever owns your block of 
IP space) "reputation" is hurt, it's not easy to get delisted.

Good luck -- Paul





[snip]
>>
>> example is shown here.
>> ---------
>> # tail -f /var/log/mail.log
>> Apr 28 11:20:03 gechlibrary postfix/smtpd[4449]: disconnect from
>> localhost[127.0.0.1]
>> Apr 28 11:20:32 gechlibrary postfix/smtp[4451]: connect to smtp.gmail.com
>> [74.125.24.108]:587: Connection timed out
>> Apr 28 11:20:32 gechlibrary postfix/smtp[4452]: connect to smtp.gmail.com
>> [74.125.24.109]:587: Connection timed out
>> Apr 28 11:21:02 gechlibrary postfix/smtp[4451]: 9BE0E7805B6: to=<
>> xyz at gmail.com>, relay=none, delay=60, delays=0.12/0/60/0, dsn=4.4.1,
>> status=deferred (connect to smtp.gmail.com[74.125.24.109]:587: Connection
>> timed out)
>> Apr 28 11:21:03 gechlibrary postfix/smtp[4452]: connect to smtp.gmail.com
>> [74.125.24.108]:587: Connection timed out
>> Apr 28 11:21:03 gechlibrary postfix/smtp[4452]: C7A8F7805E6: to=<
>> xyz at gmail.com>, relay=none, delay=60, delays=0.07/0.01/60/0, dsn=4.4.1,
>> status=deferred (connect to smtp.gmail.com[74.125.24.108]:587: Connection
>> timed out)
>> Apr 28 11:21:03 gechlibrary postfix/smtp[4453]: connect to smtp.gmail.com
>> [74.125.24.108]:587: Connection timed out
>> Apr 28 11:21:03 gechlibrary postfix/smtp[4453]: E4358780614: to=<
>> pqrs at gmail.com>, relay=none, delay=60, delays=0.07/0.01/60/0, dsn=4.4.1,
>> status=deferred (connect to smtp.gmail.com[74.125.24.108]:587: Connection
>> timed out)
>>
>> firewall was blocked, and because of this reason, status = deferred was
>> appeared in mail log.
>>
>> #mialq
>>
>> 18308780A2A      918 Sat Apr 28 10:40:03  root at localhost
>> (delivery temporarily suspended: connect to smtp.gmail.com[74.125.24.109]:587:
>> Connection timed out)