Hi all! Thanks to all who were interested and answered for this issue. I appreciate it. An update below.
On 25/05/17 18:08, Andreas Schamanek wrote: > Hi Daniel, > > I wish I could help. I even compared your stuff with my setup and > re-read https://wiki.debian.org/PostfixAndSASL , Now I don't > understand why it works at all on my server. However, I'll ignore this > and keep my fingers off and crossed ;-) > > On Thu, 25 May 2017, at 21:15, John Fawcett wrote: > >> Is the contents of the file containing the sasl users and passwords >> the same between the two hosts? > > That's a good question, though. My Debian Postfix uses PAM. The DB is > empty: > > ``` > # sasldblistusers2 -v 2>&1 | grep version > Built against SASL API version 2.1.26 > LibSasl version 2.1.26 by "Cyrus SASL" > # sasldblistusers2 #-> returns nothing > # strings /etc/sasldb2 > no:such:user > userPassword > ``` Fortunately I was able to find the cause of this issue and authentication is already working. As mentioned in another thread (Delivery to accounts of the same domain on two different servers), there are already users authenticating without problems. It seems that the issue was a inconsistency in the servername: /etc/hostname for the operating system provided by the VPS provider had uppercase and lowercase characters but when creating each SASL user, these users uses a realm with the hostname string passed entirely to lowercase. After changing the host name to something less cryptic and everything in lowercase and re-creating the users in SASL, everything worked without problems. Something quite weird ... but we always learn new things ... :-) Kind regards, Daniel
signature.asc
Description: OpenPGP digital signature
