1 Topic by trichardson

  • trichardson
  • Member
  • Offline
  • Registered: 2018-08-03
  • Posts: 10

Topic: User sent emails not showing in iRedAdmin

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 0.9.8
- Linux/BSD distribution name and version: CentOS 7
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): LDAP
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? Yes
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

We have a few accounts on a single domain, setup through iRedAdmin-Pro. All seems to work fine, apart from one user who registers 0 emails in the 'sent log' on iRedAdmin. The received and quarantines is all okay, just the sent. All other users are unaffected.

I have checked their mailbox and they are able to send fine and mails are in their 'sent' mailbox.

Any pointers appreciated
Thanks

----

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

2 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,790

Re: User sent emails not showing in iRedAdmin

How does this user send email? Does he send with a MUA with SMTP authentication enabled?

3 Reply by trichardson

  • trichardson
  • Member
  • Offline
  • Registered: 2018-08-03
  • Posts: 10

Re: User sent emails not showing in iRedAdmin

They use Thunderbird MUA and connect to SMTP over 993 with Auth enabled. They also send over ActiveSync (iOS) and its the same outcome - mails sent sucessfully, but not logged in the sent emails list on the admin panel.

4 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,790

Re: User sent emails not showing in iRedAdmin

- SMTP over 993? SMTP should use port 587 with STARTTLS (or TLS) secure connection. If you enable smtp over ssl in Postfix, you can also use port 465 with SSL secure connection.
- You need to check Postfix log file and find related error. It's hard for others to help without related log.

5 Reply by trichardson

  • trichardson
  • Member
  • Offline
  • Registered: 2018-08-03
  • Posts: 10

Re: User sent emails not showing in iRedAdmin

Sorry, yes 993 for IMAP, 587 STARTTLS with auth to Postfix.
There are no errors shown in the Postfix log. Mails are delivered successfully, it just doesn't seem to get added to the 'iRedAdmin-Pro' database entry (if there is such a thing).

6 Reply by trichardson

  • trichardson
  • Member
  • Offline
  • Registered: 2018-08-03
  • Posts: 10

Re: User sent emails not showing in iRedAdmin

trichardson wrote:

Sorry, yes 993 for IMAP, 587 STARTTLS with auth to Postfix.
There are no errors shown in the Postfix log. Mails are delivered successfully, it just doesn't seem to get added to the 'iRedAdmin-Pro' database entry (if there is such a thing).

Actually - I do see an error with AlterMIME for this user which then skips, so may explain it. Didn't think that would be problem, but perhaps if it skips this step, this is where it gets added to the database.

Aug  6 12:11:46 mx1 postfix/submission/smtpd[7753]: 1EA6624D51024: client=unknown[172.18.14.21], sasl_method=PLAIN, sasl_username=USER@MAILSERVER.COM
Aug  6 12:11:46 mx1 postfix/cleanup[7754]: 1EA6624D51024: message-id=<e238b1a5-28ed-23ed-510a-c2229593a03e@MAILSERVER.COM>
Aug  6 12:11:46 mx1 postfix/qmgr[28319]: 1EA6624D51024: from=<USER@MAILSERVER.COM>, size=3800, nrcpt=1 (queue active)
Aug  6 12:11:46 mx1 postfix/submission/smtpd[7753]: disconnect from unknown[172.18.14.21]
Aug  6 12:11:46 mx1 amavis[27928]: (27928-11) (!!)collect_results from [7972] (/usr/bin/altermime): DIED, signal 11 (000b) mime_alter.c:1401:AM_disclaimer_load_text:ERROR: Cannot stat '/etc/postfix/disclaimer/default.txt' (No such file or directory)\nmime_alter.c:1401:AM_disclaimer_load_text:ERROR: Cannot stat '/etc/postfix/disclaimer/default.txt' (No such file or directory)\nmime_alter.c:2350:AM_insert_disclaimer_into_segment:WARNING: Disclaimer was NULL after linebreak adaption\n
Aug  6 12:11:46 mx1 amavis[27928]: (27928-11) (!)mangling by altermime failed: Program /usr/bin/altermime failed: 11, mime_alter.c:1401:AM_disclaimer_load_text:ERROR: Cannot stat '/etc/postfix/disclaimer/default.txt' (No such file or directory)\nmime_alter.c:1401:AM_disclaimer_load_text:ERROR: Cannot stat '/etc/postfix/disclaimer/default.txt' (No such file or directory)\nmime_alter.c:2350:AM_insert_disclaimer_into_segment:WARNING: Disclaimer was NULL after linebreak adaption, mail will pass unmodified
Aug  6 12:11:46 mx1 postfix/10025/smtpd[7766]: connect from mx1.MAILSERVER.COM[127.0.0.1]

I will attempt to look for errors here

7 Reply by trichardson

  • trichardson
  • Member
  • Offline
  • Registered: 2018-08-03
  • Posts: 10

Re: User sent emails not showing in iRedAdmin

I've cleared the altermime error (recreated default.txt), but it still does not show the sent mail in the iRedAdmin log. It just shows 'No outgoing mails.'

8 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,790

Re: User sent emails not showing in iRedAdmin

Are you sure no any Amavisd error in Postfix log file?

Amavisd processes the mail (calls SpamAssassin and ClamAV for spam/virus scanning), then store the basic info of processed mail in SQL database, then iRedAdmin-Pro can see the info by querying SQL db.

In your case, seems Amavisd didn't successfully process the mail and didn't store the mail info in SQL db. So i suggest sending some more emails for testing, and check Amavisd log carefully. You may want to turn on debug mode in Amavisd for further debugging, FYI:
https://docs.iredmail.org/debug.amavisd.html

9 Reply by trichardson

  • trichardson
  • Member
  • Offline
  • Registered: 2018-08-03
  • Posts: 10

Re: User sent emails not showing in iRedAdmin

Please close this and thanks for the help. It turns out the user had the mail address spelt wrong (which is one of out alias domains, so it was allowed).

Once the mail address was corrected, it showed up in the logs