Athanasius II Dabbas

Patriarch Athanasius II Dabbas (died 1619), sometime known also as Athanasius III,[1] was Eastern Orthodox Patriarch of Antioch from 1611 to 1619.

Athanasius II Dabbas
Patriarch of Antioch
ChurchMelkite Church
SeePatriarch of Antioch
InstalledSeptember 1611
Term ended1619
PredecessorDorotheus IV Ibn Al-Ahmar
SuccessorIgnatius III Atiyah and Cyril IV Dabbas.
Personal details
Died1619
Tripoli (Lebanon)

Life

Athanasius II Dabbas succeeded to be elected Patriarch because he promised to the Damascenes to pay annually the deficit of the tax required of the Christians (Kharaj tax) by the Ottomans. Thus he was consecrated Patriarch in September 1611.[2]

In 1612 he appointed and consecrated metropolitan bishop of Aleppo Meletios Karmah (who twenty years later became patriarch), with whom he later argued for financial reasons or for Meletios’ contacts with the Franciscans. In 1614 Athanasius went to Constantinople to ask Ecumenical Patriarch Timothy II to depose Meletios, who also came to Constantinople. The two prelates, Athanasius and Meletios, were then able to reach an agreement.[3] Athanasius had a positive opinion of the Latin missionaries in Syria, and in 1617 he probably held a pro-Catholic synod.[2]

Athanasius was not able to uphold the promise of paying the tax required of the Christians, and thus in 1619 he was imprisoned by the Ottoman governor of Damascus and was put in jail. After he paid a large ransom he was allowed to leave for Tripoli (Lebanon) where he died of illness in 1619.[4]

Notes

  1. He is known as Athanasius II in the patriarchal lists of Korolevski and Skaff, as Athanasius III in the list of Costantius.
  2. Raheb, Abdallah (1981). Conception of the Union in the Orthodox Patriarchate of Antioch (1622 - 1672) (PDF). Beirut. pp. 20–21. Retrieved 7 June 2010.
  3. Levenq, G. (1930). "Athanase II". Dictionnaire d'histoire et de géographie ecclésiastiques. 4. Paris: Letouzey et Ané. p. 1369.
  4. Skaff, Elias (1993). The place of the Patriarchs of Antioch in Church History. Sophia Press. pp. 279–280.
gollark: TS can happily be precompiled to multiple JS files for each route or whatever.
gollark: But as I *said*, there's no issue with using TS in that situation either, unless you are somehow generating JS from scratch for some stupid reason on every request.
gollark: The full osmarks.net setup is hilariously complex, involves at least fifteen different backend services spread across two machines, and involves about 400 lines of nginx configuration.
gollark: Then you won't get HTTPS or nice links.
gollark: It *can* also just serve static files, which are good enough for most cases.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.