fail2ban custom emby filter

[Marv 9]

Hi,

 

I'm recently having many fail2ban logs errors.

The filter can't find the logs b/c it no longer exist.

2016-12-13 18:21:31,089 fail2ban.server [1820]: INFO    Changed logging target to /var/log/fail2ban.log for Fail2ban v0.8.13

2016-12-13 18:21:31,118 fail2ban.filter [1820]: INFO    Set maxRetry = 3
2016-12-13 18:21:31,119 fail2ban.filter [1820]: INFO    Set findtime = 600
2016-12-13 18:21:31,120 fail2ban.actions[1820]: INFO    Set banTime = 900
2016-12-13 18:21:31,127 fail2ban.jail   [1820]: INFO    Creating new jail 'emby'
2016-12-13 18:21:31,128 fail2ban.jail   [1820]: INFO    Jail 'emby' uses poller
2016-12-13 18:21:31,128 fail2ban.jail   [1820]: INFO    Initiated 'polling' backend
2016-12-13 18:21:31,129 fail2ban.filter [1820]: INFO    Added logfile = /var/lib/emby-server/logs/server-63616969832.txt
2016-12-13 18:21:31,130 fail2ban.filter [1820]: INFO    Added logfile = /var/lib/emby-server/logs/server-63616914796.txt
2016-12-13 18:21:31,132 fail2ban.filter [1820]: INFO    Added logfile = /var/lib/emby-server/logs/server-63617164812.txt
2016-12-13 18:21:31,133 fail2ban.filter [1820]: INFO    Added logfile = /var/lib/emby-server/logs/server-63616905619.txt
2016-12-13 18:21:31,135 fail2ban.filter [1820]: INFO    Added logfile = /var/lib/emby-server/logs/server-63617056237.txt
2016-12-13 18:21:31,137 fail2ban.filter [1820]: INFO    Added logfile = /var/lib/emby-server/logs/server-63616915344.txt
2016-12-13 18:21:31,139 fail2ban.filter [1820]: INFO    Added logfile = /var/lib/emby-server/logs/server-63616914947.txt
2016-12-13 18:21:31,141 fail2ban.filter [1820]: INFO    Added logfile = /var/lib/emby-server/logs/server-63616809673.txt
2016-12-13 18:21:31,143 fail2ban.filter [1820]: INFO    Added logfile = /var/lib/emby-server/logs/server-63616914900.txt
2016-12-13 18:21:31,151 fail2ban.filter [1820]: INFO    Added logfile = /var/lib/emby-server/logs/server-63617169291.txt
2016-12-13 18:21:31,151 fail2ban.filter [1820]: INFO    Set maxRetry = 5
2016-12-13 18:21:31,152 fail2ban.filter [1820]: INFO    Set findtime = 600
2016-12-13 18:21:31,152 fail2ban.actions[1820]: INFO    Set banTime = 900
2016-12-13 18:21:31,166 fail2ban.jail   [1820]: INFO    Jail 'nextcloud' started
2016-12-13 18:21:31,167 fail2ban.jail   [1820]: INFO    Jail 'emby' started
2016-12-13 18:22:37,168 fail2ban.filter [1820]: ERROR   Unable to get stat on /var/lib/emby-server/logs/server-63616914796.txt because of: [Errno 2] No such file or directory: '/var/lib/emby-server/logs/server-63616914796.txt'
2016-12-13 18:22:37,168 fail2ban.filter [1820]: ERROR   Unable to get stat on /var/lib/emby-server/logs/server-63616905619.txt because of: [Errno 2] No such file or directory: '/var/lib/emby-server/logs/server-63616905619.txt'
2016-12-13 18:22:37,168 fail2ban.filter [1820]: ERROR   Unable to get stat on /var/lib/emby-server/logs/server-63616915344.txt because of: [Errno 2] No such file or directory: '/var/lib/emby-server/logs/server-63616915344.txt'
2016-12-13 18:22:37,168 fail2ban.filter [1820]: ERROR   Unable to get stat on /var/lib/emby-server/logs/server-63616914947.txt because of: [Errno 2] No such file or directory: '/var/lib/emby-server/logs/server-63616914947.txt'
2016-12-13 18:22:37,168 fail2ban.filter [1820]: ERROR   Unable to get stat on /var/lib/emby-server/logs/server-63616809673.txt because of: [Errno 2] No such file or directory: '/var/lib/emby-server/logs/server-63616809673.txt'
2016-12-13 18:22:37,168 fail2ban.filter [1820]: ERROR   Unable to get stat on /var/lib/emby-server/logs/server-63616914900.txt because of: [Errno 2] No such file or directory: '/var/lib/emby-server/logs/server-63616914900.txt'
2016-12-13 18:22:38,169 fail2ban.filter [1820]: ERROR   Unable to get stat on /var/lib/emby-server/logs/server-63616914796.txt because of: [Errno 2] No such file or directory: '/var/lib/emby-server/logs/server-63616914796.txt'
2016-12-13 18:22:38,169 fail2ban.filter [1820]: ERROR   Unable to get stat on /var/lib/emby-server/logs/server-63616905619.txt because of: [Errno 2] No such file or directory: '/var/lib/emby-server/logs/server-63616905619.txt'
2016-12-13 18:22:38,169 fail2ban.filter [1820]: ERROR   Unable to get stat on /var/lib/emby-server/logs/server-63616915344.txt because of: [Errno 2] No such file or directory: '/var/lib/emby-server/logs/server-63616915344.txt'
2016-12-13 18:22:38,169 fail2ban.filter [1820]: ERROR   Unable to get stat on /var/lib/emby-server/logs/server-63616914947.txt because of: [Errno 2] No such file or directory: '/var/lib/emby-server/logs/server-63616914947.txt'
2016-12-13 18:22:38,169 fail2ban.filter [1820]: ERROR   Unable to get stat on /var/lib/emby-server/logs/server-63616809673.txt because of: [Errno 2] No such file or directory: '/var/lib/emby-server/logs/server-63616809673.txt'
2016-12-13 18:22:38,169 fail2ban.filter [1820]: ERROR   Unable to get stat on /var/lib/emby-server/logs/server-63616914900.txt because of: [Errno 2] No such file or directory: '/var/lib/emby-server/logs/server-63616914900.txt'
2016-12-13 18:22:39,169 fail2ban.filter [1820]: ERROR   Unable to get stat on /var/lib/emby-server/logs/server-63616914796.txt because of: [Errno 2] No such file or directory: '/var/lib/emby-server/logs/server-63616914796.txt'
2016-12-13 18:22:39,170 fail2ban.filter [1820]: WARNING Too many errors. Setting the jail idle
2016-12-13 18:22:39,170 fail2ban.filter [1820]: ERROR   Unable to get stat on /var/lib/emby-server/logs/server-63616905619.txt because of: [Errno 2] No such file or directory: '/var/lib/emby-server/logs/server-63616905619.txt'
2016-12-13 18:22:39,170 fail2ban.filter [1820]: WARNING Too many errors. Setting the jail idle
2016-12-13 18:22:39,170 fail2ban.filter [1820]: ERROR   Unable to get stat on /var/lib/emby-server/logs/server-63616915344.txt because of: [Errno 2] No such file or directory: '/var/lib/emby-server/logs/server-63616915344.txt'
2016-12-13 18:22:39,170 fail2ban.filter [1820]: WARNING Too many errors. Setting the jail idle
2016-12-13 18:22:39,170 fail2ban.filter [1820]: ERROR   Unable to get stat on /var/lib/emby-server/logs/server-63616914947.txt because of: [Errno 2] No such file or directory: '/var/lib/emby-server/logs/server-63616914947.txt'
2016-12-13 18:22:39,170 fail2ban.filter [1820]: WARNING Too many errors. Setting the jail idle
2016-12-13 18:22:39,170 fail2ban.filter [1820]: ERROR   Unable to get stat on /var/lib/emby-server/logs/server-63616809673.txt because of: [Errno 2] No such file or directory: '/var/lib/emby-server/logs/server-63616809673.txt'
2016-12-13 18:22:39,170 fail2ban.filter [1820]: WARNING Too many errors. Setting the jail idle
2016-12-13 18:22:39,170 fail2ban.filter [1820]: ERROR   Unable to get stat on /var/lib/emby-server/logs/server-63616914900.txt because of: [Errno 2] No such file or directory: '/var/lib/emby-server/logs/server-63616914900.txt'
2016-12-13 18:22:39,170 fail2ban.filter [1820]: WARNING Too many errors. Setting the jail idle

