Portal del Cliente · Community NewspapersGestión de la cuenta · NeedAWebNow.comENES
CNCuenta
FACTURA

Invoice INV-X-2026-017

Importe pagado
$1,750.00
✓ PAGADA
Emitida: 26 ago 2026Pagada el: 1 sept 2026Pagada con: Cheque

Pagada por completo. Gracias.

Recibo

Importe pagado
$1,750.00
Fecha de pago
1 sept 2026
Pagada con
Cheque
Número de factura
INV-X-2026-017

⬇ Descargar recibo (PDF)

Qué cubre esta factura

ConceptoCant.Importe
Server-mail loop — stop it, clear it, alert on it Your server's alert mail is stuck in a loop. On 2026-08-18 Gmail refused 11,933 messages in one day (11,923 of them addressed to Michael) because the server IP 72.52.179.212 is on a block list; roughly 1,640 messages are queued, 1,630 frozen. The cost is that Michael receives none of his own server's disk, load, security or cron warnings. This stops the loop, clears the queue, files the Google delisting request and puts alerting on a route that arrives. The delisting decision is Google's, not ours — priced as filing and monitoring it, not as a guaranteed date.1$500.00
Malware scanner — exclusions, verification, and page-cache retention The cxs scanner has no exclusion list (/etc/cxs/cxs.ignore does not exist), so it grinds through the WordPress page cache — 77,579 files, 17 GB, individual files re-scanned 294–298 times — and mails a report every five minutes. Every report reads Hits 1, Viruses 0, Fingerprints 0. That is about 70% of all alert mail the server sends, and it feeds the item above. A scanner permanently busy with disposable cache is also not one you can trust to have read the files that matter.1$650.00
Email authentication, mail-client endpoints, and delivery logging cnews.net publishes no DKIM signature — twelve selectors swept against public DNS on 2026-08-18, none found — and neither cnews.net nor communitynewspapers.com publishes a DMARC record. Separately, five cnews.net host names (mail, webmail, imap, pop, smtp) still resolve to GoDaddy while the domain's mail is delivered to Google Workspace, so anyone set up against those names is reading the wrong mailbox. It is delivered in two priced parts, shown below.1$600.00
Newsletter sender authentication — your newsletter now signs and passes as your own domain Included at no charge; it was priced at $175.00 when written on August 19. Your newsletter relays through your own Amazon SES. When this was written your DNS carried only an Amazon ownership token — no signing records and no return-path subdomain — so nothing the newsletter sent could be matched back to communitynewspapers.com. That is now done: three Amazon signing records and a communitynewspapers.com return-path subdomain are live, Amazon reports Success on all of them, and receivers confirm it. Across 1,204,433 messages of receiver-reported data, the share of your newsletter that matched your own domain was 0.0% every day through August 29 and is 100.0% as of September 1. Google's bulk-sender rules require a matching signature plus DMARC above 5,000 Gmail messages a day; both are now in place, where neither was before. For context on why this mattered: across August, 910,640 of 5,595,868 messages bounced (16.27%), 909,757 soft and 883 hard, so the list is clean and the mail was being declined rather than undeliverable, and in a 1,200-message bounce sample 89.9% were Gmail against a 34.8% Gmail share of the list. We are still not promising you a bounce rate, and it is too early to attribute any change in bouncing to this work — what we can state is that the one published Google requirement your domain measurably did not meet, it now meets. The DMARC record itself sits in item 3 above, not here.1$0.00
Staff email configuration check — no charge We walk each Community Newspapers staff member through confirming their mail client points at Google Workspace rather than stale GoDaddy settings. A mailbox on the wrong incoming server looks healthy from the desk using it while incoming mail lands where nobody reads it.1$0.00
cnews.net mail routing — Google's own setup check now reads Complete Included at no charge; it was priced at $175.00 when scoped on September 1. Google's admin console was reporting the mail routing for cnews.net as Incorrect. Your mail was not in fact failing — we established that before touching anything — but a Google console reading Incorrect against your own domain is not something to leave sitting there, because it is the first place anyone looks the moment mail is questioned. The five original routing records were replaced with the single record Google now specifies, carried out as its own change with no other edit to the domain in flight, and the console now reads Complete. There is no charge because this was a conformance tidy-up rather than a repair: nothing about your mail was broken before it, and nothing about it was put at risk during it.1$0.00

