I ask this because when I have asked our ISP for more details, they forward me the log and it shows the exact reason it failed, such as no such user, spam, etc. If it still fails, contact your system administrator." Why would it not report a specific reason? Our users receive a generic 5.0.0 NDR which states "The e-mail system was unable to deliver the message, but did not report a specific reason. Now the problem is this - when a user sends an email outside of our domain and it fails for a valid reason such as the user does not exist at the organization, file size too large, etc. It's an odd setup in my opinion but I'm not experienced to say otherwise. Our ISP is our email host in that when creating a new user, we create it on our ISP site and then forward it to our Exchange server. We use SMTP connectors for the domains we have. Also supports X.509 PKI auth via STARTTLS and EXTERNAL.We have Exchange 2003 running in our head office. Supports all Cyrus SASL authentication methods except for APOP. Internal, LOGIN, PLAIN, X.500 ( DAP), LDAP, OpenLDAP, Active Directory, eDirectory, Kerberos, etc. ![]() Alternate checkpassword utilities support authentication against PAM, LDAP, and databases. The original supports only LOGIN and PLAIN. Pluggable Authentication Modules, GSSAPI, CRAM-MD5, DIGEST-MD5, APOP, PLAIN, LDAP, CMU SASL library, Kerberos Supports adding new authentication mechanisms through custom backends. Plain, Login, CRAM-MD5, DIGEST-MD5, Certificateīy default PLAIN and LOGIN over SSL only, Certificates, bsd_auth and PAM. Internal, LOGIN, PLAIN, CRAM-MD5, Netware, LDAP?, partial NT Domain NT Domain, Active Directory, Local Directory NT Domain, Active Directory, PLAIN, LOGIN, NTLM, SCRAM-MD5, CRAM-MD5 ![]() Kolab employs Cyrus and Postfix and thus supports all Cyrus SASL authentication methods and X.509 PKI auth via STARTTLS and EXTERNAL. Proxy to other server, any other mechanism via AUTH plugins.Īctive Directory, Windows authentication, CRAM-MD5, PLAIN, LOGIN Many mechanism (SMTP callout, Dovecot SASL, REST, etc.) via script. PLAIN, LOGIN, CRAM-MD5, DIGEST-MD5, APOP, ODBC, Active Directory, NT Domain APOP and SASL mechanisms: ANONYMOUS, PLAIN, LOGIN, CRAM-MD5, DIGEST-MD5, SCRAM-SHA-1, EXTERNAL, GSSAPI, NTLM, OTP, SKEY, RPA.ĬRAM-MD5, DIGEST-MD5, PLAIN, LOGINĬyrus SASL, Dovecot SASL, GNU SASL, CRAM-MD5, Heimdal GSSAPI, PLAIN, LOGIN, SPA PAM, MySQL, PostgreSQL, SQLite, LDAP, Active Directory(LDAP), Kerberos 5, proxied IMAP auth, getpwent, shadow, SIA, BSDauth, Vpopmail. Uses Cyrus SASL authentication library for support for other mechanisms: Berkeley DB, GDBM, or NDBM (sasldb), PAM, MySQL, PostgreSQL, SQLite, LDAP, Active Directory(LDAP), DCE, Kerberos 4 and 5, proxied IMAP auth, getpwent, shadow, SIA, Courier Authdaemon, httpform, APOP and SASL mechanisms: ANONYMOUS, CRAM-MD5, DIGEST-MD5, SCRAM-SHA-1(-PLUS), SCRAM-SHA-224(-PLUS), SCRAM-SHA-256(-PLUS), SCRAM-SHA-384(-PLUS), SCRAM-SHA-512(-PLUS), EXTERNAL, GSSAPI, LOGIN, NTLM, OTP, PASSDSS, PLAIN, SRP Supports X.509 PKI auth via STARTTLS and EXTERNAL. Managed by Courier authentication library which can use PAM, Userdb, PostgreSQL(beta), MySQL, LDAP, and EXTERNAL. Also supports X.509 PKI auth via STARTTLS/SSL GSSAPI, CRAM-MD5, DIGEST-MD5, APOP, CLRTXT, LOGIN, PLAIN, LDAP, InternalĪctive Directory (LDAP), CLRTXT, CRAM-MD5, DIGEST-MD5, APOP, GSSAPI, NTLM, MSN, SESSIONID, External Authentication Plug-in. ![]() Native Anti Hammer - Brute-force attack protection Proprietary with OSS parts, a community ( Freeware) and 3 paid editions (SMB, Enterprise, Hosting) Proprietary/ SaaS, with open-source parts Proprietary (free version: 5 domains, 5 users, 5 groups) Embedded, Optimized for Email & Groupware
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |