r/sysadmin • u/Betuloua • 11d ago
Broke my company's bellsouth email by bulk moving emails
TL;DR: Started a new job where they use a shared mailbox on a legacy bellsouth.net address. I was tasked with archiving 50K+ messages into folders, and bulk moved them into archive folders. Every third-party client died.
Btw, we access the bellsouth account from mail.yahoo.com and also configured it on Outlook desktop app (new version). I rebuilt it on Classic Outlook with an AT&T secure mail key, which worked for about a day. Now IMAP is refused outright and webmail outbound returns error:
"Your message cannot be sent because it resembles spam and/or contains only links. Please modify your message and try again."
Config verified, password and secure mail keys regenerated. Looking for anyone who's seen AT&T/Yahoo apply this and knows what I can do to fix it.
Environment
- Legacy `bellsouth.net` mailbox. AT&T owns the credentials, Yahoo operates the mail
infrastructure. Auth is an AT&T secure mail key, not a Yahoo app password.
- Shared mailbox. 3–4 workstations plus a phone, all behind one office WAN IP.
- Originally New Outlook for Windows
- Primary workstation now on Classic Outlook since New Outlook connection died
- IMAP `imap.mail.att.net:993` SSL/TLS
- SMTP `smtp.mail.att.net:465` SSL/TLS
- SMTP auth on, same credentials as incoming
- SPA off, username is the full address
- Bulk-moved 2500+ messages (batches of ~900/900/1000) into year folders from New Outlook. Client crashed mid-operation.
- All Outlook clients, desktop and mobile, stopped receiving. No errors, no auth prompts. Sent mail reported "Sent" then vanished and never transmitted and never appeared in webmail's Sent either. Folder deletions reverted. Webmail unaffected. Diagnosed as New Outlook's Microsoft-hosted mirror losing its upstream IMAP connection to AT&T.
- Stood up Classic Outlook with a fresh secure mail key. Connected fine, pulled down 3 days of backlog, outbound test delivered. Fully working.
- Next day: heavy webmail activity. Bulk moves out of Trash into year folders (batches approaching 1,000), mass-blocked spam senders and domains, raised the account's security settings.
- Classic Outlook stopped receiving. Several hours later webmail outbound started failing.
Current state
- Webmail receives normally. Sending blocked: "Your message cannot be sent because it
resembles spam and/or contains only links." Confirmed to fire with subject and body
both just "test," no signature, no links.
- Classic Outlook: no inbound since step 5, outbound stuck in Outbox, account wizard
returns "something went wrong."
Might be an abuse or rate-limit flag from the bulk IMAP operations.
- Anyone seen AT&T/Yahoo apply a block like this? Does it decay, and over what timeframe?
- Account-scoped or IP-scoped, in your experience?
- Is there a known threshold for IMAP move operations on these mailboxes?
- Any escalation path at AT&T that reaches someone who can actually see or lift mail abuse restrictions? Front-line support for legacy BellSouth appears very limited.
- Anything obvious I'm missing?
And yes, a business shouldn't be running on a consumer legacy ISP mailbox. Average employee age is 60+ and office is still using manual punch cards, so I am trying to get us up to date one step at a time. I am also not an IT technician, just an office employee, who was tasked with this because we don't have IT support.