DKIM stopped working

Discussion in 'Installation/Configuration' started by AzraelAkuma, Oct 25, 2023.

  1. AzraelAkuma

    AzraelAkuma New Member

    Hello.
    This is my first post on this Forum. I've been using ISPConfig for many years and it's been nice experience. I guess yesterday was my unlucky day. I upgraded from Ubuntu Server 20.04 to 22.04. Everything looked good, but after a while people started complaining about e-mail issues. I noticed that DKIM is no longer applied to outgoing emails. I had no idea where to start investigation, so I installed opemdkim (i thought it had been removed during upgrade), that didnt help. Then I ran ispconfig update script, and that killed mail services totally.
    (delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)
    I restored /etc from backup and server is operational now, but still no DKIM. In the web UI all domain keys are in place. I dont know how dkim is implented in ispconfig. Please advice.
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    ISPConfig does not use OpenDkim for email signing, it has to be uninstalled as it might collide with other parts of the setup. It uses amavisd or Rspamd, depending on your setup. You must run the ISPConfig update script after you upgraded the OS as the config files of the OS must be adjusted to match the requirements of the new software versions.

    This means that amavisd was not started. Start amavisd and if it does not start, check the mail.log file to see why it can not start.
     
  3. AzraelAkuma

    AzraelAkuma New Member

    I removed opendkim, reinstalled amavisd, and ran ispconfig update script. All services are running, but no incoming/outgoing mail works.

    Oct 25 09:45:48 taube.lukas.design amavis[1129]: (01129-09) (!)XkYEZhAGIcT9 FWD from <[email protected]> -> <[email protected]>, 451 4.5.0 From MTA() during fwd-connect (All attempts (1) >

    ostfix/smtpd[2429]: warning: connect to Milter service inet:localhost:11332: Connection refused
     
  4. AzraelAkuma

    AzraelAkuma New Member

    i also found this:
    amavis[9755]: (09755-12) (!)connect to 127.0.0.1:* failed, attempt #1: Can't connect to socket 127.0.0.1:* using module IO::Socket::IP: Connection refused
    that gets me to this:
    serverfault.com/questions/958695/amavis-cant-connect-to-socket-127-0-0-1-using-module-iosocketip-connec
    but i made no changes to main.cf...
     
  5. Taleman

    Taleman Well-Known Member HowtoForge Supporter

  6. till

    till Super Moderator Staff Member ISPConfig Developer

    Check under system > server config that spamfilter is set to amavis and not rspamd. if that#s correct, change it to rspamd, save, change back to amavis and press save.
     
  7. AzraelAkuma

    AzraelAkuma New Member

    Hi,
    I restored basic functionality. I compared main.cf and master.cf with other ISPconfig servers (used only for web hosting) and added back missing part. Now sending / receiving works again, but still no DKIM. (SPF and DMARC is OK) I must have missed something.
    @ Taleman - Yes I ran update script.
     
    ahrasis likes this.
  8. till

    till Super Moderator Staff Member ISPConfig Developer

    Did you purge the config when reinstalling amavisd? If yes, this might have wiped out the dkim signatures which are part of the amavisd config. You can try to use Tools > resync to resync the email domains.
     
    ahrasis likes this.
  9. AzraelAkuma

    AzraelAkuma New Member

    No I didn't purge. I think it got removed during OS upgrade in the first place, I only installed it back.
    Resync didnt help.
     
  10. AzraelAkuma

    AzraelAkuma New Member

    I figured it out. / /etc/amavis/conf.d/60-dkim was empty. Thanx for the hint.
     

Share This Page