ZhangHuangbin wrote:pbf343 wrote:Where do I locate the correct amavisd password from MySQL to insert into the settings.py file?
Check 'iRedMail.tips' file. You remember this file?
Or, check '@storage_sql_dsn' setting in Amavisd config file. Reference: http://www.iredmail.org/docs/file.locat … ml#amavisd
Yes remember that file and it has a value. However, this system was maintained by another person and has had two upgrades (performed by you) so I did not think that file would be accurate today. Thanks for the tip/tips :-)
Ironically, I also looked in the original "config" file which is also archived on the system. It has a value which I just tried. if understanding the logs, it is working now without any db_connection errors at this time. The value does in fact match the iRedMail.tips file value as well. So, it appears to have NOT been altered.
Example:
2015-07-08 12:27:18 DEBUG smtp session: encryption_cipher=
2015-07-08 12:27:18 DEBUG smtp session: encryption_keysize=0
2015-07-08 12:27:18 DEBUG --> Apply plugin: reject_null_sender
2015-07-08 12:27:18 DEBUG <-- Result: DUNNO
2015-07-08 12:27:18 DEBUG Creating Amavisd database connection.
2015-07-08 12:27:18 DEBUG Got db cursor.
2015-07-08 12:27:18 DEBUG --> Apply plugin: amavisd_wblist
2015-07-08 12:27:18 DEBUG Possible policy senders: ['@.', 'fernanda@speedjon.com', '@speedjon.com', '@.speedjon.com', '@com', '@.com', '82.211.35.173', '82.*.*.*', '*.*.*.173', '82.*.35.173', '82.211.35.*', '82.211.*.173', '*.211.35.173', '82.*.*.173', '*.*.35.173', '*.*.*.*', '82.211.*.*']
This still never answered the question as to where in the MySQL database said password lives. Are you not willing to share where that value resides in the database? Was I correct and that is just the hashed string of the plain text string?
Great, I will read it today. However, I'm getting an error when following the link. Maybe it is not published live yet?
ZhangHuangbin wrote:Note: still not yet finished.
Agreed. Watching the iredapd.log via debug mode now. Testing some inbound e-mail which appears to be arriving.
Dashboard does in fact show Top 10 with "<>" user as high user for the existing period.
I'm thinking that:
The db connection failure was resulting in system NOT blocking "null user"
That if corrected the null user block should start taking place now.
Once published and read by me, what else do you recommend to investigate?
Thank you for the replies & help!