docker-mailserver.docker-ma.../test/config/fetchmail.cf

poll pop3.example.com. with proto POP3
	user 'username' there with
	password 'secret'
	is 'user2@domain.tld'
	here options keep ssl
	
poll pop3-2.example.com. with proto POP3
	user 'username' there with
	password 'secret'
	is 'user3@domain.tld'
	here options keep ssl
fix: fix test setup.sh debug fetchmail on wildcard domains on hosts that belong to wildcard domains pop3.example.com might actually resolve to pop3.example.com.[mydomain.com] and give a valid ip the return code of fetchmail then no longer is 11 (dns failure) but something else (2 for socket error in our case) to make sure we always get return code 11 we use the domain name pop3.example.com. that is not allowed to be resolved to a subdomain. 2019-11-12 09:23:45 +01:00			`poll pop3.example.com. with proto POP3`
Implement fetchmail (#260) (#271) To retrieve emails from external mail accounts. 2016-08-21 22:13:13 +02:00			`user 'username' there with`
			`password 'secret'`
			`is 'user2@domain.tld'`
			`here options keep ssl`
Solve Fetchmail imap idle issue (#10) * Migrate PR#1730 from tomav/docker-mailserver repo to new docker-mailserver/docker-mailserver repo * Resolved review comments * Moved counter increment to have consistency between fetchmail process and fetchmail config files * Added tests for new fetchmail option Co-authored-by: Georg Lauterbach <44545919+aendeavor@users.noreply.github.com> 2021-01-17 10:39:09 +01:00
			`poll pop3-2.example.com. with proto POP3`
			`user 'username' there with`
			`password 'secret'`
			`is 'user3@domain.tld'`
			`here options keep ssl`