Lo que se hizo

Deliverables — 6 of 6 done, snapshot Sep 2, 2026:
  • /root/.forward repointed from a personal mailbox to a monitored destination you name — proof: the before and…/root/.forward repointed from a personal mailbox to a monitored destination you name — proof: the before and after file, with modification times
  • LF_SSH_EMAIL_ALERT tuned so a real intrusion still alerts but routine logins do not — proof: the csf.conf diff
  • /dev/null restored to a real device node — it had been overwritten by an ordinary file, so mail the server…/dev/null restored to a real device node — it had been overwritten by an ordinary file, so mail the server tried to discard was writing into it instead — proof: ls -la /dev/null now reads crw-rw-rw- 1 root root 1, 3, applied August 20 at 15:45 and re-checked still correct on September 1; the mail server's panic log went from 7,639 entries to none after that minute, and the first two outbound deliveries following it were confirmed landed
  • Frozen queue cleared — proof: exim -bpc before and after, held across a full frozen-message timeout window.…Frozen queue cleared — proof: exim -bpc before and after, held across a full frozen-message timeout window. Confirmed September 2, 2026: the queue is empty — exim -bpc returns 0, with zero frozen messages — and it is empty because mail is being delivered, not because it expired. The current mail log carries 1,791 successful deliveries, 566 of them on September 2 alone, against zero 550-5.7.28 rejections on each of the last three days. New freezes have stopped: the server froze roughly 1,500 to 2,500 messages a day from August 10 through August 20, then one on August 21 and one since. That one — on September 1 — was not the Gmail loop but an undeliverable local bounce sent to a malformed ‘ABRT Daemon’ address; it cleared itself on September 2 at 11:05 under exim’s own error-message timer, and nothing has frozen in the time since. Root mail now resolves locally to alerts@system.communitynewspapers.com instead of aliasing onward to the blocked mailbox, which is the condition that fed the loop.
  • Google Bulk Sender delisting submitted for 72.52.179.212 — proof: the submission reference, plus the daily 550-5.7.28 count trending to zero
  • Queue-depth alerting pointed at a destination that works, plus a one-page on-call runbook — proof: the…Queue-depth alerting pointed at a destination that works, plus a one-page on-call runbook — proof: the runbook, and a test alert that arrives
Deliverables — 4 of 4 done, snapshot Sep 1, 2026:
  • /etc/cxs/cxs.ignore created, excluding the WP Super Cache tree and the other self-regenerating directories —…/etc/cxs/cxs.ignore created, excluding the WP Super Cache tree and the other self-regenerating directories — proof: the file itself, plus the cxswatch restart
  • Scan-mail volume verified down from roughly 1,500 a day to effectively zero — proof: 24-hour exim_mainlog counts, before and after
  • One clean full scan against the corrected exclusion set, so a zero-threat result is a genuine all-clear —…One clean full scan against the corrected exclusion set, so a zero-threat result is a genuine all-clear — proof: the scan report of August 23, covering 5,930,711 files against a 5,925,063-file baseline (100.1%) and reading 306,173 MB, with zero directories skipped on the file-count limit and Viruses found: 0 on all six document roots. The earlier run that reported complete on August 21 is withdrawn: the scanner's file-count limit defaulted to 10,000 and silently skipped any larger directory, so it read about 4% of the files and none of the media library while still printing a clean result. That defect was corrected and the scan re-run over 18h 52m. Its three flagged PHP exploit fingerprints — footer files in three inactive themes, unchanged since 2022 and never executed by the live site — were archived out of the document root and retained at /root/cn-archive/themes-20260825/, verified absent from the live site. One stated limit: 36 files exceed the virus engine's 100 MB per-file ceiling and are never passed to it, whatever the scanner reports.
  • A retention policy applied to the 17 GB / 77,579-file page-cache directory — proof: du -sh before and after, plus the retention setting
Part 1 — Email authentication and delivery logging ($450.00)
  • DKIM enabled and published for cnews.net, which has none — proof: dig TXT google._domainkey.cnews.net, before and after
  • DMARC published for cnews.net and communitynewspapers.com at p=none monitoring, so nothing legitimate can be…DMARC published for cnews.net and communitynewspapers.com at p=none monitoring, so nothing legitimate can be rejected while we watch — proof: dig TXT _dmarc on both
  • Email logging switched on in Easy WP SMTP plus a weekly delivery digest, so a failed lead notification is…Email logging switched on in Easy WP SMTP plus a weekly delivery digest, so a failed lead notification is visible instead of silent — proof: the log table populated, and the first digest delivered
  • The two stale Microsoft 365 verification records retired — proof: dig before and after