This is my current logs as I'm posting:

/var/lib/emby-server/logs$ ls -la
total 1140
drwxr-xr-x  2 emby emby   4096 Dec 13 18:22 .
drwxr-xr-x 14 emby emby   4096 Nov 26 12:29 ..
-rw-r--r--  1 emby emby 853217 Dec 11 12:30 server-63616969832.txt
-rw-r--r--  1 emby emby  93486 Dec 12 18:40 server-63617056237.txt
-rw-r--r--  1 emby emby  31150 Dec 12 19:52 server-63617164812.txt
-rw-r--r--  1 emby emby  96755 Dec 13 17:55 server-63617169291.txt
-rw-r--r--  1 emby emby  53339 Dec 13 19:55 server-63617250091.txt

In addition, Emby showing my failed login attempts from WAN, but my fail2ban filter didn't log at all.

 

Did you ever fix this?

Just noticed that I get the same log entries and my jail isn't working properly.

Anyone else noticed this?

[Marv 9]

Is this still working for everyone?

For me it only works from time to time it seems.

[Luke 37060]

Perhaps it might be easier for others to answer if you describe what's not working?

[Marv 9]

I get the same errors as posted by techworld above from time to time.

When this happens login attempts don't get caught by Fail2ban for Emby anymore.

I don't know if this has something to do with how Emby handles log rotations.

