cert
cert-1
cert-2

Pass LPI 102-500 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
102-500 Exam - Verified By Experts
102-500 Premium Bundle
$29.98

102-500 Premium Bundle

$79.99
$109.97
  • Premium File 120 Questions & Answers. Last update: Nov 13, 2026
  • Training Course 126 Video Lectures
  • Study Guide 962 Pages
 
$109.97
$79.99
accept 15 downloads in last 7 days
block-screenshots
Purchase LPI 102-500 Exam Training Products Individually
LPI 102-500 Premium File
Premium File 120 Q&A
$76.99$69.99
LPI 102-500 Video Training Course
Training Course 126 Lectures
$21.99 $19.99
LPI 102-500 PDF Study Guide
Study Guide 962 Pages
$21.99 $19.99
LPI 102-500 Practice Test 40

Question 390

A team maintaining a Linux host reports: Two users forward messages to each other and produce repeated deliveries that fill the mail queue. Which TWO complementary steps provide the best corrective action and its most direct diagnostic verification? Select TWO answers.

  1. Inspect CUPS printer state, queue name and job ID, view lpq or lpstat output, and confirm the target job disappears after cancellation.
  2. Configure a supported per-user ~/.forward destination and validate permissions and loop prevention, or select an approved server-side forwarding mechanism.
  3. Chain two ~/.forward files to one another and assume the MTA will always infer the intended final recipient without loops.
  4. Use suitable logrotate frequency, size, retention and postrotate or copytruncate strategy based on service behavior and test the rotation safely.
  5. Inspect ~/.forward ownership and content, trace headers and MTA delivery logs, and send a single controlled test message.

Explanation

Correct Answers

B:

Recommended administrative action: Configure a supported per-user ~/.forward destination and validate permissions and loop prevention, or select an approved server-side forwarding mechanism. Linux principle: User-level forwarding and system aliases apply at different scope, and circular forwarding can generate repeated messages or delivery failures.

E:

Most direct verification evidence: Inspect ~/.forward ownership and content, trace headers and MTA delivery logs, and send a single controlled test message. Linux principle: User-level forwarding and system aliases apply at different scope, and circular forwarding can generate repeated messages or delivery failures.

Incorrect Answers

A:

That option would inspect CUPS printer state, queue name and job ID, view lpq or lpstat output, and confirm the target job disappears after cancellation, but it addresses a different concern. User-level forwarding and system aliases apply at different scope, and circular forwarding can generate repeated messages or delivery failures.

C:

This shortcut is unsafe for the present Linux issue: Chain two ~/.forward files to one another and assume the MTA will always infer the intended final recipient without loops. User-level forwarding and system aliases apply at different scope, and circular forwarding can generate repeated messages or delivery failures.

D:

That option would use suitable logrotate frequency, size, retention and postrotate or copytruncate strategy based on service behavior and test the rotation safely, but it addresses a different concern. User-level forwarding and system aliases apply at different scope, and circular forwarding can generate repeated messages or delivery failures.

Question 391

While verifying a Linux change request, an engineer finds: An alert system reports successful handoff to a local mail command but dozens of messages remain undelivered in the MTA queue. Which administrative step is the MOST appropriate way to resolve this issue? Select ONE best answer.

  1. Configure reachable approved chrony sources and check tracking and source selection before declaring time synchronization healthy.
  2. Treat exit status zero from a local mail submission as a receipt from the remote mailbox and repeatedly send every queued message again.
  3. Inspect pending mail via mailq or a supported MTA queue command, identify the deferred-delivery reason and repair transport before replaying messages.
  4. Edit approved local alias mappings and run newaliases as required by the installed MTA, then test delivery and the local queue.

Explanation

Correct Answer

C:

Recommended administrative action: Inspect pending mail via mailq or a supported MTA queue command, identify the deferred-delivery reason and repair transport before replaying messages.

Incorrect Answers

A:

That option would configure reachable approved chrony sources and check tracking and source selection before declaring time synchronization healthy, but it addresses a different concern. Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition.

B:

That option would treat exit status zero from a local mail submission as a receipt from the remote mailbox and repeatedly send every queued message again, but it addresses a different concern. Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition.

D:

This alternative addresses Mail aliases and newaliases database updates, not the specific issue of Mail queue inspection and resend decisions: Edit approved local alias mappings and run newaliases as required by the installed MTA, then test delivery and the local queue. Linux principle: Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition. Appropriate response: Inspect pending mail via mailq or a supported MTA queue command, identify the deferred-delivery reason and repair transport before replaying messages. Root-cause evidence: Review queue IDs, delivery attempts, logs, DNS or transport errors and results after a controlled retry. Independent acceptance: The backlog drains for the intended destinations and repeat sends are not introduced merely to mask a routing failure.

