You are not logged in.
I am setting up a postfix server on Arch and I want to get to the bottom of the term email "submission" and "relay". So what does this really mean?
In my head I have two possible scenarios:
SCENARIO 1
What the terms mean is:
- "relaying" ⟹ "event of sending email using SMTP protocol"
- "submission" ⟹ "event of recieving using SMTP protocol"
In this scenario I have to always tell who in the email chain I am refering to.
SCENARIO 2:
What the terms mean is:
- "relaying" ⟹ "event of email passing through any device using SMTP protocol (email is recieved & sent ie. forwarded)"
- "submission" ⟹ "event of sending using SMTP protocol"
So which scenario is correct?
Last edited by 71GA (2020-12-22 18:49:28)
C, ARM, ARM assembly, HTML, CSS, JS, Linux
Offline
I think scenario 2 is closer: certainly for "relaying" that sounds spot on. Relaying was first - that was the job of the server: relay outside mail to internal recipients and internal mail to outside recipients. Submission came later as people who might belong "inside" would connect from the "outside" (e.g., an employee of a company working from home and using the company email server to send their mail). Submission can be thought of as a superset of relaying: the server relays submissions, but it does much more than just relay for a submission. Submitted emails (but not relayed) may require authentication and may be rewritten.
So I'm not sure about "the even of sending using SMTP protocol" as your defintion. That may be the client / user's perspective, but for the server, submission is relay but with a few checks and potential modifications of the message first.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
An email system consists of the following modules...
[Client]
MUA--Mail User agent (Thunderbird)
[Mail Server]
MSA--Mail Submission Agent
MDA--Mail Delivery Agent
MTA-- Mail Transfer Agent
The MSA recieves an email from the MUA and checks it for format, errors and valid sender/reciever then either responds as undeliverable or hands it off to either the MDA or the MTA (for relaying). MTAs' can also respond as undeliverable
The MTA will relay the email to either another email server MTA within the enterprise where it will be handed off to the MDA or it will relay it to an Edge MTA for forwarding on to a destination MTA over the Internet according to DNS MX records.
The MDA stores the email until an MUA requests to read it (pushed to the client or just read on the server)
RFC 2476 message submission.
Last edited by Zod (2020-12-19 01:37:08)
Offline
Zod nails it.
Incase you want some background info how/why this happened, check https://en.wikipedia.org/wiki/Simple_Ma … ol#History .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Trilby's answer helped me the most. Thank you very much!
Last edited by 71GA (2020-12-20 19:13:47)
C, ARM, ARM assembly, HTML, CSS, JS, Linux
Offline
Trilby's answer helped me the most. Thank you very much!
Yes, he is great.
Please pu t the word SOLVED to your title.
A dog is a man's best friend.
Offline