View Bug Details

IDProjectCategoryView StatusLast Update
0000818DCP-o-maticBugspublic2018-10-17 20:16
ReporterCarsten Assigned Tocarl  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
PlatformMacOSOS XOS Version10.6
Product Version2.7.0 
Target Version2.8.0 
Summary0000818: Glitch in using cinema KDM recipients email addresses
Description

When an entry for an email recipients in the cinema database is empty, sending the KDM email to all recipients fails (Error: Failed to send email (Failed sending data to the peer), seemingly because DOM tries to send the KDM email to an 'empty' recipient.
Creating such an empty entry is 'too easy to let this happen'. - E.G. when you quit the 'Add' or 'Edit' dialog with 'OK' while the address field is empty.

I just tried to send test emails for the new time zone feature, and the send process always failed for one cinema for no apparent reason. Until I went into cinema details and noticed that black line indicating an empty address entry. See attached screenshot.

Steps To Reproduce

Create an empty email entry in the cinema database. Send KDM Email to this cinema.

TagsNo tags attached.
Branch
Estimated weeks required
Estimated work requiredAverage

Activities

Carsten

2016-03-11 20:34

manager  

empty_email_fields.pdf (94,785 bytes)

Carsten

2016-03-11 20:45

manager   ~0001166

Seems the same happens when an entry in the Preferences -> KDM Email -> CC: addresses fields is empty.

I guess it's best to discard empty entries in both databases in general.

carl

2016-03-13 02:49

administrator   ~0001172

Empty email addresses not stored by 692f9e2951a8bf600f95bb0b76c18df71c881504.

Bug History

Date Modified Username Field Change
2016-03-11 20:34 Carsten New Bug
2016-03-11 20:34 Carsten File Added: empty_email_fields.pdf
2016-03-11 20:45 Carsten Note Added: 0001166
2016-03-12 01:16 carl Status new => acknowledged
2016-03-12 01:16 carl Target Version => 2.8.0
2016-03-13 02:49 carl Note Added: 0001172
2016-03-13 02:49 carl Status acknowledged => resolved
2016-03-13 02:49 carl Resolution open => fixed
2016-03-13 02:49 carl Assigned To => carl
2018-10-17 20:16 carl Status resolved => closed