Question 392

A Linux administrator investigates the following system incident: An alert system reports successful handoff to a local mail command but dozens of messages remain undelivered in the MTA queue. Which Linux behavior or technical principle BEST explains why the issue occurs? Select ONE best answer.

  1. Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition.
  2. Systemd-journald may use volatile or persistent storage depending on configuration and directory availability; querying only the current boot cannot prove retention.
  3. Linux distinguishes its running system clock from the hardware real-time clock, while the timezone transforms the displayed civil time without changing the UTC instant.
  4. Treat exit status zero from a local mail submission as a receipt from the remote mailbox and repeatedly send every queued message again.

Explanation

Correct Answer

A:

Relevant Linux operating principle: Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition.

Incorrect Answers

B:

This alternative addresses Persistent systemd journal storage, not the specific issue of Mail queue inspection and resend decisions: Systemd-journald may use volatile or persistent storage depending on configuration and directory availability; querying only the current boot cannot prove retention. Linux principle: Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition. Appropriate response: Inspect pending mail via mailq or a supported MTA queue command, identify the deferred-delivery reason and repair transport before replaying messages. Root-cause evidence: Review queue IDs, delivery attempts, logs, DNS or transport errors and results after a controlled retry. Independent acceptance: The backlog drains for the intended destinations and repeat sends are not introduced merely to mask a routing failure.

C:

This alternative addresses System clock versus real-time clock and UTC policy, not the specific issue of Mail queue inspection and resend decisions: Linux distinguishes its running system clock from the hardware real-time clock, while the timezone transforms the displayed civil time without changing the UTC instant. Linux principle: Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition. Appropriate response: Inspect pending mail via mailq or a supported MTA queue command, identify the deferred-delivery reason and repair transport before replaying messages. Root-cause evidence: Review queue IDs, delivery attempts, logs, DNS or transport errors and results after a controlled retry. Independent acceptance: The backlog drains for the intended destinations and repeat sends are not introduced merely to mask a routing failure.

D:

That option would treat exit status zero from a local mail submission as a receipt from the remote mailbox and repeatedly send every queued message again, but it addresses a different concern. Independent acceptance: The backlog drains for the intended destinations and repeat sends are not introduced merely to mask a routing failure.

Question 393

On a production Linux workstation or server, a technician observes: An alert system reports successful handoff to a local mail command but dozens of messages remain undelivered in the MTA queue. Which evidence or command result MOST directly tests the suspected root cause? Select ONE best answer.

  1. Run `logrotate -d` or a controlled forced rotation, inspect the daemon's file handles, timestamps and retained compressed archives.
  2. Treat exit status zero from a local mail submission as a receipt from the remote mailbox and repeatedly send every queued message again.
  3. Inspect `chronyc tracking`, `chronyc sources -v`, configured servers or pools, network reachability and timedatectl synchronization status.
  4. Review queue IDs, delivery attempts, logs, DNS or transport errors and results after a controlled retry.

Explanation

Correct Answer

D:

Most direct verification evidence: Review queue IDs, delivery attempts, logs, DNS or transport errors and results after a controlled retry.

Incorrect Answers

A:

That option would run `logrotate -d` or a controlled forced rotation, inspect the daemon's file handles, timestamps and retained compressed archives, but it addresses a different concern. Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition.

B:

This shortcut is unsafe for the present Linux issue: Treat exit status zero from a local mail submission as a receipt from the remote mailbox and repeatedly send every queued message again. It cannot establish a safe correction.

C:

That option would inspect `chronyc tracking`, `chronyc sources -v`, configured servers or pools, network reachability and timedatectl synchronization status, but it addresses a different concern. Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition.

Question 394

During an LPIC-1 practice lab, the operator encounters this condition: An alert system reports successful handoff to a local mail command but dozens of messages remain undelivered in the MTA queue. Which observed outcome BEST confirms a successful and properly scoped correction? Select ONE best answer.

  1. Retained journal data stays readable within approved storage limits and recovered records can be analyzed from their copied location.
  2. A test event of the selected class appears at the required local or remote destination without unrelated messages being silently dropped.
  3. Treat exit status zero from a local mail submission as a receipt from the remote mailbox and repeatedly send every queued message again.
  4. The backlog drains for the intended destinations and repeat sends are not introduced merely to mask a routing failure.

Explanation

Correct Answer

D:

Observable acceptance criterion: The backlog drains for the intended destinations and repeat sends are not introduced merely to mask a routing failure.

Incorrect Answers

A:

This alternative addresses Journal vacuuming and offline rescue analysis, not the specific issue of Mail queue inspection and resend decisions: Retained journal data stays readable within approved storage limits and recovered records can be analyzed from their copied location. Linux principle: Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition. Appropriate response: Inspect pending mail via mailq or a supported MTA queue command, identify the deferred-delivery reason and repair transport before replaying messages. Root-cause evidence: Review queue IDs, delivery attempts, logs, DNS or transport errors and results after a controlled retry. Independent acceptance: The backlog drains for the intended destinations and repeat sends are not introduced merely to mask a routing failure.

B:

This alternative addresses Rsyslog facility priority and central forwarding, not the specific issue of Mail queue inspection and resend decisions: A test event of the selected class appears at the required local or remote destination without unrelated messages being silently dropped. Linux principle: Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition. Appropriate response: Inspect pending mail via mailq or a supported MTA queue command, identify the deferred-delivery reason and repair transport before replaying messages. Root-cause evidence: Review queue IDs, delivery attempts, logs, DNS or transport errors and results after a controlled retry. Independent acceptance: The backlog drains for the intended destinations and repeat sends are not introduced merely to mask a routing failure.

C:

This shortcut is unsafe for the present Linux issue: Treat exit status zero from a local mail submission as a receipt from the remote mailbox and repeatedly send every queued message again. Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition.

Question 395

A helpdesk escalation describes this Linux behavior: An alert system reports successful handoff to a local mail command but dozens of messages remain undelivered in the MTA queue. Which misleading assumption MOST directly contributes to this failure and should be rejected? Select ONE best answer.

  1. Chain two ~/.forward files to one another and assume the MTA will always infer the intended final recipient without loops.
  2. Assume pinging pool.ntp.org proves a running server's clock is synchronized and that editing a file automatically reloads the time daemon.
  3. Delete the original PDF as a substitute for canceling a queued print job and indiscriminately purge all printers for one stalled queue.
  4. Treat exit status zero from a local mail submission as a receipt from the remote mailbox and repeatedly send every queued message again.

Explanation

Correct Answer

D:

Reject this specific misconception: Treat exit status zero from a local mail submission as a receipt from the remote mailbox and repeatedly send every queued message again. It incorrectly assumes behavior that conflicts with the observed Linux conditions.

Incorrect Answers

A:

This alternative addresses User mail forwarding and delivery loops, not the specific issue of Mail queue inspection and resend decisions: Chain two ~/.forward files to one another and assume the MTA will always infer the intended final recipient without loops. Linux principle: Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition. Appropriate response: Inspect pending mail via mailq or a supported MTA queue command, identify the deferred-delivery reason and repair transport before replaying messages. Root-cause evidence: Review queue IDs, delivery attempts, logs, DNS or transport errors and results after a controlled retry. Independent acceptance: The backlog drains for the intended destinations and repeat sends are not introduced merely to mask a routing failure.

B:

That option would assume pinging pool.ntp.org proves a running server's clock is synchronized and that editing a file automatically reloads the time daemon, but it addresses a different concern. Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition.

C:

This alternative addresses CUPS queue inspection and selective cancellation, not the specific issue of Mail queue inspection and resend decisions: Delete the original PDF as a substitute for canceling a queued print job and indiscriminately purge all printers for one stalled queue. Linux principle: Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition. Appropriate response: Inspect pending mail via mailq or a supported MTA queue command, identify the deferred-delivery reason and repair transport before replaying messages. Root-cause evidence: Review queue IDs, delivery attempts, logs, DNS or transport errors and results after a controlled retry. Independent acceptance: The backlog drains for the intended destinations and repeat sends are not introduced merely to mask a routing failure.

Question 396

An operations handoff identifies this problem: A helpdesk repeatedly resends email alerts instead of investigating a deferred delivery queue and creates duplicate notifications. Which administrative step is the MOST appropriate way to resolve this issue? Select ONE best answer.

  1. Treat exit status zero from a local mail submission as a receipt from the remote mailbox and repeatedly send every queued message again.
  2. Inspect pending mail via mailq or a supported MTA queue command, identify the deferred-delivery reason and repair transport before replaying messages.
  3. Configure a facility-and-priority selector with the intended action and a supported remote target, then test message routing and transport.
  4. Edit approved local alias mappings and run newaliases as required by the installed MTA, then test delivery and the local queue.

Explanation

Correct Answer

B:

Recommended administrative action: Inspect pending mail via mailq or a supported MTA queue command, identify the deferred-delivery reason and repair transport before replaying messages.

Incorrect Answers

A:

