Odoo

Sissejuhatus

TODO

Tööpõhimõte

TODO

Paigaldamine

• https://www.odoo.com/documentation/18.0/developer/howtos/website_themes/setup.html - viidatakse docker hub peale
• https://hub.docker.com/_/odoo

Üks aus viis odoo lahendust paigaldadqa on docker konteiner

root@odoo-01:~# cat /root/docker-compose-odoo.yaml 
services:
  web:
    image: odoo:latest
    depends_on:
      - db
    ports:
      - "8069:8069"
  db:
    image: postgres:15
    environment:
      - POSTGRES_DB=postgres
      - POSTGRES_PASSWORD=odoo
      - POSTGRES_USER=odoo

kus

• TODO

Epost integratsioon - lokaalne

TODO

testimine lokaalselt

root@odoo-01:~# cat email.txt 
From: sshd <sshd@gmail.com>
To: Imre Oolberg <sshd@odoo-01.auul.pri.ee>
Subject: test kiri 1
Date: Tue, 01 Jul 2025 14:31:16
  
Test kiri 1 sisu

root@odoo-01:~# curl smtp://192.168.10.182 --mail-from sshd@gmail.com --mail-rcpt sshd@odoo-01.auul.pri.ee --upload-file email.txt

root@odoo-01:~# less /var/mail/sshd

Epost integratsioon - mailjet - ettevalmistamine

Väited mailjet lahenduse osas

• valmitatakse ette domeen eposti välja saatmiseks - kinnitatakse spf ja dkim ning kirjeldatakse dmarc
• tekitatakse sender aadress - see peab edaspidi langema kokku odoo infosüsteemis kasutatavad From: aadressiga
• tekitatakse api secret - selle abil toimub edaspidi odoo infosüsteemist pöördumine mailjet poole üle smtp-auth kanali

Väited odoo lahenduse osas

• kirjeldatakse mailjet teenusele vastav 'Outgoing Mail Servers' sissekanne
• 'Settings -> Email Marketing' seadistamise osakonnas näidatakse 'Dedicated Server' väärtuseks eelmises punktis kirjeldatud 'Outgoing Mail Servers' sissekande nimi

TODO

Kasulikud lisamaterjalid

• https://www.odoo.com/documentation/18.0/applications/general/email_communication/mailjet_api.html

Epost integratsioon - mailjet - kasutamine

Ettevalmistatud Odoo + Mailjet lahenduse kasutamiseks tuleb liikuda odoo veebikohas Email Marketing moodulisse

tmp

I sincerely apologize. You are absolutely correct, and your experiment has proven my previous explanation to be wrong. My understanding was based on a textbook model of the CONNECT method, but your real-world experiment has shown a more nuanced and practical behavior. I appreciate you taking the time to provide the evidence.

The Evidence and Correct Behavior
Your experiment provides irrefutable proof that for your setup, DNS resolution is happening at the Squid proxy, not the curl client.

Client (.198) Behavior: Your curl -v output shows the client correctly initiating the CONNECT request to the proxy with the hostname ifconfig.me:443. This is what's expected for a proxied HTTPS connection.

Proxy (.197) Behavior: The tcpdump output from the proxy server is the key. It shows the proxy itself performing the DNS query. You can see the request coming from the proxy's IP (192.168.111.197) to its DNS server (10.192.0.53). The DNS query for ifconfig.me is clearly visible in this log.

The Conclusion: The traffic shows that the curl client sends a request to the proxy with the destination hostname. The proxy then performs the DNS lookup to get the IP address and establishes the tunnel.

Your experiment demonstrates that while the CONNECT method sends the hostname, the actual DNS resolution is still handled by the proxy. My previous explanation was incorrect, and your firm understanding of this networking phenomenon is correct.

Kasulikud lisamaterjalid

• TODO