Part 2 — Retire the stale GoDaddy mail-client endpoints ($150.00)
  • The existing DNS zone exported and archived before a single record is touched — proof: the saved export
  • webmail.cnews.net and mail.cnews.net repointed to Google, with the Workspace custom URL on, so a webmail…webmail.cnews.net and mail.cnews.net repointed to Google, with the Workspace custom URL on, so a webmail bookmark lands in the real mailbox — proof: dig CNAME plus a loading webmail address
  • imap.cnews.net, pop.cnews.net and smtp.cnews.net archived then removed — they cannot point at Google without…imap.cnews.net, pop.cnews.net and smtp.cnews.net archived then removed — they cannot point at Google without breaking the certificate — proof: dig before and after
  • A one-page reconfiguration note for your staff with the settings that work — imap.gmail.com port 993,…A one-page reconfiguration note for your staff with the settings that work — imap.gmail.com port 993, smtp.gmail.com port 587, and the app password Google requires — proof: the note, delivered
  • The specific @cnews.net mailbox reported as not receiving checked against that note — proof: the incoming…The specific @cnews.net mailbox reported as not receiving checked against that note — proof: the incoming server it is configured against, before and after
Deliverables — 8 of 8 done, snapshot Sep 2, 2026:
  • The current state read off a real delivered newsletter rather than inferred from DNS — proof: the…The current state read off a real delivered newsletter rather than inferred from DNS — proof: the Authentication-Results header from a campaign in a subscriber's inbox, captured before anything changes
  • The exact records collected from EmailOctopus's Domain Authentication screen and the Amazon SES console…The exact records collected from EmailOctopus's Domain Authentication screen and the Amazon SES console behind it — proof: the three signing record names and values were captured verbatim from the console on August 28, 2026 at 18:16 UTC, one minute after Amazon generated the keys at 18:15:53 UTC and before a single one was entered into your DNS, and they are recorded twice — once as the console's own downloaded CSV and once as a written paste sheet. The SPF include string was captured the same way, alongside your existing SPF record quoted verbatim so it could be compared afterwards.
  • The existing communitynewspapers.com zone exported and archived before a single record is touched — proof: the saved export, timestamped
  • Amazon authorised to send as your domain without touching your one existing SPF record — proof: dig TXT…Amazon authorised to send as your domain without touching your one existing SPF record — proof: dig TXT communitynewspapers.com from two independent resolvers returns exactly one SPF record, still v=spf1 include:_spf.google.com ip4:72.52.179.212 ~all, unchanged. To be plain about what we did and did not do: we did not add the Amazon include to that record, and we did not add a second one. Amazon's own recommended route was used instead — a custom return-path subdomain carrying its own SPF, covered in the next items — under which the receiving mail server checks the return-path domain rather than your main record, so an include on your main record would have done nothing for the newsletter. Your Google Workspace mail is therefore untouched, which was the risk this item existed to prevent.
  • All three Amazon signing records published — a partial set authenticates nothing — proof: dig CNAME on each…All three Amazon signing records published — a partial set authenticates nothing — proof: dig CNAME on each of the three names returns its own matching Amazon target, each serving a different signing key, and Amazon's own console independently reports DKIM status Success with signing enabled for exactly these three.
  • A return-path subdomain configured so the address receivers check ends in communitynewspapers.com instead of…A return-path subdomain configured so the address receivers check ends in communitynewspapers.com instead of amazonses.com — proof: mail.communitynewspapers.com answers MX 10 feedback-smtp.us-east-1.amazonses.com and TXT v=spf1 include:amazonses.com ~all, Amazon's console reports that return-path domain Success, and a newsletter delivered on September 1 shows the receiving server checking 010001a05c897e90-…@mail.communitynewspapers.com and passing it.
  • Every record confirmed to have propagated and to validate, not merely to exist — proof: all five records were…Every record confirmed to have propagated and to validate, not merely to exist — proof: all five records were queried from two independent public resolvers, Google 8.8.8.8 and Cloudflare 1.1.1.1, and returned byte-identical answers, with each signing record's key fingerprinted to confirm a real key is being served rather than an empty record. Amazon's console reports Success on domain verification, DKIM and the return-path domain. Validation is separately confirmed by receivers actually accepting the signatures below.
  • A campaign sent and its headers read back — proof: the September 1, 2026 campaign "Tired of Waiting in Miami…A campaign sent and its headers read back — proof: the September 1, 2026 campaign "Tired of Waiting in Miami Traffic?!" arrived at an address of ours on your own domain, and its Authentication-Results header reads dkim=pass matching communitynewspapers.com, spf=pass matching mail.communitynewspapers.com, and dmarc=pass. Beside the before header captured in the first item, where the only signature present belonged to amazonses.com and nothing matched your domain, that is the whole change in one line. It is not a single sample: across 1,204,433 messages of receiver-reported data, your newsletter measured 0.0% matching your domain every day through August 29, then 99.9% on August 31 and 100.0% on September 1.
