Since the update to 15.3 (or around the same time) I initially got an error message with the following line:
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd which was error: unsupported dictionary type: hash
I fixed the error by changing hash: to lmdb: and that error is removed. However, I know get an error stating
“status=deferred (SASL authentication failed; cannot authenticate to server smtp.gmail.com[108.177.15.109]: invalid parameter supplied)”
This is the relevant area that I changed in main.cf. these changes are at the end of the file, and all other occurrences of the parameters have been commented out.
I have a few relays configured in my postfix configuration, and uncomment the one I require. For Gmail, I remember I had to add a couple of lines and this is what I have now:-
Hi,
The issue is “perhaps” with the upgrade to postfix 3.5.9, where hash is no longer acceptable it seems.
I check in one of my backups for 15.2 where the emails were working and I was using hash. The error message received suggests looking at a Google link which I will now do.
THe error message says that it is an Authentication Error. Do you have 2 step authentication turned on? If you do then you have to create an app specific password. Not sure of the detail, I have it turned off but here is a link:
OK, just did some very basic editing on a vanila Leap 15.3 (postfix 3.5.9). Simply added the relay details to main.cf and added a sasl password file with my gmail details and my normal relay.
Relayed via my normal relay but failed with gmail. Think something has changed in the version for 15.3
,Hi JulinaB,
As I don’t quite see how the 679,687… & 717,719… numbers fir into the file.
If I could please request a copy of your working file that would be great.
I have sent a PM.
copied sasl_passwd to gmail and added the [smtp.gmail.com]:465 user@gmail.com:password
7 ran postmap /etc/postfix/gmail to produce gmail.lmdb
started postfix and got
2021-08-23T13:58:16.632689+01:00 venus postfix/pickup[17137]: 9A5F1251539: uid=0 from=<root>
2021-08-23T13:58:16.632945+01:00 venus postfix/trivial-rewrite[17140]: using backwards-compatible default setting append_dot_mydomain=yes to rewrite "venus" to "venus.localdomain"
2021-08-23T13:58:16.633150+01:00 venus postfix/cleanup[17139]: warning: lmdb:/etc/postfix/sender_canonical is unavailable. open database /etc/postfix/sender_canonical.lmdb: No such file or directory
2021-08-23T13:58:16.633200+01:00 venus postfix/cleanup[17139]: warning: lmdb:/etc/postfix/sender_canonical lookup error for "root@venus.localdomain"
2021-08-23T13:58:16.633253+01:00 venus postfix/cleanup[17139]: warning: 9A5F1251539: sender_canonical_maps map lookup problem for root@venus.localdomain -- message not accepted, try again later
2021-08-23T13:58:16.633294+01:00 venus postfix/cleanup[17139]: warning: lmdb:/etc/postfix/canonical is unavailable. open database /etc/postfix/canonical.lmdb: No such file or directory
2021-08-23T13:58:16.633344+01:00 venus postfix/cleanup[17139]: warning: lmdb:/etc/postfix/canonical lookup error for "root@venus.localdomain"
As you can see there are lots of unable to find .lmdb type files. Can I ask what other steps you took?
Nothing else but my system has the following in /etc/postfix:
Progress:~ # cd /etc/postfix
Progress:/etc/postfix # ls -al *.lmdb
-rw-r--r-- 1 root root 8192 Aug 6 10:50 access.lmdb
-rw-r--r-- 1 root root 8192 Aug 6 10:50 canonical.lmdb
-rw-r--r-- 1 root root 12288 Aug 21 15:40 gmail.lmdb
-rw-r--r-- 1 root root 8192 Aug 6 10:50 helo_access.lmdb
-rw-r--r-- 1 root root 8192 Aug 6 10:50 relay.lmdb
-rw-r--r-- 1 root root 8192 Aug 6 10:50 relay_ccerts.lmdb
-rw-r--r-- 1 root root 8192 Aug 6 10:50 relocated.lmdb
-rw------- 1 root root 8192 Aug 6 10:50 sasl_passwd.lmdb
-rw-r--r-- 1 root root 8192 Aug 6 10:50 sender_canonical.lmdb
-rw-r--r-- 1 root root 8192 Aug 6 10:50 transport.lmdb
-rw-r--r-- 1 root root 8192 Aug 6 10:50 virtual.lmdb
Progress:/etc/postfix # ls -al *canonical*
-rw-r--r-- 1 root root 13194 Jun 10 10:25 canonical
-rw-r--r-- 1 root root 12288 Mar 5 10:55 canonical.db
-rw-r--r-- 1 root root 8192 Aug 6 10:50 canonical.lmdb
-rw-r--r-- 1 root root 412 Jun 10 10:25 sender_canonical
-rw-r--r-- 1 root root 12288 Mar 5 10:55 sender_canonical.db
-rw-r--r-- 1 root root 8192 Aug 6 10:50 sender_canonical.lmdb
Progress:/etc/postfix #
The *.db files are redundant now of course but I do have canonical and canonical.lmdb. Only guessing but maybe the .lmdb versions were only created because there was a corresponding .db file or were referenced in your original main.cf.
Anyway to create canonical.lmdb etc, assuming that there is already a canonical file etc:
If you don’t have a base file then I suggest that you just comment out the lines in main.cf - neither file has any contents other than comments on my system.
Kind of suggest to me that the email address or password is wrong. Do you have any funny characters in either like punctuation marks. I use only letters and numbers.
Hi Julina
I doubled /triple checked the sasl_passwd/gmail file for username and password error and found no problems. - Only text nad numbers no special characters
I deliberately used a wrong password and got the same answer. - possible indication not reading sasl_passwd/gmail file correctly???
Anyway I built a stock 15.3 virtual machine changed the indicated parameters and got the same result.
So now I am completely confused - one last thing to try is to build a 15.2 virtual PC and try original settings and change bits as I go.
whilst installing 15.3 I saw in the release note that due to licenses etc 15.3 was dropping support for Berkeley DB and this affected Postfix
