162
Views
12
CrossRef citations to date
0
Altmetric
Research Article

PTS1-independent targeting of isocitrate lyase to peroxisomes requires the PTS1 receptor Pex5p

, , &
Pages 61-69 | Published online: 09 Jul 2009
 

Abstract

The targeting of castor bean isocitrate lyase to peroxisomes was studied by expression in the heterologous host Saccharomyces cerevisae from which the endogenous ICL1 gene had been removed by gene disruption. Peroxisomal import of ICL was dependent upon the PTS1 receptor Pex5p and was lost by deletion of the last three amino acids, Ala-Arg-Met. However, removal of an additional 16 amino acids restored the ability of this truncated ICL to be targeted to peroxisomes and this import activity, like that of the full-length protein, was dependent upon Pex5p. The ability of peptides corresponding to the carboxyl terminal ends of wild-type and Δ3 and Δ19 mutants of ICL to interact with the PTS1-binding portion of Pex5p from humans, plants and yeast was determined using the yeast two-hybrid system. The peptide corresponding to wild-type ICL interacted with all three Pex5p proteins to differing extents, but neither mutant could interact with Pex5p from any species. Thus, ICL can be targeted to peroxisomes in a Pex5p-dependent but PTS1-independent fashion. These results help to clarify the contradictory published data about the requirement of the PTS1 signal for ICL targeting.

Reprints and Corporate Permissions

Please note: Selecting permissions does not provide access to the full text of the article, please see our help page How do I view content?

To request a reprint or corporate permissions for this article, please click on the relevant link below:

Academic Permissions

Please note: Selecting permissions does not provide access to the full text of the article, please see our help page How do I view content?

Obtain permissions instantly via Rightslink by clicking on the button below:

If you are unable to obtain permissions via Rightslink, please complete and submit this Permissions form. For more information, please visit our Permissions help page.