General type of mail configuration: mail sent by smarthost; received via SMTP or fetchmail
System mail name: your hostname
IP-address to listen on for incoming SMTP connections: 127.0.0.1
Other destinations for which mail is accepted: your hostname
Machines to relay mail for: leave this blank
IP address or host name of the outgoing smarthost: mail.example.com::587
Hide local mail name in outgoing mail?
Yes - all outgoing mail will appear to come from your gmail account
No - mail sent with a valid sender name header will keep the sender’s name
Keep number of DNS-queries minimal (Dial-on-Demand)? No
Delivery method for local mail: choose the one you prefer
Split configuration file into small files? Yes (you need to edit one of the files next)
Then run sudo vi /etc/exim4/passwd.client and add the following lines for your mail host, and any aliases it has (found through nslookup). Substitute email address and password with the account you want to route mail through):
1
mail.example.com:email address:password
Once you edit the passwd.client file, run sudo update-exim4.conf which will integrate your changes into your Exim4 config.
Run sudo systemctl restart exim4 and make sure that the service stops and starts properly. If the service is unable to restart, something probably went wrong when you edited the passwd.client file.
Now the configure has been finished.
We can use exim -v [email protected] to get in send process to send a test email.
deb http://mirrors.163.com/debian/ buster main non-free contrib deb http://mirrors.163.com/debian/ buster-updates main non-free contrib deb http://mirrors.163.com/debian/ buster-backports main non-free contrib deb http://mirrors.163.com/debian-security/ buster/updates main non-free contrib
deb-src http://mirrors.163.com/debian/ buster main non-free contrib deb-src http://mirrors.163.com/debian/ buster-updates main non-free contrib deb-src http://mirrors.163.com/debian/ buster-backports main non-free contrib deb-src http://mirrors.163.com/debian-security/ buster/updates main non-free contrib
In some cases, we need to pull some docker image through our custom proxy server.
But the HTTPS_PROXY and HTTP_PROXY in current login terminal will not be useful for the docker pull command. The proxychains-ng tool is the same situation.
This is because docker is divided into dockerd and client. The docker pull command is executed by dockerd service. So we need make sure dockerd use proxy server.
The Docker daemon uses the HTTP_PROXY, HTTPS_PROXY, and NO_PROXY environmental variables in its start-up environment to configure HTTP or HTTPS proxy behavior. You cannot configure these environment variables using the daemon.json file.