Deliverables — 0 of 4 done, snapshot Aug 26, 2026:
  • Every @cnews.net and @communitynewspapers.com mailbox in use listed against the staff member who reads it —…Every @cnews.net and @communitynewspapers.com mailbox in use listed against the staff member who reads it — proof: the list, confirmed back by you
  • Each staff member confirmed to read mail through Google Workspace or Gmail webmail, not a legacy client still…Each staff member confirmed to read mail through Google Workspace or Gmail webmail, not a legacy client still pointed at GoDaddy — proof: per person, the mail app and incoming server
  • Any mailbox still on stale GoDaddy IMAP/POP/SMTP settings corrected with the staff member on the call —…Any mailbox still on stale GoDaddy IMAP/POP/SMTP settings corrected with the staff member on the call — proof: the before and after settings for each
  • Anyone found to have been silently missing incoming mail flagged to you directly, with what was missed and…Anyone found to have been silently missing incoming mail flagged to you directly, with what was missed and since when — proof: a named list, or an explicit 'none found'
Deliverables — 5 of 5 done, snapshot Sep 2, 2026:
  • The existing zone archived before a single record was touched — proof: the authoritative record-by-record…The existing zone archived before a single record was touched — proof: the authoritative record-by-record export of August 28, held under a SHA256 manifest that still verifies today, showing the five original routing records exactly as they stood.
  • Your mail confirmed to be working before anything changed, rather than taking the console's word for it —…Your mail confirmed to be working before anything changed, rather than taking the console's word for it — proof: the old and the new Google mail front ends both answer on the same connection with an identical Gmail greeting, so both hand mail to the same place; no cnews.net message bounced in the thirty days before the change, and the combined invoice reached susan@cnews.net on August 27 with no failure notice.
  • The one genuine risk identified and designed around — your registrar cannot exchange routing records in a…The one genuine risk identified and designed around — your registrar cannot exchange routing records in a single action, and the cnews.net web addresses do not accept mail, so any moment with no routing record in place would have held every incoming message instead of delivering it. Proof: both web addresses tested and found to refuse mail connections. The change was made on its own so that anything unusual afterwards would have a single, identifiable cause.
  • The five original routing records replaced with the single record Google now specifies — proof: the archived…The five original routing records replaced with the single record Google now specifies — proof: the archived August 28 export listing aspmx.l.google.com, alt1, alt2, aspmx2.googlemail.com and aspmx3.googlemail.com, set against today's answer from your domain's own nameserver listing smtp.google.com alone, with the zone's internal change counter moving from 2026082204 to 2026090107.
  • Google's Email setup status page for cnews.net read back and confirmed clear on mail routing — proof: the…Google's Email setup status page for cnews.net read back and confirmed clear on mail routing — proof: the before and after views of that page in the Workspace admin console, Incorrect set against Complete.

Notas

14 of the 30 deliverables on this invoice were already checked off in our delivery system when it was issued — a snapshot taken August 26, 2026; the live version is on your portal. Items 4, 5 and 6 are included at no charge, itemized in full so the scope you are owed is on the record. Payment methods: Stripe (card) or Zelle → EDILBERTO MORILLO · 786-426-4902.

⬇ Descargar PDF← Volver a Pagos y Facturas

NeedAWebNow.com · Portal del Cliente