Search results

  1. T

    Variables for message email

    Thanks, very helpful! I added |DUMPTOKENS| to the welcome email. Here are the fields it added: OWNED PORT SERVERNAME account additional_bandwidth aftp api_with_password bandwidth catchall cgi creator cron date_created dnscontrol docsroot domain domainptr email ftp inode ip language login_keys...
  2. T

    Variables for message email

    I’m wondering this, too.
  3. T

    Why was this email discarded?

    Thanks.
  4. T

    Why was this email discarded?

    My customer is having trouble receiving email from domains that use protection.outlook.com. Can you help me understand why this particular email was deleted? Relevant lines from /var/log/exim/mainlog-20210822: The discarded line says “R=domain_filter”. This client has the DA adult filter...
  5. T

    Question about esf_skip_hosts

    I have easy spam fighter enabled. A client cannot receive emails from a vendor because the vendor uses zoho.com and the vendor’s domain does not have DKIM correctly configured. If I add *.zoho.com to /etc/virtual/esf_skip_hosts, will that fix the problem? 2020-09-29 16:00:57 1kNLo1-007Cr1-LV...
  6. T

    Allow users to change skin?

    I agree. I’m glad it’s available at all, but I still had trouble finding it even though I knew where to look!
  7. T

    Is it possible to customize the message easy spam fighter gives when it rejects mail?

    Thanks. I upvoted the feature request.
  8. T

    Is it possible to customize the message easy spam fighter gives when it rejects mail?

    In the file /etc/exim.easy_spam_fighter/check_message.conf, there is this line: I would like to tweak that message. Is there a way to do that that will persist through custombuild updates to easy_spam_fighter and exim_conf?
  9. T

    Allow users to change skin?

    I must be blind, but I don’t see it in Evolution or Enhanced.
  10. T

    Allow users to change skin?

    Is it possible to allow users to change their own skins?
  11. T

    cannot allow TLS1.0, TLS1.1 in exim

    Indeed! I tried that, too, but no luck so far.
  12. T

    cannot allow TLS1.0, TLS1.1 in exim

    @wtptrs, try this, from https://forum.nginx.org/read.php?2,281984,282011#msg-282011
  13. T

    cannot allow TLS1.0, TLS1.1 in exim

    Looks like there may be a similar issue in Debian: https://forum.nginx.org/read.php?2,281984,281984
  14. T

    cannot allow TLS1.0, TLS1.1 in exim

    Update: update-crypto-policies --set LEGACY fixed the problem even without rebooting, although I did restart exim.
  15. T

    cannot allow TLS1.0, TLS1.1 in exim

    OpenSSL 1.1.1g 21 Apr 2020 It looks like I have to reboot to see if update-crypto-policies --set LEGACY made a difference. Will do that overnight.
  16. T

    cannot allow TLS1.0, TLS1.1 in exim

    It may have to do with this: https://access.redhat.com/articles/3642912 I am thinking that update-crypto-policies --set LEGACY will allow the client to connect. Waiting to hear back to know for sure.
  17. T

    cannot allow TLS1.0, TLS1.1 in exim

    Yes, an old Mac Mail client. I used this guide, which fixed the issue in CentOS 7: https://help.poralix.com/articles/fixing-ssl-routines-error-ssl23-unknown-protocol-exim However, the error message mentioned there is different than the one I’m seeing now.
  18. T

    cannot allow TLS1.0, TLS1.1 in exim

    Having the same issue on CentOS 8. The same configuration worked on CentOS 7. The error message when the client tries to send mail: TLS error on connection ... (SSL_accept (TLSv1)): error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol
  19. T

    Permissions error when restoring from backup onto new server

    Thanks for your help. I fixed the problem by chmodding 644 all the files that were giving errors. I went back and looked again at my custombuild options and noticed that mod_ruid2=no on the new server (CentOS 8) and mod_ruid2=yes on the old server (CentOS 7). Many of the user’s files on the...
  20. T

    Permissions error when restoring from backup onto new server

    I am moving users from one server to another by creating an admin backup for the user on the old server and then restoring the user on the new server. I have done this before and it has worked well, and it has worked well today so far. However, I have run into a snag with a certain user...
Top