This worked for me for some time without an issue. Now I get these errors every once in a while. 

[GWTPqZp6b 41]

I'm seeing similar results too.  

 

Assuming this can be fixed and fail2ban can be relied upon, I was wondering it would be possible to use the <RemoteIPFilter> blacklist section dynamically populated from fail2ban?

I currently run behind a reverse proxy and use fail2ban to maintain a file of nginx deny entries which are included in my location blocks to prevent unauthorized/brute forced accesses instead of firewall entries. 

 

EDIT: Just tried latest 0.10.2 version and the log spamming is gone when `Unable to get stat on /var/lib....` etc. However the primary problem exists that if the log file is update, e.g restart emby, fail2ban wont detect the login failures in the new log file. Looks like we need a way to detect changes in the server files and reload fail2ban to accommodate. 

Edited March 21, 2018 by GWTPqZp6b

[Harbinger1080 3]

EDIT: Just tried latest 0.10.2 version and the log spamming is gone when `Unable to get stat on /var/lib....` etc. However the primary problem exists that if the log file is update, e.g restart emby, fail2ban wont detect the login failures in the new log file. Looks like we need a way to detect changes in the server files and reload fail2ban to accommodate. 

 

I use a similar configuration with fail2ban and nginx, and Emby is the only thing I can't get to work properly.

 

I think to make it work better with fail2ban, the log file should use something like logrotate-- current daily log should be server.txt, and then rotate hourly, or daily, or whatever.  Emby is the only thing I can't get fail2ban to work with properly-- and I'd really like to rotate the Emby logs more often anyway.

[GWTPqZp6b 41]

yeah, Ive spent a few days looking into this and it appears the standard logrotate issue with fail2ban was fixed a good few versions ago. It appears as Emby uses its own logrotate mechanism it simply isnt being recognised. I'm not sure right now if or how to fix this without support from Emby dev's sadly. 

[Luke 37060]

How does emby log rotation affect fail2ban?

[GWTPqZp6b 41]

The logs generated by emby are rotated once per 24 hours or upon restart it appears, when the rotate occurs fail2ban fails to acknowledge the file has been rotated so doesn't monitor the new active log file. 

 

When old log files were removed fail2ban used to throw a significant number of errors, i.e 'No such file or directory' as reported above. This behavior has been fixed in v 0.10.x but the former issue with failing to switch to the new log still occurs. 

 

Ill try and find the github issue which discussed it and the applied fix. 

Edited March 24, 2018 by GWTPqZp6b

[GWTPqZp6b 41]

Im using Debian Stretch 

 

Logrotate issue https://bugzilla.redhat.com/show_bug.cgi?id=833056 and some info https://github.com/fail2ban/fail2ban/issues/184

 

Theres some details in this thread about the lengthy logs produced , https://community.nethserver.org/t/fail2ban-does-huge-logs/8144 and https://github.com/fail2ban/fail2ban/issues/660

 

and heres my latest log entries from fail2ban with the new 0.10 version which prevents log spamming. It looks like its observing the removed server log files but no picking up the new files. 

2018-03-21 19:58:18,118 fail2ban.server         [25822]: INFO    Starting Fail2ban v0.10.2
2018-03-21 19:58:18,118 fail2ban.server         [25822]: INFO    Daemon started
2018-03-21 19:58:18,129 fail2ban.database       [25822]: INFO    Connected to fail2ban persistent database '/var/lib/fail2ban/fail2ban.sqlite3'
2018-03-21 19:58:18,130 fail2ban.jail           [25822]: INFO    Creating new jail 'emby'
2018-03-21 19:58:18,131 fail2ban.jail           [25822]: INFO    Jail 'emby' uses poller {}
2018-03-21 19:58:18,131 fail2ban.jail           [25822]: INFO    Initiated 'polling' backend
2018-03-21 19:58:18,136 fail2ban.filter         [25822]: INFO    Added logfile: '/var/lib/emby/logs/server-63657187200.txt' (pos = 82623, hash = 3cd151fb0ac1d2c1cb0bdf975c110b75)
2018-03-21 19:58:18,136 fail2ban.filter         [25822]: INFO    Added logfile: '/var/lib/emby/logs/server-63657180985.txt' (pos = 44184, hash = 1bf3802f59ce9645f5771d3c156c9571)
2018-03-21 19:58:18,137 fail2ban.filter         [25822]: INFO    Added logfile: '/var/lib/emby/logs/server-63657180187.txt' (pos = 90979, hash = 93deae61b069d32c6aa72ccf337c50dd)
2018-03-21 19:58:18,137 fail2ban.filter         [25822]: INFO    Added logfile: '/var/lib/emby/logs/server-63657177462.txt' (pos = 113400, hash = 1809e00b64417afc2d848fcc0e326262)
2018-03-21 19:58:18,137 fail2ban.filter         [25822]: INFO    Added logfile: '/var/lib/emby/logs/server-63657100800.txt' (pos = 615771, hash = b347cd72f4890effab2925cfb93e82a9)
2018-03-21 19:58:18,138 fail2ban.filter         [25822]: INFO    Added logfile: '/var/lib/emby/logs/server-63657088856.txt' (pos = 998902, hash = 8426ba74b1443fa31d476045b5954328)
2018-03-21 19:58:18,138 fail2ban.filter         [25822]: INFO    Added logfile: '/var/lib/emby/logs/server-63657014399.txt' (pos = 966474, hash = 066a013c2ad0a269c5cf79969d1b10b9)
2018-03-21 19:58:18,139 fail2ban.filter         [25822]: INFO      maxRetry: 1
2018-03-21 19:58:18,139 fail2ban.filter         [25822]: INFO      encoding: UTF-8
2018-03-21 19:58:18,139 fail2ban.actions        [25822]: INFO      banTime: 600
2018-03-21 19:58:18,140 fail2ban.filter         [25822]: INFO      findtime: 600
2018-03-21 19:58:18,144 fail2ban.jail           [25822]: INFO    Jail 'emby' started
2018-03-23 18:48:12,215 fail2ban.filter         [25822]: ERROR   Too many errors at once (100), going idle
2018-03-23 18:48:14,442 fail2ban.filterpoll     [25822]: WARNING Too many errors. Remove file '/var/lib/emby/logs/server-63657014399.txt' from monitoring process
2018-03-23 18:48:14,465 fail2ban.filter         [25822]: INFO    Removed logfile: '/var/lib/emby/logs/server-63657014399.txt'
2018-03-23 18:48:16,468 fail2ban.filterpoll     [25822]: WARNING Too many errors. Remove file '/var/lib/emby/logs/server-63657088856.txt' from monitoring process
2018-03-23 18:48:16,469 fail2ban.filter         [25822]: INFO    Removed logfile: '/var/lib/emby/logs/server-63657088856.txt'

and my log folder 

ls -l /var/lib/emby/logs/
total 1396
-rw-r--r-- 1 emby emby  19546 Mar 22 22:33 ffmpeg-transcode-295c477b-b365-4222-b177-9301a6b4a980.txt
-rw-r--r-- 1 emby emby  21066 Mar 22 22:33 ffmpeg-transcode-bae772a4-25fe-4fa4-b12a-c72a2ddafc3f.txt
-rw-r--r-- 1 emby emby  23763 Mar 22 22:32 ffmpeg-transcode-e2a8aa9b-8709-4607-872d-de28d56bc406.txt
-rw-r--r-- 1 emby emby 615771 Mar 20 21:17 server-63657100800.txt
-rw-r--r-- 1 emby emby 113400 Mar 20 22:03 server-63657177462.txt
-rw-r--r-- 1 emby emby  90979 Mar 20 22:16 server-63657180187.txt
-rw-r--r-- 1 emby emby  44184 Mar 20 23:59 server-63657180985.txt
-rw-r--r-- 1 emby emby  88204 Mar 21 23:59 server-63657187200.txt
-rw-r--r-- 1 emby emby  60251 Mar 22 20:17 server-63657273600.txt
-rw-r--r-- 1 emby emby  16022 Mar 22 20:18 server-63657346710.txt
-rw-r--r-- 1 emby emby 223755 Mar 23 00:00 server-63657346935.txt
-rw-r--r-- 1 emby emby  59132 Mar 23 23:46 server-63657360000.txt

and the monitor status

 fail2ban-client status
Status
|- Number of jail:	1
`- Jail list:	emby
root@emby:/home/ianj# fail2ban-client status emby
Status for the jail: emby
|- Filter
|  |- Currently failed:	0
|  |- Total failed:	0
|  `- File list:	/var/lib/emby/logs/server-63657177462.txt /var/lib/emby/logs/server-63657187200.txt /var/lib/emby/logs/server-63657100800.txt /var/lib/emby/logs/server-63657180187.txt /var/lib/emby/logs/server-63657180985.txt
`- Actions
   |- Currently banned:	0
   |- Total banned:	0
   `- Banned IP list:

and my jail monitor line

cat /etc/fail2ban/jail.d/emby.local
[emby]
enabled = true
port = 8920,8096
filter = emby
logpath = /var/lib/emby/logs/server-*.txt
maxretry = 1
findtime = 600
bantime = 600
banaction = nginx-multiport

and just verified that Emby is logging correctly which it is, heres my failed log in attempt just reported in the current log file

2018-03-23 23:57:42.136 Info HttpServer: HTTP Response 401 to 172.56.xxx.xxx. Time: 863ms. http://emby.xxx.xxx:8096/Users/authenticatebyname

Edited March 24, 2018 by GWTPqZp6b

[mastrmind11 717]

If Emby named the current log "server.txt" and added timestamps after the log rolls (like 99% of every other Linux app), this would not be an issue.

[Luke 37060]

i think rather than try and parse the log file you should probably just look at using the emby api to get the information that you need.

[Harbinger1080 3]

i think rather than try and parse the log file you should probably just look at using the emby api to get the information that you need.

 

Possibly-- I haven't gotten in to the API yes, since fail2ban is a common and widely used tool specifically for parsing log files.  If I was going to write a service that uses the API, or a plugin, I'd have it directly ban/unban IP addresses in the same way fail2ban already does.  Seems redundant, and I don't really like the idea of having a separate service perform the exact same function.  But if that's the only way I can block potentially suspicious probes of the Emby login process, then that's how it'll need to be done.

 

I'll submit a feature request later, to request a change to log rotation-- hopefully with an option to simply use logrotate in Linux installs.  That would make configuring fail2ban very simple and more in line with other applications commonly hosted alongside it.

[dcrdev 251]

Possibly-- I haven't gotten in to the API yes, since fail2ban is a common and widely used tool specifically for parsing log files.  If I was going to write a service that uses the API, or a plugin, I'd have it directly ban/unban IP addresses in the same way fail2ban already does.  Seems redundant, and I don't really like the idea of having a separate service perform the exact same function.  But if that's the only way I can block potentially suspicious probes of the Emby login process, then that's how it'll need to be done.

 

I'll submit a feature request later, to request a change to log rotation-- hopefully with an option to simply use logrotate in Linux installs.  That would make configuring fail2ban very simple and more in line with other applications commonly hosted alongside it.

 

Agree with this - we should have the option to disable Emby's built in log rotate function so that the logrotate tool can be used inplace.

[Luke 37060]

This may help with fail2ban:

https://emby.media/community/index.php?/topic/57525-33111-log-file-rotation

[everydayevil 6]

This may help with fail2ban:

https://emby.media/community/index.php?/topic/57525-33111-log-file-rotation

 

Luke,

 

Thanks! This will be a welcome change.

 

-everydayevil

[GWTPqZp6b 41]

This may help with fail2ban:

https://emby.media/community/index.php?/topic/57525-33111-log-file-rotation

 

 

Thank you Luke. I think with Embys big advantage over its competitors its its self-hosted nature, the ability to secure the front end is a fundamental need and valuable addition. I'll test this evening. Thank you again for your responsiveness. 

[carsten@curdt-online.de 0]

Hello all,

 

just 1 hint for all others trying to set this up using for EMBY running in a Docker container with fail2ban running on the host:

 

Make sure, that the TZ environment variable of the Docker container is set correctly (to the same TZ as the one on the docker host). Otherwise the filter will not match. Double check in the EMBY log, that the date/time of the log entries matches the time on the host!

 

Example for docker-compose:

 

  emby:
    container_name: emby
    restart: always
    image: emby/embyserver:latest
    depends_on:
      - traefik
    volumes:
      - /mnt/volumes/emby/config:/config
    ports:
      - "8096:8096"
      - "8920:8920"
    environment:
      - TZ=Europe/Berlin
 

Edited January 14, 2019 by carsten@curdt-online.de

[Luke 37060]

Great, thanks for the info !

[RG9400 0]

This is excellent, and I am trying to get it set up with win2ban (fail2ban for Windows). My logs are unfortunately stored at 

C:/Users/My Name/AppData/Roaming/Emby-Server/programdata/logs/embyserver.txt

 which has a space in it. Win2ban works perfectly with most windows paths, but it is having trouble parsing this one. I tried using single quotes, double quotes, and /path/to/folder\ withspace. None of it works. I tested it on fail2ban on Debian, and same issue -- fail2ban stops reading the path as soon as it hits the space. Since I cannot change the log location in Emby, this is what I am stuck with. Any ideas on how to get fail2ban to play nice with this folder location?

[Happy2Play 8281]

This is excellent, and I am trying to get it set up with win2ban (fail2ban for Windows). My logs are unfortunately stored at 

C:/Users/My Name/AppData/Roaming/Emby-Server/programdata/logs/embyserver.txt

 which has a space in it. Win2ban works perfectly with most windows paths, but it is having trouble parsing this one. I tried using single quotes, double quotes, and /path/to/folder\ withspace. None of it works. I tested it on fail2ban on Debian, and same issue -- fail2ban stops reading the path as soon as it hits the space. Since I cannot change the log location in Emby, this is what I am stuck with. Any ideas on how to get fail2ban to play nice with this folder location?

 

I would think you would get a faster response from the software provider, as this is the first time I have seen any mention of win2ban.  And at those prices I would expect an answer.

 

Just like another Windows option IPBan.

https://emby.media/community/index.php?/topic/69286-ipban-for-emby/

Edited April 5, 2019 by Happy2Play

[RG9400 0]

I would think you would get a faster response from the software provider, as this is the first time I have seen any mention of win2ban.  And at those prices I would expect an answer.

 

Just like another Windows option IPBan.

https://emby.media/community/index.php?/topic/69286-ipban-for-emby/

 

Actually, this seems to be a limitation with fail2ban in general and as far back as version .9, so I don't think it's practical to wait for them to patch it. Win2ban is just a Windows wrapper for it. It's also somewhat a limitation for Emby not being able to modify log locations.

 

IP Ban looks interesting, but I just ended up hardlinking the log file into a path without a space, and everything works perfectly after that!

[tekfranz 6]

I have this all set up with jail.local and emby.conf and I keep getting this error:

 

ERROR   Jail 'emby' skipped, because of wrong configuration: Unable to read the filter 'emby'

 

**EDIT**

Duh I gues the name of the file is emby.conf NOT ebmy.conf

 

Working now.

Edited May 13, 2019 by tekfranz

[tekfranz 6]

Has anyone got the fail2ban logs sending by email. I am using the sendmail config but GMail is denying the send. I have used GMail as a relay elsewhere and it is working.  The one issue I see is that sendmail does not include required GMail information like a "From Address". Are there any other "Free" Mail providers that the emails work with? Or do I need install a Mail Server on my EMBY Machine?

 

I followed these instructions and everything works except the final VERIFY with GMail. Great instructions BTW.

 

https://medium.com/@yenthanh/config-your-sever-as-a-mta-mail-transfer-agent-using-sendmail-with-a-gmail-account-93bbf2eec6c1

Edited May 13, 2019 by tekfranz

[runtimesandbox 152]

Have a look at mailgun rather than gmail. they provide 10000 free email sends per month - however you do need your own domain name