Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
TetraWiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Training 2022 Linux team/
(section)
Page
Discussion
English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Training on Mail Sending & Receving Problem & Bouncing Problem Part-5 . Dated 07 Feb 2022 - Tetra Support Staff - Biswajit Banerjee== {{#ev:youtube|Zm_i3TkGzds|640}} '''Video summary:''' "Training Sending,Recieveing Bouncing part5" -- shifts to diagnosing actual bounce cases, live, on one of Tetra's real relay servers (`server-relay1.tetrain.com`, confirming there are three relay servers total as mentioned in Part 4). Opens with the retry logic behind Postfix queuing: a failed outbound message isn't simply dropped -- it retries on a roughly logarithmic backoff (e.g. ~6 minutes, then ~30 minutes, then hours, then up to a day later), and the specific error encountered determines how long the next retry waits (a temporarily unavailable server retries soon; a nonexistent domain waits much longer). Demonstrates searching the relay's Postfix mail log for "bounce" and walks through several real bounce cases found live: one where a message triggers a bounce/delivery notification for unclear reasons requiring deeper log tracing by message ID; one where a specific recipient address is explicitly rejected by the receiving mail server (meaning the sender's own admin needs to contact the receiving domain's admin, since the sending side has no control over another domain's rejection policy); and one caused by a missing/incomplete SPF record on the sender's domain -- diagnosed by pulling the domain's TXT/SPF record via MXToolbox and confirming the sending relay server's IP isn't authorized in it, which is why the receiving Gmail-side server rejected the mail as likely spam. Notes bounce causes are numerous and case-specific, and that this topic continues into the next session. Ends mid-topic due to time (session capped at ~30 minutes as usual for this series).
Summary:
Please note that all contributions to TetraWiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
TetraWiki:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)