Closed (fixed)
Project:
Mailer Plus (DSM+)
Version:
1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
3 Jan 2022 at 12:39 UTC
Updated:
28 Oct 2022 at 09:59 UTC
Jump to comment: Most recent
Comments
Comment #2
jeroentAs a workaround, you can create a mailer transport of the type "DSN" and fill in something like
smtp://localhost:25?verify_peer=0Comment #3
adamps commentedThanks for the issue, good idea. This could be added as an option in
SmtpTransport.Comment #6
mschudders commentedadded the option for verify_peer.
Will report back after testing, but local testing seems good.
Comment #7
adamps commentedMany thanks for the patch. I have some comments (some in the MR, some here that are additions)
Comment #9
nrogers commentedI have made the requested changes and also changed what I think was unintended behavior in the TransportBase getDsn function since it was adding an '@' when username and pass are empty.
Comment #10
nrogers commentedAlso, I'm not entirely sure it's necessary to update the schema if the new options are in the defaultConfiguration() function since setConfiguration is called upon plugin initialization and the default configuration is merged with the current configuration. But I could be wrong.
Comment #11
nrogers commentedComment #12
solideogloria commentedComment #13
adamps commentedLooks very good thanks. I added some more comments, however they are now all minor and should be very quick.
The schema is needed thanks - it is separate from the idea of default values. It provides metadata for config information, see docs. The config_inspector module is useful to test the schema is correct.
Comment #14
nrogers commentedOk, requested changes made as well as some other minor form changes for consistency and to follow the form elements UI standards.
Comment #15
nrogers commentedAlso, I meant the schema update hook to resave all the smtp transports, not the schema modification itself, sorry I wasn't very clear there. It doesn't hurt to just ensure all the values are present either way, I just wasn't sure if it mattered if existing smtp transport configs were updated with the new default values or not. Thanks Adam!
Comment #17
adamps commentedGreat many thanks
I see you might be right, although I have a vague memory of warnings in the past if it's skipped. Anyway it's good as it is, definitely safe.