This shortcut is unsafe for the present Linux issue: Treat exit status zero from a local mail submission as a receipt from the remote mailbox and repeatedly send every queued message again. Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition.

C:

That option would configure a facility-and-priority selector with the intended action and a supported remote target, then test message routing and transport, but it addresses a different concern. Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition.

D:

This alternative addresses Mail aliases and newaliases database updates, not the specific issue of Mail queue inspection and resend decisions: Edit approved local alias mappings and run newaliases as required by the installed MTA, then test delivery and the local queue. Linux principle: Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition. Appropriate response: Inspect pending mail via mailq or a supported MTA queue command, identify the deferred-delivery reason and repair transport before replaying messages. Root-cause evidence: Review queue IDs, delivery attempts, logs, DNS or transport errors and results after a controlled retry. Independent acceptance: The backlog drains for the intended destinations and repeat sends are not introduced merely to mask a routing failure.

Question 397

A team maintaining a Linux host reports: A helpdesk repeatedly resends email alerts instead of investigating a deferred delivery queue and creates duplicate notifications. Which Linux behavior or technical principle BEST explains why the issue occurs? Select ONE best answer.

  1. Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition.
  2. Linux distinguishes its running system clock from the hardware real-time clock, while the timezone transforms the displayed civil time without changing the UTC instant.
  3. Treat exit status zero from a local mail submission as a receipt from the remote mailbox and repeatedly send every queued message again.
  4. Mail alias files map local recipient names to delivery targets, and some MTAs use a compiled alias database that must be rebuilt after changes.

Explanation

Correct Answer

A:

Relevant Linux operating principle: Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition.

Incorrect Answers

B:

This alternative addresses System clock versus real-time clock and UTC policy, not the specific issue of Mail queue inspection and resend decisions: Linux distinguishes its running system clock from the hardware real-time clock, while the timezone transforms the displayed civil time without changing the UTC instant. Linux principle: Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition. Appropriate response: Inspect pending mail via mailq or a supported MTA queue command, identify the deferred-delivery reason and repair transport before replaying messages. Root-cause evidence: Review queue IDs, delivery attempts, logs, DNS or transport errors and results after a controlled retry. Independent acceptance: The backlog drains for the intended destinations and repeat sends are not introduced merely to mask a routing failure.

C:

This shortcut is unsafe for the present Linux issue: Treat exit status zero from a local mail submission as a receipt from the remote mailbox and repeatedly send every queued message again. It cannot establish a safe correction. Linux principle: Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition.

D:

This alternative addresses Mail aliases and newaliases database updates, not the specific issue of Mail queue inspection and resend decisions: Mail alias files map local recipient names to delivery targets, and some MTAs use a compiled alias database that must be rebuilt after changes. Linux principle: Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition. Appropriate response: Inspect pending mail via mailq or a supported MTA queue command, identify the deferred-delivery reason and repair transport before replaying messages. Root-cause evidence: Review queue IDs, delivery attempts, logs, DNS or transport errors and results after a controlled retry. Independent acceptance: The backlog drains for the intended destinations and repeat sends are not introduced merely to mask a routing failure.

Question 398

While verifying a Linux change request, an engineer finds: A helpdesk repeatedly resends email alerts instead of investigating a deferred delivery queue and creates duplicate notifications. Which evidence or command result MOST directly tests the suspected root cause? Select ONE best answer.

  1. Review queue IDs, delivery attempts, logs, DNS or transport errors and results after a controlled retry.
  2. Inspect /etc/ntp.conf or /etc/chrony.conf, verify service state, view ntpq -p or chronyc sources and check UDP connectivity.
  3. Treat exit status zero from a local mail submission as a receipt from the remote mailbox and repeatedly send every queued message again.
  4. Inspect `journalctl -u name.service --since ...`, `-p` selections, boot switches and the original message fields.

Explanation

Correct Answer

A:

Most direct verification evidence: Review queue IDs, delivery attempts, logs, DNS or transport errors and results after a controlled retry.

Incorrect Answers

B:

That option would inspect /etc/ntp.conf or /etc/chrony.conf, verify service state, view ntpq -p or chronyc sources and check UDP connectivity, but it addresses a different concern. Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition.

C:

This shortcut is unsafe for the present Linux issue: Treat exit status zero from a local mail submission as a receipt from the remote mailbox and repeatedly send every queued message again. It cannot establish a safe correction. Linux principle: Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition. Appropriate response: Inspect pending mail via mailq or a supported MTA queue command, identify the deferred-delivery reason and repair transport before replaying messages. Root-cause evidence: Review queue IDs, delivery attempts, logs, DNS or transport errors and results after a controlled retry. Independent acceptance: The backlog drains for the intended destinations and repeat sends are not introduced merely to mask a routing failure.

