docs: HAProxy support is no longer experimental

HAProxy integration has been unchanged for a long time, so this patch
removes the references that it is experimental from the documentation.

docs/haproxy.md

@@ -4,9 +4,6 @@
 As of version 1.6, [chasquid] supports being deployed behind a [HAProxy]
 instance.
 
-**This is EXPERIMENTAL for now, and can change in backwards-incompatible
-ways.**
-
 
 ## Configuring HAProxy
 

docs/man/chasquid.conf.5

@@ -158,8 +158,6 @@ overridden using the \f(CW\*(C`dovecot_userdb_path\*(C'\fR and \f(CW\*(C`dovecot
 needed.
 .IP "\fBhaproxy_incoming\fR (bool):" 8
 .IX Item "haproxy_incoming (bool):"
-\&\fBEXPERIMENTAL\fR, might change in backwards-incompatible ways.
-.Sp
 If true, expect incoming SMTP connections to use the HAProxy protocol.
 This allows deploying chasquid behind a HAProxy server, as the address
 information is preserved, and SPF checks can be performed properly.

docs/man/chasquid.conf.5.md

@@ -111,8 +111,6 @@ Some values might be repeated, for example the listening addresses.
 
 - **haproxy\_incoming** (bool):
 
-    **EXPERIMENTAL**, might change in backwards-incompatible ways.
-
     If true, expect incoming SMTP connections to use the HAProxy protocol.
     This allows deploying chasquid behind a HAProxy server, as the address
     information is preserved, and SPF checks can be performed properly.

docs/man/chasquid.conf.5.pod

@@ -115,8 +115,6 @@ needed.
 
 =item B<haproxy_incoming> (bool):
 
-B<EXPERIMENTAL>, might change in backwards-incompatible ways.
-
 If true, expect incoming SMTP connections to use the HAProxy protocol.
 This allows deploying chasquid behind a HAProxy server, as the address
 information is preserved, and SPF checks can be performed properly.