1 Topic by mikek

  • mikek
  • Member
  • Offline
  • Registered: 2020-08-20
  • Posts: 22

Topic: MX stops working and starts again after reboot

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.7.1
- Deployed with downloadable installer
- Linux/BSD distribution name and version: Ubuntu 24.04.01
- Store mail accounts in which backend: MySQL
- Web server: Nginx
- Manage mail accounts with iRedAdmin
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

New installation of iRedMAil.
It works great for awhile. After a few hours, MX delivery stops working.
Sending email from an outside source to an iRedMail account doesn't get deliverd to the inbox and does not bounce. No error messages. Shows Sent.
Checking an iRedMail account using IMAP or Roundcube shows no errors and no new email.
Sending email from IMAP iRedMail account or Round Cube shows no errors and does not get delivered. Sits in Sent items folder.
Rebooting the Ubuntu server solves all problems and mail gets delivered again for a short time.
Repeat. Rebooting again gets it working again for awhile.
How should I debug this?
Which modules should I debug? I am somewhat new but have a basic understanding of iRedMail and good IT skills.
Which logs will help?

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by mikek

  • mikek
  • Member
  • Offline
  • Registered: 2020-08-20
  • Posts: 22

Re: MX stops working and starts again after reboot

The timestamps in this email header suggest that the server receives the email:

Date of email: Sat, 25 Jan 2025 01:12:21 -0800
Server received it: Sat, 25 Jan 2025 09:19:04 +0000 (UTC)
Received by AMVIS Sat, 25 Jan 2025 18:53:14 +0000 (UTC)
Rebot and delivered to INBOX: Sat, 25 Jan 2025 18:53:14 +0000 (UTC)


Return-Path: <19056-645-274477-905->
Delivered-To: xxxxx
Received: from xxxx (xxxxx [127.0.0.1])
    by xxxxx (Postfix) with ESMTP id 4YgP2f49sbzQk4l
    for <xxxxx>; Sat, 25 Jan 2025 18:53:14 +0000 (UTC)
X-Virus-Scanned: Debian amavis at xxxxx
X-Spam-Flag: NO
X-Spam-Score: 3.184
X-Spam-Level: ***
X-Spam-Status: No, score=3.184 tagged_above=2 required=6.2
tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
DMARC_PASS=-0.001, FROM_SUSPICIOUS_NTLD=1, FROM_SUSPICIOUS_NTLD_FP=1,
HTML_MESSAGE=0.001, RDNS_NONE=1.274, SPF_HELO_NONE=0.001, SPF_PASS=-0.001,
T_PDS_OTHER_BAD_TLD=0.01] autolearn=no autolearn_force=no
Authentication-Results: xxxxx (amavis); dkim=pass (2048-bit key)
header.d=glucoclean.top; domainkeys=pass (2048-bit key)
header.from=piano_courses@glucoclean.top header.d=glucoclean.top
Received: from xxxxx ([127.0.0.1])
by xxxxx (xxxxx [127.0.0.1]) (amavis, port 10024)
with ESMTP id AJX1OEQGx2hI for <xxxxx>;
Sat, 25 Jan 2025 18:53:14 +0000 (UTC)
Received: from eagle.glucoclean.top (unknown [71.4.35.222])
    by xxxxx (Postfix) with ESMTP id 4Yg8J86qbbzQlqF
    for <xxxxx>; Sat, 25 Jan 2025 09:19:04 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; s=k1; d=glucoclean.top;
h=Mime-Version:Content-Type:Date:From:Reply-To:Subject:To:Message-ID; i=piano_courses@glucoclean.top;
bh=GfDrKUPIizcV/MK3OPrkQCH/kek=;
b=rIhQFyLDJM2EinQNhgFwvMZUwMWl4QOJHIJ/rz0nlcUDG2YhHne7dAqcf0Dciglz/uZiwAYwrBQV
   CPWY8gjQY3z8wh7hCuPw6RxrL4RAj3LVctMnUZv4q//VCid00BQ99dh09QDjz0OeayL9xlcybD8k
   7En/e98n/opqsS6zWToWea6ZPyj3PCNakT5d2d6ADcpOnjGuyd30pORJ6JQEs8VkimxJmyH10whS
   OVZXkyMdeiQxQe6UB6DK4XJ6Fcfpe2AePh10LS5MmAzeGWMrP1WZiS4kLWic26XySgrUs/n05zeu
   Ku8F9ytP+Skdeqhpnm7+6Cx38TzbDPKcHpYsZg==
DomainKey-Signature: a=rsa-sha1; c=nofws; q=dns; s=k1; d=glucoclean.top;
b=XzKBARTF7xXLCGviPPTB9NHIFllrYT4Mg7IFBPHY2VQlQOpOPQVS82TBSaP5zw9rr0ta6Sw7up8S
   J2ur5R54pQDHE9zlPu34Jt3WnCWaIZ1NoM39amC6MvN+oprjEDLjfNsiAaBBBphOZI/R85w4Hf7/
   AQRdw7xJjeuampfMQFb7stdsH+6sDK4X/nvVfHC6UA5tLrbOj7ZEkh+JjToANBGekRZkPFep0PbI
   oqFeXajQwys+NSW8hoX/2FheV1D0eSVdpHeURTbGRTliKbzSn9tXD0EWjJfEPvmQuOsSZhKNC7O0
   0krppBldTRqEIA4LsX6KCD4CFwh9mmOjoAhjng==;
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="f88c13b9d82dffeebb1963faea6e8096"
Date: Sat, 25 Jan 2025 01:12:21 -0800
From: "Learn Piano" <piano_courses@glucoclean.top>
Reply-To: "Learn Piano" <piano_courses@glucoclean.top>
Subject: The Ingenious Way TO Learn Piano
To: <xxxxx>
Message-ID: <9ygfco8n5y24e2ef-e7rv91lkz8maawv2-4302d@glucoclean.top>

3 Reply by Cthulhu

  • Cthulhu
  • Member
  • Offline
  • Registered: 2019-06-04
  • Posts: 928

Re: MX stops working and starts again after reboot

How much RAM do you have?

iredmail needs at least 4GB ram for a low traffic mailserver

4 Reply by mikek

  • mikek
  • Member
  • Offline
  • Registered: 2020-08-20
  • Posts: 22

Re: MX stops working and starts again after reboot

Cthulhu wrote:

How much RAM do you have?

iredmail needs at least 4GB ram for a low traffic mailserver

I only had 1GB ram set for the Hyper-V VM. I increased it to 8GB and 4 cores. So far so good. I will see after a few hours if it keeps going.

5 Reply by mikek

  • mikek
  • Member
  • Offline
  • Registered: 2020-08-20
  • Posts: 22

Re: MX stops working and starts again after reboot

Adding RAM made no difference. It stops working after less than an hour and starts working when I reboot.

6 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,197

Re: MX stops working and starts again after reboot

Any related error in /var/log/syslog, /var/log/dovecot/*.log?