Exim send e-mails to another mx server - exim

I have two servers one for web and other for e-mail.
The web server has installed exim for send notifications to clients but I can't receive emails from the same domain in the e-mail server because all the emails sent from web server stay right there.
The web server and email server have their respective dns entries.

I changed the vdomain driver to use dnslookup and transport to remote_smtp in the exim conf.
All email sent to the same domain now just look for mx register in the dns.
vdomain:
debug_print = "R: vdomain for $local_part#$domain"
driver = dnslookup
domains = dsearch;/etc/exim.domains
local_parts = lsearch;/etc/exim.domains/$domain
transport = remote_smtp

Related

Setting Outgoing Emails Servers in Odoo

I'm trying to set-up outgoing email server in Odoo for my Organization.
For doing so the system request for username and password along with server details,
Now we have around 15 users in Odoo.
Do we need to enter all usernames individually?
Odoo is not a mail server.
You have to configure with your any of your official mail accounts (gmail/outlook/any other official mail service you have for your office). odoo will use those to send mail.
Description: A description for the outgoing mail server.
SMTP server: The pointer to the SMTP of your server, ex. smtp.gmail.com .
SMTP port: The port of your SMTP server, ex. 465 for Gmail.
Connection security: You should choose SSL/TLS for Gmail.
Username: Your e-mail account, like: youremail#gmail.com
Password: Password of your e-mail account.
SMTP Server :- smtp.gmail.com
SMTP Port :- 465
Connection Security :- SSL/TLS
Username :- Your mail account
Password:- Password of your email account
The following fields are needed to configure the mail server.
Description :-> A description of the Outgoing mail server
Priority :-> Priority of your outgoing mail server. Low priority mail servers are used first and mostly.
SMTP Server :-> The server SMTP e.g, zsmtp.hybridzimbra.com(for Thunderbird)
SMTP Port :-> The SMTP port of your server e.g, 465 (for Thunderbird)
Connection Security :-> Security to be used like TLS(STARTTLS) or SSL/TLS. Use SSL/TLS for Thunderbird
Username :-> Your e-mail account.
Password:-> The password of your e-mail account.
I think the following document should help you out.
https://www.odoo.com/documentation/15.0/applications/general/email_communication/email_servers.html

DNS a-route with SSL and Apache

I have a domain served at server A and I have set up an A-record to server B.
For http://mypage.com all works fine.
But there is also SSL on the domain. On server B there are a few virtual hosts set up. One of which has an SSL virtual host (443), theirpage.com. If I now go to https://mypage.com I end up at theirpage.com.
If I set up mypage.com MUST I have the SSL certificate from server A available for this new specific ssl-virualhost? The provider at server A does not share their ssl-certificates...
Assuming:
Server A - DNS only, no web services.
Server B - Web server.
The following is extreme oversimplification of what actually happens. For simplicity we exclude all caches, networking and application complexity.
What happens on the client:
User navigates to mypage.com (HTTPS)
Browser/OS does a lookup of who mypage.com is; receives the IP
Browser attempts to establish secure connection with IP of a webserver.
It is at this point browser will look at the SSL certificate provided by your web server. That certificate must be signed by trusted authority and have a valid alternate name of mypage.com. Not signed or name does not match to what user typed into the browser you will receive a certificate error.
If the certificate passed:
Browser will complete establishing connection
Browser will request a content named mypage.com
Browser displays content revived from the web server
In this scenario only web server must have a valid certificate, prooving to the client that it is indeed the server client attempts to connect to.
HTTP Scenario is similar, but connection is not secured and site will load. Most of the websites setup redirect request on HTTP calls, forcing the user's browser repeat it's request via HTTPS protocol.

How to change the "cn" value to IP address instead of localhost in websphere Application server

I am trying to set up a client-server EJB using two different machines on my network. while installing WAS server it prompted me to add admin credentials, so LTPA is enabled (hope it enabled SSL). Now on client EJB deployed WAS server I have to configure the outbound IIOP SSL certificate(Correct me if I am wrong on this). But unfortunately in the server WAS admin console I can see SSL Signer certificates cn(Host/domain) parameter as localhost. the same "localhost" is arriving when I try to "retrieve from port" in client EJB WAS server.
I have attached the "Retrieve from port" screenshot
Client WAS retrieve from port action
Even I have tried changing the hostname in the server WAS under the Server-> Communications -> Port to IP address instead of localhost.
I expect it should bring domainname.ipaddress
"Retrieve from port" action always brings "localhost" from the remote server
As per the comment by #Gas, I am following this below link
https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.multiplatform.doc/ae/tsec_sslreplacecell.html
will update in short

Domino Client was not authenticated to send anonymous mail during MAIL FROM

I have a Domino server v8.5.3. FixPack 6 with the Interim fix 853FP6HF3180_W32 and I have to send emails through smtp.office365.com via SSL. I have enabled the SSL negotiadted over TCP/IP port in the configuration document and the SMTP outbound (port 25) negotiated SSL.
I get the next error:
Error transferring to outlook-xxxxxxxx.OFFICE365.COM; SMTP Protocol Returned a Permanent Error 530 5.7.57 SMTP; Client was not authenticated to send anonymous mail during MAIL FROM [XXXXXXXXXXXXXX.outlook.com]

HTTPS client - certificate

I write raw HTTPS client in C - a program that takes domain name, resolves it to IP address (via DNS), connects to the IP address on port 443 (SSL), performs SSL handshake and then sends HTTP request via the SSL socket.
To try this program I have a domain hosted on a webserver. I installed Let's encrypt certificate for the domain.
I found out that there are many domain names sharing the same IP address as my domain. So when I connect to the IP address on port 443 to perform SSL handshake who ensures that mydomain's SSL certificate will be sent from the server to the client and not another certificate belonging to other domain name sharing the same IP address?
There exists a TLS extension called Server Name Indication (SNI) which is widely used (and is e.g. require for http/2 clients). You can find the formal specification of this extension in RFC 6066.
Using SNI, a client can send a desired hostname in its Hello request which allows the server to select a matching key/certificate combination for this connection.