D:

That option would inspect `journalctl -u name.service --since .`, `-p` selections, boot switches and the original message fields, but it addresses a different concern. Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition.

Question 399

A Linux administrator investigates the following system incident: A helpdesk repeatedly resends email alerts instead of investigating a deferred delivery queue and creates duplicate notifications. Which observed outcome BEST confirms a successful and properly scoped correction? Select ONE best answer.

  1. The host tracks an approved source with acceptable measured offset and remains time-synchronized under representative network conditions.
  2. The backlog drains for the intended destinations and repeat sends are not introduced merely to mask a routing failure.
  3. Retained journal data stays readable within approved storage limits and recovered records can be analyzed from their copied location.
  4. Treat exit status zero from a local mail submission as a receipt from the remote mailbox and repeatedly send every queued message again.

Explanation

Correct Answer

B:

Observable acceptance criterion: The backlog drains for the intended destinations and repeat sends are not introduced merely to mask a routing failure.

Incorrect Answers

A:

This alternative addresses Chrony synchronization and source state, not the specific issue of Mail queue inspection and resend decisions: The host tracks an approved source with acceptable measured offset and remains time-synchronized under representative network conditions. Linux principle: Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition. Appropriate response: Inspect pending mail via mailq or a supported MTA queue command, identify the deferred-delivery reason and repair transport before replaying messages. Root-cause evidence: Review queue IDs, delivery attempts, logs, DNS or transport errors and results after a controlled retry. Independent acceptance: The backlog drains for the intended destinations and repeat sends are not introduced merely to mask a routing failure.

C:

This alternative addresses Journal vacuuming and offline rescue analysis, not the specific issue of Mail queue inspection and resend decisions: Retained journal data stays readable within approved storage limits and recovered records can be analyzed from their copied location. Linux principle: Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition. Appropriate response: Inspect pending mail via mailq or a supported MTA queue command, identify the deferred-delivery reason and repair transport before replaying messages. Root-cause evidence: Review queue IDs, delivery attempts, logs, DNS or transport errors and results after a controlled retry. Independent acceptance: The backlog drains for the intended destinations and repeat sends are not introduced merely to mask a routing failure.

D:

This shortcut is unsafe for the present Linux issue: Treat exit status zero from a local mail submission as a receipt from the remote mailbox and repeatedly send every queued message again. Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition.

Question 400

On a production Linux workstation or server, a technician observes: A helpdesk repeatedly resends email alerts instead of investigating a deferred delivery queue and creates duplicate notifications. Which THREE elements together give the appropriate corrective action, direct diagnostic evidence and observable acceptance result? Select THREE answers.

  1. Inspect /etc/rsyslog.conf rules, generated `logger` messages, receiver logs and network or TLS transport state.
  2. Treat exit status zero from a local mail submission as a receipt from the remote mailbox and repeatedly send every queued message again.
  3. Inspect pending mail via mailq or a supported MTA queue command, identify the deferred-delivery reason and repair transport before replaying messages.
  4. The backlog drains for the intended destinations and repeat sends are not introduced merely to mask a routing failure.
  5. Review queue IDs, delivery attempts, logs, DNS or transport errors and results after a controlled retry.
  6. Apply supported journal size or age retention and `journalctl --vacuum-*` controls; use `journalctl --directory` or `--file` to inspect saved journals.

Explanation

Correct Answers

C:

Recommended administrative action: Inspect pending mail via mailq or a supported MTA queue command, identify the deferred-delivery reason and repair transport before replaying messages. Linux principle: Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition.

D:

Observable acceptance criterion: The backlog drains for the intended destinations and repeat sends are not introduced merely to mask a routing failure. Linux principle: Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition.

E:

Most direct verification evidence: Review queue IDs, delivery attempts, logs, DNS or transport errors and results after a controlled retry. Linux principle: Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition.

Incorrect Answers

A:

This alternative addresses Rsyslog facility priority and central forwarding, not the specific issue of Mail queue inspection and resend decisions: Inspect /etc/rsyslog.conf rules, generated `logger` messages, receiver logs and network or TLS transport state.

B:

This shortcut is unsafe for the present Linux issue: Treat exit status zero from a local mail submission as a receipt from the remote mailbox and repeatedly send every queued message again. Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition.

F:

That option would apply supported journal size or age retention and `journalctl --vacuum-*` controls; use `journalctl --directory` or `--file` to inspect saved journals, but it addresses a different concern. Submitting a message to an MTA queue is not proof of final recipient delivery; queue status and remote response determine disposition.

LPI Level 1 (102-500) Practice Tests