According to the 1.2 version of the YAML spec "The content of a mapping node is an unordered set of key: value node pairs, with the restriction that each of the keys is unique." so you have badly formed YAML and parsers are free to handle that as they see fit. Do you have any control over the generation of the config file?

If the structures contained in the files are simple you could write a simple parser and handle the multiple entries in whatever fashion makes sense in your application. If you describe the bigger task you are working on we may be able to offer better advice.

Can you show us your sample confi file?

I am also using YAML file config with same keys, I used to read all the keys as array of hashes.

use strict;
use warnings;
use YAML::XS qw/LoadFile/;
use Data::Dumper;
my $config = LoadFile('./config.yaml');

print Dumper($config);
[download]

---
- emailName: ree
- emailAddresses:
    - test@test.com
    - user@domain.com
- credential:
    username: user1
    password: password
- credential:
    username: vinothg
    password: password
[download]

If you don't have the more fanciful features of YAML in your input, try YAML::Tiny.

use strict;
use warnings;
use YAML::Tiny;
my $yaml = YAML::Tiny->read('test.yaml');
[download]

---
rootproperty: blah
section:
  one: two
  three: four
  Foo: Bar
  one: again
  empty: ~
[download]

D:\>perl test.pl
YAML::Tiny found a duplicate key 'one' in line 'again' at test.pl line
+ 5.
[download]

test1:
  abc:
  abc:
    - sdhfg

test1:
  - def

test1:
  ghi:
    - sdjfhgsdj
    - sdgfgsd
  ghi:
    - rty
    - weytr

test2:
  - jkl
[download]