3,250
edits
Changes
Jump to navigation
Jump to search
Line 24:
Line 24: − {{#smeversion: {{#var:contribname}} }} Line 32:
Line 31: + − + − yum --enablerepo=smecontribs install {{#var:smecontribname}}+ − signal-event post-upgrade − signal-event reboot − </tab><tab name="For SME 8"> − yum --enablerepo=smecontribs install {{#var:smecontribname}} − signal-event post-upgrade − signal-event reboot − </tab></tabs> Line 64:
Line 57: − + Line 90:
Line 83: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Line 119:
Line 169: − + Line 132:
Line 182: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + − <!-- list of category you want to see this page in --> − [[contriblang:: {{#var:lang}} | ]]
→DNS CNAME Record
<!-- keep this first element as is, you can add some if needed -->
<!-- keep this first element as is, you can add some if needed -->
{{#smeversion: {{#var:smecontribname}} }}
{{#smeversion: {{#var:smecontribname}} }}
=== Description ===
=== Description ===
=== Installation ===
=== Installation ===
prerequisite you need a valide SSL certificate, redirection might fails if https uses a non valid certificate, try [[Letsencrypt]]
<tabs container><tab name="For SME 10">
<tabs container><tab name="For SME 10">
yum --enablerepo=smecontribs install {{#var:smecontribname}}
yum --enablerepo=smecontribs install {{#var:smecontribname}}
</tab><tab name="For SME 9">
</tab>
</tabs>
=== Configuration ===
=== Configuration ===
Second would be to force Outlook to use old detection configuration by manipulating Registry, as a priviledged user run in a windows shell:
Second would be to force Outlook to use old detection configuration by manipulating Registry, as a priviledged user run in a windows shell:
reg add HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Office\16.0\Outlook\setup /T REG_DWORD /F /V DisableOffice365SimplifiedAccountCreation /D 1"
reg add "HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Office\16.0\Outlook\setup /T REG_DWORD /F /V DisableOffice365SimplifiedAccountCreation /D 1"
===== Outlook 2019 =====
===== Outlook 2019 =====
see bug https://bugs.koozali.org/show_bug.cgi?id=12100
see bug https://bugs.koozali.org/show_bug.cgi?id=12100
====DNS SRV Record alternate method====
smtp
_smtp._tcp SRV 0 1 25 mail.example.com.
smtps
_smtps._tcp SRV 0 1 465 mail.example.com.
submission (not in use on SME)
_submission._tcp SRV 0 1 587 mail.example.com.
imap
_imap._tcp SRV 0 1 143 imap.example.com.
_imaps._tcp SRV 0 1 993 imap.example.com.
pop3
_pop3._tcp SRV 0 1 110 pop3.example.com.
_pop3s._tcp SRV 0 1 995 pop3.example.com.
{{Note box|Cladav and cardav are not yet implemented for thunderbird xml autoconfig. It relies on RFC 6764, meaning only way is to use th SRV records.}}
caldav with or without TLS , could use a TXT field too, if no txt value is present then client will check /.well-known/caldav
_caldav._tcp SRV 0 1 80 calendar.example.com.
_caldavs._tcp SRV 0 1 443 calendar.example.com.
_caldav._tcp TXT path=/caldav
_caldavs._tcp TXT path=/caldav
cardav , could use a TXT field too, if no txt value is present then client will check /.well-known/cardav
_cardav._tcp SRV 0 1 80 calendar.example.com.
_cardavs._tcp SRV 0 1 443 calendar.example.com.
_cardav._tcp TXT path=/caldav
_cardavs._tcp TXT path=/caldav
==== DNS and file for MTA-STS and TLS-RPT ====
as you are there you can inform the worl you use along side with DKIM, SPF and DMARC properly configured this. See
create a subdomain ''mta-sts.yourdomain.com , make it point to your server, and set [[Letsencrypt|Let's Encrypt]] to create a certificate for it''
fill the content of the file /home/e-smith/files/ibays/Primary/''.well-known/mta-sts.txt with''<syntaxhighlight lang="console">
version: STSv1
mode: testing
mx: yourdomain.com
max_age: 604800
</syntaxhighlight>fill the following records at your dns. (fill the id field with current timestamp, and update the domain/ email to your needs)<syntaxhighlight lang="console">
_smtp._tls.yourdomain.com. 900 IN TXT "v=TLSRPTv1; rua=mailto:admin@yourdomain.com"
_mta-sts.yourdomain.com. 900 IN TXT "v=STSv1; id=1575556993"
</syntaxhighlight>
==== DNS and BIMI Record ====
add a picture as svg accessible with your web srver, be sure DMARC fields are ok. and then file the DNS field, with the correct URL. You might need to check if your SVG is compatible <syntaxhighlight lang="console">
default._bimi IN TXT "v=BIMI1; l=https://yourdomain.com/images/Logo.svg"
</syntaxhighlight>you might also obtain a certificate for your logo after having validate your ownership see: Verified Mark Certificates (VMC). As of 2023 this is a paid certificate for about 1500 USD a year, after registering for your trademark. So this will be kept out of scope of this page for the moment
# https://authindicators.github.io/rfc-brand-indicators-for-message-identification/
# https://mxtoolbox.com/dmarc/bimi/how-to-create-bimi-record
# https://bimigroup.org/using-the-rnc-schema-to-validate-bimi-svg-images/
==== DNS DKIM /SPF and DMARC ====
see [[Email#DKIM Setup - qpsmtpd version .3E.3D 0.96]]
====DNS CNAME Record ====
having a CNAME for autodiscover pointing to your server could help but is not mandatory.
====Server Side ====
====Server Side ====
you can list the available configuration with the following command :
you can list the available configuration with the following command :
=== Uninstall ===
=== Uninstall ===
yum remove {{#var:smecontribname}} {{#var:contribname}}
yum remove {{#var:smecontribname}}
=== Bugs ===
=== Bugs ===
{{ #smechangelog: {{#var:smecontribname}} }}
{{ #smechangelog: {{#var:smecontribname}} }}
===Sources===
Microsoft clients
*https://docs.microsoft.com/en-us/previous-versions/office/exchange-server-2007-technical-articles/bb332063(v=exchg.80)?redirectedfrom=MSDN#SupportedScenariosConnecting
*https://docs.microsoft.com/en-us/exchange/client-developer/exchange-web-services/autodiscover-for-exchange#options-for-using-autodiscover
*https://docs.microsoft.com/en-us/exchange/client-developer/web-service-reference/soap-autodiscover-web-service-reference-for-exchange?redirectedfrom=MSDN
*https://docs.microsoft.com/en-us/openspecs/exchange_server_protocols/ms-oxdscli/48d23e06-f884-44b5-993e-75b7a115827c
*https://support.microsoft.com/en-us/topic/outlook-2016-implementation-of-autodiscover-0d7b2709-958a-7249-1c87-434d257b9087
*https://admx.help/HKCU/software/policies/microsoft/office/16.0/outlook/setup
*https://www.howto-outlook.com/howto/autodiscoverconfiguration.htm
Multiple configuration
*https://github.com/mailcow/mailcow-dockerized/blob/master/data/web/autodiscover-json.php
*https://github.com/mailcow/mailcow-dockerized/blob/master/data/web/inc/vars.inc.php
*https://forum.virtualmin.com/t/autodiscover-mail-settings-outlook/108570
*https://github.com/mailcow/mailcow-dockerized/issues/615 (trouble with Outlook 2016)
*https://github.com/mailcow/mailcow-dockerized/blob/master/data/web/autodiscover.php
*https://github.com/gronke/email-autodiscover/blob/master/mail/autodiscover.xml
*https://mcmilk.de/projects/autoconfig/ (MS TB and Apple)
* https://roll.urown.net/server/mail/autoconfig.html
* https://github.com/smartlyway/email-autoconfig-php
about new MS json file
* https://blog.icewolf.ch/archive/2020/12/09/autodiscover-v2-json-requests.aspx (TODO create this file)
* https://github.com/mailcow/mailcow-dockerized/blob/master/data/web/autodiscover-json.php
* https://www.msxfaq.de/exchange/autodiscover/autodiscover_v2.htm
* https://github.com/gronke/email-autodiscover/blob/master/settings.json.sample
* https://github.com/mailcow/mailcow-dockerized/pull/636
about Mozilla
* https://wiki.mozilla.org/Thunderbird:Autoconfiguration:ConfigFileFormat
generic
* https://datatracker.ietf.org/doc/html/rfc6764<!-- list of category you want to see this page in -->
[[Category: Contrib]]
[[Category: Contrib]]
<!-- Please keep there the template revision number as is -->
<!-- Please keep there the template revision number as is -->
[[contribtemplate::2| ]]
[[contribtemplate::2| ]]