From 07eb15246f524f495b473cf97ddd51f661f8b5bf Mon Sep 17 00:00:00 2001 From: Adam Cooke Date: Tue, 20 Feb 2024 21:48:57 +0000 Subject: [PATCH] docs: update docs for how IP address allocation works closes #2209 --- app/views/ip_addresses/_form.html.haml | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/app/views/ip_addresses/_form.html.haml b/app/views/ip_addresses/_form.html.haml index ea8053f6..e6f534ed 100644 --- a/app/views/ip_addresses/_form.html.haml +++ b/app/views/ip_addresses/_form.html.haml @@ -17,16 +17,15 @@ %p.fieldSet__text This priority will determine the likelihood of this IP address being selected for use when sending a message. The higher the number the more likely the IP - is to be chosen. By defalt, the priority is set to the maximum value of 100. + is to be chosen. By default, the priority is set to the maximum value of 100. This can be used to warm up new IP addresses by adding them with a low priority. To give an indication of how this works, if you have three IPs with 1, 50 and 100 as their priorities, and you send 100,000 emails, the priority 1 address will receive - a tiny percentage, the priority 50 will receive roughly 25% and the priority 100 will - receive roughly 75%. + a tiny percentage, the priority 50 will receive roughly one third of e-mails and the + priority 100 will receive roughly two thirds. .fieldSetSubmit.buttonSet = f.submit :class => 'button button--positive js-form-submit' .fieldSetSubmit__delete - if @ip_address.persisted? = link_to "Delete IP address", [@ip_pool, @ip_address], :class => 'button button--danger', :method => :delete, :remote => true, :data => {:confirm => "Are you sure you wish to remove this IP from the pool?"} -