AttributeError: 'bool' object has no attribute 'split'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Server Environment And Tools |
New
|
Undecided
|
Unassigned |
Bug Description
When I put below information to test it with gmail I am facing below problem:
File "/opt/ingenuity
fields = conf.mail_
AttributeError: 'bool' object has no attribute 'split'
Here is the information I put in the incoming mail configuration in openerp7:
server: smtp.gmail.com
port :993
SSL:True
username: <email address hidden>
password: mypassword
Path Model Field (model) Match algorithm Field (email)
INBOX Message Domain of email address
"[Gmail]/Sent Mail" Message Domain of email address
Regards,
Mohammad
Related branches
- Stefan Rijnhart (Opener): Approve (code review)
- Ronald Portier (Therp) (community): Approve (test)
- Holger Brunn (Therp): Needs Resubmitting
- Nicolas JEUDY (community): Needs Fixing (code review and test install)
-
Diff: 1019 lines (+939/-0)15 files modifiedfetchmail_attach_from_folder/__init__.py (+25/-0)
fetchmail_attach_from_folder/__openerp__.py (+46/-0)
fetchmail_attach_from_folder/match_algorithm/__init__.py (+26/-0)
fetchmail_attach_from_folder/match_algorithm/base.py (+43/-0)
fetchmail_attach_from_folder/match_algorithm/email_domain.py (+44/-0)
fetchmail_attach_from_folder/match_algorithm/email_exact.py (+56/-0)
fetchmail_attach_from_folder/match_algorithm/openerp_standard.py (+51/-0)
fetchmail_attach_from_folder/model/__init__.py (+24/-0)
fetchmail_attach_from_folder/model/fetchmail_server.py (+280/-0)
fetchmail_attach_from_folder/model/fetchmail_server_folder.py (+120/-0)
fetchmail_attach_from_folder/security/ir.model.access.csv (+2/-0)
fetchmail_attach_from_folder/view/fetchmail_server.xml (+56/-0)
fetchmail_attach_from_folder/wizard/__init__.py (+23/-0)
fetchmail_attach_from_folder/wizard/attach_mail_manually.py (+114/-0)
fetchmail_attach_from_folder/wizard/attach_mail_manually.xml (+29/-0)
Go to your folder configuration and fill in 'to' or 'from' into the field 'Field (email)'. This matching algorithm also requires 'Field (model)' to be filled to do something useful.
Yes, you should get a warning or even an error message for filling in an invalid configuration, that would be a lot more user friendly.