If you're not on SQL version here is a workaround. Normally I am totally against this idea b/c of data integrity reasons.
On 4.50 a customer needed EmailUserID to be 36 instead of default of 30. I saw the field was not used in any other tables. I used DFDM to uncheck the box for Formatted Display (to disassociate the dictionary) then entered the 36-digit value. It expanded the (physical) field for me to 36 while dict length stayed at 30 (this is what Skip Source Data Truncation does in VI). This was OK b/c the field wasn't used elsewhere and they never did any reporting on it (e.g. Company Listing). I made note when they upgrade it would get chopped back down to 30 and I would need to re-do this (unless they upgraded to SQL where it's stuck at 30)
If you BACKUP the Sy_Company.m4t file and find the EmailUserIDPassword$ field is not used elsewhere you could try this below. I normally would have said just use same DFDM trick above but problem is you need to put in the encrypted password.
So on v2014 I tried V/ just now into Sy_Company (made BACKUP the Sy_Company.m4t file first) using a 20-digit password. Originally I checked the box for Skip Source Data Truncation as it does the expand trick but it doesn't work on this table.
So I unchecked it and then it worked. The reason is it encrypted my password first and the encrypted one is only 14 digits! Had I started with 21 unencrypted it may have encrypted to 15 ergo no go.
Import Job specifics:
* Table Name = Sy_Company
* On Data tab use these 3 fields and do a REPLACE on all 3: CompanyKey (from DFDM), CompanyCode, and EmailUserIDPassword$
Note from this point onwards never use the Company Maint / Email tab screen to maintain any changes in password. Always import into it. Also if you upgrade, you'll have to repeat this trick unless they upgrade to SQL and then M/D tricks are needed.